Database Users

g1 problem

hi i need help plz after rooting i don spl . the device now on g1 logo i try meny things home+power - cmera+power ..... nothing

First of all, you've officially murdered the English language. The only way I sort of understood what you were saying was by copy and pasting your post to Google Translate.
Secondly, I still can't understand it. So you rooted but didn't flash an SPL but flashed the radio, and now your stuck at G1 logo? Hmmm, I could only presume you've successfully entered Bricksville (Population: Noobs*Infinite).
Try pulling out the battery and boot into Recovery (Home + Power) Mode, FastBoot (Back + Power) Mode, or Bootloader (Volume Down/Camera + Power) Mode.
Or plug in USB adapter into device and setup ADB. After you've successfully setup ADB, get back to me so I can give you the commands and needed nbh files to pull you out of your predicament.

I mean, after change recovery img I done spl but the device freeze on G1 logo and it doesnt respond . what you mean setup ADB ???????

dude you are basically f'ed. you didnt update your radio did you. you just flashed a spl. welcome to BRICKSVILLE. population...YOU. and countless others who probably didnt READ AND RE READ THE ENTIRE POST AND READ WHILE YOU ARE DOING THESE PROCEDURES. these CAN AND WILL BRICK YOUR PHONE IF YOU DO NOT KNOW WHAT YOU ARE DOING.

It's quite amazing that the population of "Bricksville" continues to grow. There is plenty of literature out there about rooting your device but it still seems to elude some. Just awesome. And how true.. Noobs*Infinite... I lol'd.

nolimit78 said:
It's quite amazing that the population of "Bricksville" continues to grow. There is plenty of literature out there about rooting your device but it still seems to elude some. Just awesome. And how true.. Noobs*Infinite... I lol'd.
Click to expand...
Click to collapse
Very true, it's impossible to brick unless you have trouble reading that means you need to go back to elementary.

Ace42 said:
Very true, it's impossible to brick unless you have trouble reading that means you need to go back to elementary.
Click to expand...
Click to collapse
+1. This is true.

Meh, it's probably just a troll.

Lol these posts are quite funny
bricksville... I'll keep that in mind... lol

I think I asked for help, not a silly jokes

majed2001 said:
I think I asked for help, not a silly jokes
Click to expand...
Click to collapse
you got help. the jokes were for our amusement. its not our fault you bricked your phone, we are allowed to "chuckle" when other people mess up, because we know that we are smart enought to keep our very expensive phones up and running.

[MISC] Full brick

So I got my Z yesterday. thought i root it today, the easy way with the terminal so downloaded:
wpthis-Z.ko and
hboot_7230_0.84.2000_100908.nb0
I Had over 50% battery and full root access. Everything was going great until I try reboot the phone and it would not start up again. Now it's completely dead no lights when I charge, no buttons work. Dead.

Oh no !
Which guide were you following to do it ? Do you think you might have type the wrong destination partition when you did the "dd" to copy the hboot across ?

This One http://forum.xda-developers.com/showthread.php?t=835777it is very strange . i dont understand

So how far did you get ? Did all the rooting go ok ? And then it only went wrong after you dd'd the new hboot and then rebooted the phone ?

steviewevie said:
So how far did you get ? Did all the rooting go ok ? And then it only went wrong after you dd'd the new hboot and then rebooted the phone ?
Click to expand...
Click to collapse
Rooting whent ok but after the dd and try to reboot . dead.

I can only guess that either the hboot image was corrupted, or you somehow typed the "dd" command wrong, so that something else was overwritten.
Either way, it doesn't sound good, but I hope someone else can come up with some sort of miracle for you.
I presume leaving it on charge doesn't help ? Just in case the battery has died too much (and the 50% charge it said wasn't really accurate).

steviewevie said:
I can only guess that either the hboot image was corrupted, or you somehow typed the "dd" command wrong, so that something else was overwritten.
Either way, it doesn't sound good, but I hope someone else can come up with some sort of miracle for you.
I presume leaving it on charge doesn't help ? Just in case the battery has died too much (and the 50% charge it said wasn't really accurate).
Click to expand...
Click to collapse
I have rooted some phones in the past. but nothing like this has happened to me before.
most likely corrupt img I tink.
but its very strange that it comply dead !

stian230 said:
I have rooted some phones in the past. but nothing like this has happened to me before.
most likely corrupt img I tink.
but its very strange that it comply dead !
Click to expand...
Click to collapse
Do you still have a copy of the hboot that you downloaded ? Because you could compare the MD5 checksum on that to see if it was corrupted.

steviewevie said:
Do you still have a copy of the hboot that you downloaded ? Because you could compare the MD5 checksum on that to see if it was corrupted.
Click to expand...
Click to collapse
right I have on my pc, thanks steviewevie. hm back to the old N1. crappy ****

I think its send to htc time, just say you was flashing a ruu and it turned off and went dead plead ignorance always
JD
Sent from my HTC Desire Z Beast

JupiterDroid said:
I think its send to htc time, just say you was flashing a ruu and it turned off and went dead plead ignorance always
JD
Sent from my HTC Desire Z Beast
Click to expand...
Click to collapse
Yes I gess you right JD. waiting for Monday to come .

Is it possible that the hboot-file doesn't work with the nordic DZ's?
I probably have the same batch of the norwegian model like Stian, and got perm-root without any problems using the same guide.
S-OFF on the other hand didn't work.. It made my phone enter a infinite boot loop, so it didn't get any further than the "Quietly brilliant"-screen... Luckily, the phone wasn't bricked, so I could enter bootloader and reset to factory..
For the record; i checked the MD5 checksums, and used adb shell on my computer so that I could copy/paste the "dd"-command hence preventing any typo's...

Duppsko said:
Is it possible that the hboot-file doesn't work with the nordic DZ's?
I probably have the same batch of the norwegian model like Stian, and got perm-root without any problems using the same guide.
S-OFF on the other hand didn't work.. It made my phone enter a infinite boot loop, so it didn't get any further than the "Quietly brilliant"-screen... Luckily, the phone wasn't bricked, so I could enter bootloader and reset to factory..
For the record; i checked the MD5 checksums, and used adb shell on my computer so that I could copy/paste the "dd"-command hence preventing any typo's...
Click to expand...
Click to collapse
I'm very keen on finding an answer to this. I'm getting my Finnish version and would like to get it rooted etc but if the hboot does no work we will be out of luck? Unless someone finds a new one somewhere?

AnyDone said:
I'm very keen on finding an answer to this. I'm getting my Finnish version and would like to get it rooted etc but if the hboot does no work we will be out of luck? Unless someone finds a new one somewhere?
Click to expand...
Click to collapse
I'm sure VISIONary r14 has perm root without flashing a new hboot.

Sure about that? Seems I missed it completely that it can be done without flashing hboot? Doesn't hboot mount it r-o again after restart?

Duppsko said:
Is it possible that the hboot-file doesn't work with the nordic DZ's?
I probably have the same batch of the norwegian model like Stian, and got perm-root without any problems using the same guide.
S-OFF on the other hand didn't work.. It made my phone enter a infinite boot loop, so it didn't get any further than the "Quietly brilliant"-screen... Luckily, the phone wasn't bricked, so I could enter bootloader and reset to factory..
For the record; i checked the MD5 checksums, and used adb shell on my computer so that I could copy/paste the "dd"-command hence preventing any typo's...
Click to expand...
Click to collapse
I don't have the nordic edition , I order my from expansys.

AnyDone said:
Sure about that? Seems I missed it completely that it can be done without flashing hboot? Doesn't hboot mount it r-o again after restart?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=846223
r12 [test version]
Temproot is now the default
Added option to try to Permroot (test on Desire HD, Desire Z and G2)
After permroot, required kernel module is placed in /data/local for your convenience
Added option to unroot
Note: this does NOT rewrite your hboot - you will need to do this manually to get S-OFF.
Click to expand...
Click to collapse
It is now r14 - but perm root was incorporated in r12.

MD5 checksums:
2ce1bdd5e4c1119ccfcecb938710d742
2CE1BDD5E4C1119CCFCECB938710D742 so the file was not corrupt. does anyone have new theories ??? going to call htc to tomorrow

Just call me Mr.Brick or "the Bricker boy"

Can you get into fastboot?
If not then you probably wont be able to do a thing. Except JTAG.
Have you tried a power cycle by any chance? Take out battery, hold power button for 10 seconds with NO battery installed. Sometimes it works miracles.

[Q] xoom bricked ?

hi guys ...i hav some big problem n i really need ur help pls.
i hav tried to root my xoom but it failed n now im afraid i hav bricked my xoom
- unlock ok
- fastboot flash boot boot.img ok
- fastboot reboot fail ( dual core technology frozen)
the only thing that it shows is the dual core technology screen nothing more and when i reset it it starts alone by itself again and stock
i hav a motorola xoom 3g titan i guess before i try to root it was 3.0.1 or may be 3.1
but i never try to use a sd card so i dont know if it works
while trying to fix it i wipe the factory, cache but still bricked
best regards

daddymaths said:
hi guys ...i hav some big problem n i really need ur help pls.
i hav tried to root my xoom but it failed n now im afraid i hav bricked my xoom
- unlock ok
- fastboot flash boot boot.img ok
- fastboot reboot fail ( dual core technology frozen)
the only thing that it shows is the dual core technology screen nothing more and when i reset it it starts alone by itself again and stock
i hav a motorola xoom 3g titan i guess before i try to root it was 3.0.1 or may be 3.1
but i never try to use a sd card so i dont know if it works
while trying to fix it i wipe the factory, cache but still bricked
best regards
Click to expand...
Click to collapse
The sd card should not be an issue since you use your computer connected to the Xoom with adb/fastboot when rooting.
Which rooting guide are you using? It does matter, especially for 3G non-US models.
I'm sure you are not bricked. You will need to start again but make sure you have all of the correct files in you platform tools folder (or whatever folder you are using for adb).
If you have successfully unlocked you can skip that step.

You are frozen at the dual core screen because you have flashed an incorrect boot.img for your specific model of xoom, and the android version you have on your xoom a.k.a 3.0-3.2. Since you are on the 3g version make sure you get a 3g boot.img and might as well get both the 3.1 and 3.0.1 boot.Hold the power button and the volume up button at the same time to reboot, wait 3 seconds,and then press only the the volume up button. you should now have a message at the top that says starting fastboot protocol support. begin flashing the images.

rootfan said:
You are frozen at the dual core screen because you have flashed an incorrect boot.img for your specific model of xoom, and the android version you have on your xoom a.k.a 3.0-3.2. Since you are on the 3g version make sure you get a 3g boot.img and might as well get both the 3.1 and 3.0.1 boot.Hold the power button and the volume up button at the same time to reboot, wait 3 seconds,and then press only the the volume up button. you should now have a message at the top that says starting fastboot protocol support. begin flashing the images.
Click to expand...
Click to collapse
Ditto, you will know for sure whenu brick when your screen is black only. You have a little work to do as notedbut stay calm.. You will get things fixed.

rockhumper said:
Ditto, you will know for sure whenu brick when your screen is black only. You have a little work to do as notedbut stay calm.. You will get things fixed.
Click to expand...
Click to collapse
+1 dont jump the gun and read everything over 5x before moving forward... Its a lil work like said but you will probably be more knowledgeable after its all said and done and be able to help others that may be stuck like you one day..
Good luck

Hey guys... I have bricked my xoom too. It's a wifi only xoom. I missed the last step in the guide I was using "fastboot oen lock" and rebooted... so now it stays on the dual core screen. I tried vol up and power buttons to get fastboot and it stays on the starting fastboot protocol... the computer doesn't recognize it. Just don't know what to do next...
Please help...!
Sent from my T959 using XDA App

rickyx said:
Hey guys... I have bricked my xoom too. It's a wifi only xoom. I missed the last step in the guide I was using "fastboot oen lock" and rebooted... so now it stays on the dual core screen. I tried vol up and power buttons to get fastboot and it stays on the starting fastboot protocol... the computer doesn't recognize it. Just don't know what to do next...
Please help...!
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Read the sticky on page one... That says a guide to all your rooting needs... Proceed

This is what scares people
Don't freak out if your xoom won't boot. Your xooms are certainly not nowhere near bricked. >.>

Kippui said:
This is what scares people
Don't freak out if your xoom won't boot. Your xooms are certainly not nowhere near bricked. >.>
Click to expand...
Click to collapse
The word "bricked" gets way too much use... 95% of folks saying they bricked are no where near it...

rockhumper said:
The word "bricked" gets way too much use... 95% of folks saying they bricked are no where near it...
Click to expand...
Click to collapse
I have only seen one bricked xoom so far.
Sent from my PG86100 using Tapatalk

bwcorvus said:
I have only seen one bricked xoom so far.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Dont you know that 50 percent of all statistics are made up? And thats 99 percent of the time

thx guys
i was unfortunately little bit busy with work and exams ....i m relieve ..i will try to follow ur advices and keep u in touch.
thx a lot.
best regards
daddymaths

Is your Xoom still "bricked?" If so, shoot me a PM and I'll help you out. I HIGHLY doubt it is truly bricked.

rooting guide?
okantomi said:
The sd card should not be an issue since you use your computer connected to the Xoom with adb/fastboot when rooting.
Which rooting guide are you using? It does matter, especially for 3G non-US models.
I'm sure you are not bricked. You will need to start again but make sure you have all of the correct files in you platform tools folder (or whatever folder you are using for adb).
If you have successfully unlocked you can skip that step.
Click to expand...
Click to collapse
i have as i say a 3G motorola titan ....could anyone provides me the right routing files ? thx

I have a completely and 100% bricked Xoom. Was in the rooting process, and did something wrong, but the device is totally dead.
No response when plugging in via USB, although white LED illuminates when the power is plugged in.

cdinoz said:
I have a completely and 100% bricked Xoom. Was in the rooting process, and did something wrong, but the device is totally dead.
No response when plugging in via USB, although white LED illuminates when the power is plugged in.
Click to expand...
Click to collapse
Hit power and volume up to reboot...there is nothing the root process can do to brick it. Stop by the irc channel.
Sent from my PG86100 using Tapatalk

Have tried that.... Is still dead, and get no response from the device. Apparently I may have totally wiped the NAND storage....?

cdinoz said:
Have tried that.... Is still dead, and get no response from the device. Apparently I may have totally wiped the NAND storage....?
Click to expand...
Click to collapse
What exactly did you do (or try to do)?

okantomi said:
What exactly did you do (or try to do)?
Click to expand...
Click to collapse
I tried to root the device and install the Tiamat kernel. I was enabling the micro SD slot (or so I thought) and when I dropped in my SD card, there was a warning that the device needed to be re-partitioned. So I did. Didnt format the microSD, seems to have formatted the entire device.
Related to this issue:
http://forum.xda-developers.com/showthread.php?p=14462676#post14462676

cdinoz said:
I tried to root the device and install the Tiamat kernel. I was enabling the micro SD slot (or so I thought) and when I dropped in my SD card, there was a warning that the device needed to be re-partitioned. So I did. Didnt format the microSD, seems to have formatted the entire device.
Related to this issue:
http://forum.xda-developers.com/showthread.php?p=14462676#post14462676
Click to expand...
Click to collapse
That's one of the only two ways to brick it. I would stop by the irc channel, but I think you may have actually bricked it.
Sent from my PG86100 using Tapatalk

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!

I need Help - Serious Acting up of Phone

I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.

live_free said:
I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.
Click to expand...
Click to collapse
what sbf did you flash? is it att bell etc? need some more info to help you out.

aideneisley3 said:
what sbf did you flash? is it att bell etc? need some more info to help you out.
Click to expand...
Click to collapse
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204

live_free said:
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204
Click to expand...
Click to collapse
STEPS:
1) Have the correct Motorola drivers installed for your PC (i.e. x32-bit or x64-bit).
2) Download RSD Lite (Links above) & install on your PC.
3) Choose a sbf file to download and flash from Motorola Atrix Firmware Super Thread: http://forum.xda-developers.com/showthread.php?t=1125944
If you are currently running firmware 4.5.91, I suggest that you only flash back to this firmware version. Flashing back to a eariler sbf/firmware version may have unintended consequences, the most serious of which is bricking your device.
*Note: U.S. AT&T users should only flash AT&T sbfs, internationl users should only flash their particular sbf versions.
4) Read the above sbf hints, trick, etc. to help prevent RSD Lite problems/errors.
5) Open RSD Lite and load the sbf file that you downloaded.
6) Put your device in RSD Protocol Mode by powering OFF, and upon powering back ON, hold both the power button and the volume UP button. Device should now say "Entering RSD Protocol Mode."
7) Connect your device to your computer via the usb cable, and select your device by clicking/highlighting it in RSD Lite.
8) Select START in RSD Lite and let the sbf flash process fully complete before disconnecting the device from the PC. There will be several reboots and the process make take 5 - 10 minutes to complete a FULL sbf flash.
9) If you have any errors or problems as a question, prefably in the Q&A section.
this is what i have done and worked for me! good luck
i copied this from the noob guide found here http://forum.xda-developers.com/showthread.php?t=1154600

Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.

live_free said:
Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.
Click to expand...
Click to collapse
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!

aideneisley3 said:
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!
Click to expand...
Click to collapse
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.

live_free said:
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.
Click to expand...
Click to collapse
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf

aideneisley3 said:
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
Click to expand...
Click to collapse
Yes. Same exact problem.

live_free said:
Yes. Same exact problem.
Click to expand...
Click to collapse
oh ok well then i'd have to agree with you then maybe it is a hardware problem... sorry i wasn't much help.
it wouldn't hurt as a last ditch effort to use motorola's software update program that you can download from their site it will tell you that there is no update and ask if you want to use it to restore your phone basically it reflashes it...
haha thats all i got. maybe someone else could offer more help.
good luck! =]

live_free said:
I did everything properly and now am in a boot loop, and I've done a battery pull.
Click to expand...
Click to collapse
apparently not.

in his defense replacement phones are refurbished (cough... broken and maybe fixed to like new). motorola gave me a replacement with broken senor so the screen didn't turn off when i was in a call and that was out of the box and when they replaced that one the screen was messed up it had super bright spots all over the screen so it is possible that it is moto's fault.
not saying it is moto's fault but that it is possible lol