[Q] Please help me to escape from brick! Is this a H/W error or S/W error? - General Questions and Answers

First, Sorry for my poor English, and thank you for reading this.
Please help me to escape from bricked phone!
At this point of time, I cannot determine the symptom wheter H/W related or S/W.
At HTC service center, they refuse to repair my DHD unless I restore bootscreen & S-off. However, my DHD is almost bricked (now stuck in first HTC logo) so I couldn't follow most of kindful guides in here.
Please let me determine the symptom, then I can give up if the problem is H/W related (and should pay almost $200 for fee), or I can continue to study in the case of S/W related problem.(Also I need some hints from you for finding solutions..)
Here are follow-up measures history.
Status of DHD at the accident
As-is Froyo
Rooted
S-OFF (eng off?)
ClockworkMod Recovery v3.0.2.5 installed
No more tuning except Camera and bootscreen
Never applied OTA (in Korea, not yet released)
Click to expand...
Click to collapse
Recent suspected events:
1. Accidental battery remove during last drinking before 4 hours.
2. Waiting phone to turn off under 2% due to Battery calibration before 30 minutes
Click to expand...
Click to collapse
Just before outbreak:
1. I excuted two browsers (FF4, Dolphin). Using Recent apps,I switched from Dolpin to FF4.
Then suddenly reboot loop started
Click to expand...
Click to collapse
Bootloader information
ACE PVT ENG-OFF
HBOOT-0.85.2007 (PD9815000)
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Click to expand...
Click to collapse
Symptom 1
Endless reboot after showing bootscreen.
Measure 1-1
Using ClockworkMod recovery, I tried to restore /system from lastest backup many times.
= It gave me an error "Error while formatting /system"
Measure 1-2
Using ClockworkMod recovery, I tried to format /system many times.
= It gave me an error "Error while formatting /system"
Measure 1-3 (HTC service man)
He tried to update (overwrite) ROM using microSD card (maybe PD98IMG.zip method)
=Reboot loop continues
=tunned bootscreen and S-off was unchanged.
He refused to repair (M/B replacement) my DHD unless I restore bootscreen & S-off.
Click to expand...
Click to collapse
Measure 1-4
installing RUU by myself using USB Calbe
(RUU_Ace_KT_KR_1.43.1010.2_Radio_12.28b.60.140e_26.03.02.26_M_release_158060_signed)
= failed. It couldn't find phone (I cannot enter android UI!).
installing RUU by myself using USB Calbe
RUU_Ace_HTC_WWE_1.15.405.1_Radio_12.21.60.12_26.02.00.09_M_test_148662
= failed. It couldn't find phone (I cannot enter android UI!).
Measure 1-5
Wipe Dalvik Cache = no effect
Fix Permissionts = no effect
Wipe datafactory reset=no effect
Symptom 2
Now DHD is stuck in HTC logo.
Click to expand...
Click to collapse
Please help me to determine the problem!
Is it H/W related error?
If then, maybe no one can be fix my DHD except HTC service man.
Is it S/W related error?
If then, here are two questions.
Why "Error while formatting /system" occurs?
Can this be fixed without entering android UI?
(Becasue I can't enter..)
Or
Modified screen and S-off can be restored without entering android UI?
(Becasue I can't enter..) If done, service man will replace M/B.
Thank you for reading this long thread!

bnsonear said:
First, Sorry for my poor English, and thank you for reading this.
Please help me to escape from bricked phone!
At this point of time, I cannot determine the symptom wheter H/W related or S/W.
At HTC service center, they refuse to repair my DHD unless I restore bootscreen & S-off. However, my DHD is almost bricked (now stuck in first HTC logo) so I couldn't follow most of kindful guides in here.
Please let me determine the symptom, then I can give up if the problem is H/W related (and should pay almost $200 for fee), or I can continue to study in the case of S/W related problem.(Also I need some hints from you for finding solutions..)
Here are follow-up measures history.
Please help me to determine the problem!
Is it H/W related error?
If then, maybe no one can be fix my DHD except HTC service man.
Is it S/W related error?
If then, here are two questions.
Why "Error while formatting /system" occurs?
Can this be fixed without entering android UI?
(Becasue I can't enter..)
Or
Modified screen and S-off can be restored without entering android UI?
(Becasue I can't enter..) If done, service man will replace M/B.
Thank you for reading this long thread!
Click to expand...
Click to collapse
ooh man its a long and harsh thread... ok
various things: CWM version that you are using can brick PERMANENTLY your phone because has a bug: it re-writes and formats the NAND memory of your device..(hasn´t reparation)be careful!! now in the dev. secction its available 3xx8 CWM with this bug fixed.
can you enter into recovery menu?
has you tried to boot your device in "safe mode"...
after reading it seems an apk problem.... safemode can help you to uninstall the last installed apk´s
if not solved we are going to use adb commands with sdk...

Related

The G1 Night Light (READ FIRST IF YOU BRICKED YOUR PHONE)

Many people complain that they have "bricked" their phones when they really haven't. This thread will hopefully help reduce the questions on all of our useful threads.
How to tell if your phone is bricked:
1.) When you try to turn it on, nothing happens?
2.) Camera+Power does nothing.
3.) Home+Power does nothing.
4.) You flashed the SPL BEFORE the radio
If you answered yes to any of the above 4, you are bricked. You probably need a new board in the phone. Read more here: http://forum.xda-developers.com/showthread.php?t=516440 It has been confirmed that you WILL brick your phone if you attempt to downgrade your radio after flashing the new SPL. Not sure why you would want to anyways...
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
2.) Your phone is stuck in a boot loop
3.) Home+Power boots into recovery
If you answered yes to the above then you are NOT bricked. You have the G1 Night Light. This is (usually) a very easy fix.
The usual scenario is: You just upgraded your radio and/or the SPL on your phone and now you are trying to turn it on with no luck.
How to fix: After you upgrade your radio and/or SPL, you need to wipe a rom on the phone. For a plain almost stock feeling rom, checkout http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/ if you are looking for hero, checkout the tutorial at g1upgrade.com.
I have also noticed when you flash hero, it will stay on the g1 logo for 5 or 6 minutes and then it'll finally start loading. Make sure your not being impatient and give it several minutes if you have just flashed a rom.
Last step:
If you have installed a new radio, then spl, then a new rom and you STILL get the g1 screen. Try it all over again. You probably didn't do something right. You don't need to ask questions in 30 different threads, your issue is not unique. You just need to search for some answers.
*Saved for future posts*
Edit:
Thanks! Updated.
I flashed the SPL before the radio whenever Haykuro released the Hero ROM and I didn't brick my device. Guess that I just got lucky. Thank goodness I know better now. haha
it's possible you flashed the radio prior to the SPL, only a loooong ways back.
Another thing to try if you are having issues is:
su
rm -r /system/sd/*
I was stuck in a boot loop and a quick ext3 wipe did the trick. The command should be able to be ran from console or terminal. You may need to mount /system with:
mount -t -rw,remount -o yaffs2 /dev/block/mtdblock3 /system
You would need to type that in between the commands above . I ran across this in another post but i think this is a good spot for it too .
Duplicate post...
thanx
At least I know now how to tell if I bricked my phone or just flashed it badly thanks for this.
youneek said:
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
Click to expand...
Click to collapse
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
alapapa said:
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
Click to expand...
Click to collapse
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Good Job
Sorry this is off topic. But...
Thank you for this thread!
Ok,
By the way, has anyone figured out what The difference in the baseband is?? I have a U in mine...
youneek said:
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Click to expand...
Click to collapse
really? if it can't get to recovery / fastboot mode nobody has published a fix w/o a hardware swap.
what's your method?
I will buy a bricked one off ebay and post the steps I do to get it back. I can only fix the "Night Light", I can't fix a truly bricked phone (yet).
digital006 said:
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
Click to expand...
Click to collapse
How and where did you sent for repair and how much does it cost? I have a bricked MyTouch3G at this moment. Did HTC took it?
not bricked just weird!
ok been reading on here ,not sure if i need to just reflash everything or sd issuse?i put the new raidio,then spl on !then put jacxrom on my phone worked great!then ran for a day.then tryed cyanogenmod 4.0 and loaded fine but got force closed issues at the google sign in so i wipe and went to jachero 1.2 loaded fine went to logo android and then htc ,but then the screen went to blank .like the as said g1 night light .so i went back to jacxrom 1.3 it loaded fine got stuck in t mobile g1 screen .ok i flashed again same thing. but this is the part if i take my memory card out it will boot up just fine!then put memory card back in but lol all apps are missing have reinstall them. i wipe every time.i have the latest raidio 22.19.26I).,spl 1.33.2005 .also the jacxrom is running fine when phones on .so any help please thanks .also when i put the spl on it loaded then said reboot so i did. after went back to recovery at the bottom it said formatting cach... but was setting there for a while so took battery out then booted phone .was it suposse to say done or not ! hope dont make any mad thanks for the info
bump
hey help me plz i have big problem
i forget hit alt+w when i install SPL then i press alt+s when SPL install i out battery then i put it my mobile don’t want open and when i holding down the Home and Power button don’t open recovery mode and i holding the End key and the Camera button don’t open boot loader plz help me plz
You aren't going to get any help with sentences that atrocious. Can you be more clear?

[Q] ***G1 screenshot for your troubleshooting perusal!***

Hi guys,
*Information contained in screenshots*
Posted a topic about a non-rooted G1 with only access to fastboot and hboot.
I was told that I would have to flash a signed ROM to solve my problem but unfortunately, after proceeding through the full ROGERS G1 downgrade guide by Haykuro, the problem still persists.
The only thing that could have gone wrong during the rooting process is the installation of the wrong recovery through flashrec (it only allowed for remote install for a 32a install).
Here is a screenshot of the phone in hboot for you to get all the info (spl, radio etc.) and a pic of the phone's screen past the splashscreen.
Anybody know how screwed I am?
adramelch said:
Hi guys,
*Information contained in screenshots*
Posted a topic about a non-rooted G1 with only access to fastboot and hboot.
I was told that I would have to flash a signed ROM to solve my problem but unfortunately, after proceeding through the full ROGERS G1 downgrade guide by Haykuro, the problem still persists.
The only thing that could have gone wrong during the rooting process is the installation of the wrong recovery through flashrec (it only allowed for remote install for a 32a install).
Here is a screenshot of the phone in hboot for you to get all the info (spl, radio etc.) and a pic of the phone's screen past the splashscreen.
Anybody know how screwed I am?
Click to expand...
Click to collapse
you're not screwed at all if you can fastboot. esp. on an unrooted g1.
do me a favor, on the screen with the exclamation point, open your keyboard and push ALT+L.
That'll get u a menu, do a data wipe.
Thank you! That solved it but now everytime the phone is turned off and is turned back on. I get to that famous screenshot of death.
Any clue?
Thank you for your reply! Much appreciated.

[Q] HELP

Hello everybody
My appologize if such kind topic is already posted but there is too much topic and I couldn't find relative information.
so, briefly I'll try to explain what was happened.
Month ago I've bought brand new HTC Desire S. Phone was bougt in Dubai, S-ON, Android 2.3.3
During update from android market (few games and facebook application, I clicked update all) my phone freezen, no reply at all.
I got desicion to remove battery and put it back. I've done it and phone switched on on white screen with HTC logo...that's all
Unfortunatelly, there is no any HTC customer service in our country, so I had to show my phone for another specialist. He recognized that boot file on my phone was corrupt, re-installed it. next step is to re-installe the software and here we met with problem.
no any software can be installed. I've used different software for different regions, but all of them were unsuccessful. initially it were shown two type of mistake
sometimes CID incorrect and sometimes Main version is older
we desided to install goldcart, so after installation is going ok, but again phone freezen on updating screen during bootloader update.
for info I've tried to install application from computer through the fastboot usb and through the memory card as well...both attepmts failed.
Does anybody can help me? Please consider that I'm not so perfect on such kind device and detailed explanation will highly appreciated. thanks in advance.
try install this RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.0 85AU_3805.06.02.03_M_release_199476_signed
from a windows PC while your HTC screen on bootloader
download this RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.0 85AU_3805.06.02.03_M_release_199476_signed from here http://forum.xda-developers.com/showthread.php?t=1002506
That sounds like the fried eMMC chip. You updated all on the market and pulled the battery out. You'll have to find someone who can open the phone up and replace the chip (beat you to it Ben!)
Sent from my HTC Desire S using XDA Premium App
S-ON + warranty = HTC Service repair
Adidas108 said:
S-ON + warranty = HTC Service repair
Click to expand...
Click to collapse
+1
return under warranty and get a replacement!
unfortunatelly, there is no sertificated HTC service in our country, so I need to send my phone to the Dubai..
Well the same exactly happened to me but luckily I was S-OFF & had Clockwork Recovery so everything was okay. I though that the eMMC chip was fried but I made a factory reset using Clockwork & it was solved.
I think you could just install a RUU that's certified from HTC, I would suggest that you download the WWE & If you tried that already try to access the the recovery screen (Vol Down + Power). If you couldn't access it then sorry, you're bricked.
Please reply with the results.
Can I also suggest that you rename your thread title to that it's a bit more meaningful and relevant to the problem that you're suffering, you do this by editing post #1 and using advanced edit.
to be honest I'm not so good in HTC...so fare problem not solved...but there is no any problem to get enter to the boot menu...if you pressing power with holding VOL down key phone goes to boot menu...
several people tried to solve the problem, but one of the restriction is S-ON mode...don't know what to do

[Q] Phone hangs during use - sometimes fails to mount /system or /data

This has been ongoing for a few weeks now. Desire S is currently running Endymion 2.2, but the same thing happened on Cyanogen and Stock roms. Phone will work fine for up to a day, then will completely freeze up during use (has happened in Browser, while entering text, and once just on the lockscreen). During the hang the touchscreen won't respond, connecting USB has no effect (no LED and ADB Devices lists nothing), the 4 buttons give haptic feedback for about 5 seconds after the hang, then nothing. Holding volume+power has no effect, but usually after about 10-20 tries or 15 minutes of doing nothing the phone will return to HTC boot screen, and sit there until I power it off and then remove the battery.
When using clockworkmod, half the time either /system or /data is not mountable (this only happoccasionally get "error mounting /cache/recovery/log"). When this is the case, formatting/factoryreset sometimes gives the "can't mount /data" error, and sometimes works.
Since switching to 4EXT the partitions are always mountable from recovery, but rebooting causes the phone to hang immediately after booting.
Current setup (which at the moment is hanging at the lockscreen)
HBOOT-6.98.2000 (PG88100000)
4EXT Recovery v2.2.7 RC5 (/system /cache and /data all ext4)
Endymion 2.2
tldr: is it possible for /system or /data to break during normal use and sometimes be unmountable? If yes, then can this be prevented? If no, any other suggestions as to what could be going on?
Reads the posts in the eMMC section at the bottom of the index thread, see end if my Sig for link
Swyped from my Desire S using XDA Premium
If you want my opinion, be drastic about your approach to this. Start from the ground up, that way you will be able to more or less narrow down the problem you are experiencing.
1. Change your HBOOT to 0.98.2000 (As you are using the revolutionary HBOOT, you will need to change this using a different method).
1a. Download HBOOT 0.98.2000 from this thread.
1b. Taken from this thread, use this method to change your HBOOT using adb. If you don't know how to use adb .. >_<.
Copy the hboot.img to your SDCARD.
In adb type:
adb devices
adb shell
su (doesn't matter if it says /system/sbin/su not found)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18​
2. Format all your partitions again using your recovery.
3. Re-install a FRESH ROM, try to avoid backups.​
Don't care if anyone thinks differently, this is just what I would do if I was having this problem.
Totally agree with the above post.
But I would suggest even more drastic approach. Restore to complete Stock and S-ON. There are Guides here how to do this. Then do a testing for a couple of days, maybe a week. At the moment when (if) this problem appears again run to your provider and insist a replacement.
IMO this way you will spare yourself a lot of nerves and troubles in future.
ben_pyett said:
Reads the posts in the eMMC section at the bottom of the index thread
Click to expand...
Click to collapse
sorry, didn't mention this in op - checked for eMMC issues when it first started happening and everything seemed okay, so I'm confident it's not a hardware fault. Not sure if there is a different problem that can result in similar, but sporadic, results.
Going to S-ON and try stock rom again and see how it goes.
Thanks guys
I checked mine and was also confident i had an ok emmc but alas, if you have the bad chip, you have a bad chip.
It may manifest it's self in different ways but eventually it's more than likely to fail. You would be wise to proceed with that caveat.
Sent from my HTC Desire
psimyn, how did it go? Also is it a telstra branded handset?
Sorry for the slow reply, finally got a response from the seller.
Handset was unbranded, bought from HK. The seller requested $40 for shipping both ways, which was apparently going to be refunded if the phone was covered by warranty.
Instead, I got an email yesterday claiming that the phone suffered a "software corruption" and that I had to pay an additional $45 for Labour and Administration. When I asked why the response was "I am just explaining to you that the labour cost and all administration are $45".
For now I just want the damn thing back, so it's been paid and they will hopefully send it today.

[Q] Unrooting HTC sensation/RUU

Hey guys,
so a time ago the volume knob disappeared from my HTC sensation. So I searched the internet and it turned out that I wasn't the only one with this problem. So I can turn it in for garanty but first I have to unroot it.
So I started unrooting following this guide: [GUIDE]How to Remove Custom Recovery/Root/Hboot and Keep Stock S-Off/Stock S-ON*VIDEO
So first all steps went flawless, but then I got to the step where you have to type "adb devices" in the cmd but it didn't show my phone. After hours of searching and trying different stuff I finally got to install the drivers for my phone correctly, and it finally showed up in the list of devices.
Then the next step: "9. If it is recognized, then download your official RUU, please get the same/similar version that came with your phone."
My phone is running cyanogenmod7.1.0 alpha 10 or something, and it's provider is Vodafone NL. So i didn't have a clue what RUU to download or where I could van these. Finally i found the following threat: [ROM]Shipped Pyramid ROM Collection.
As it didn't have a Vodafone NL RUU I downloaded the one for Vodafone UK.
Then I just tried it and first it reboots to the black HTC screen, and after a while I get the 171 Error. I tried almost anything but couldn't find what was wrong. And that's why I made this treath.
What I tried:
- Take out battery, start all over. Error 171 again.
- Leave phone on black HTC screen, run RUU again. Error 170.
- Run RUU in compatibality mode, all the same.
I have no clues what i'm doing wrong, the only thing I can think of is that I didn't turn off Fast Boot on my phone, but I can't find where I can do that. On the cyanogenmod wiki it says:
"Disable fastboot on the HTC Sensation (Settings » Power » Fastboot) or (Settings » Applications » Fastboot)"
But on my phone there is no Power menu in my settings, and in the applications meny there is no option to disable fastboot.
Anyone else experienced this problem before?
Thank you very, very much in advance, and I hope I didn't break any of the forum rules as this is my first post.
Greetings,
Frank
Go to http://theunlockr.com/2011/10/03/how-to-unroot-the-htc-sensation-4g/ and look at their tutorial it may help you out.
follow this thread.
http://forum.xda-developers.com/showthread.php?t=1478828
srauls said:
Go to http://theunlockr.com/2011/10/03/how-to-unroot-the-htc-sensation-4g/ and look at their tutorial it may help you out.
Click to expand...
Click to collapse
He took most of that tutorial of the one in my main thread, and doesn't have a solution for my problem. Thanks for the reply though.
musarraf172 said:
follow this thread.
http://forum.xda-developers.com/showthread.php?t=1478828
Click to expand...
Click to collapse
Thank you, didn't see that thread before! Too bad I don't have time right now so I'll try it another time. But that might indeed fix it

Categories

Resources