Database Develop

bricked HD

So, lets start at the begining.
Today I was testing the new android build from 20nov.
Everything went fine until restarting my phone into windows. The phone did boot properly, exept the screen stayed off.
Touch input did work.
After a couple of restarts everything was back to normal and i picked up the testing from the android build again.
However, a later on the same problem arised. This time more persistent.
Also the led wouldn't go on anymore when charging the phone...
After 30 tries of rebooting a decided to hard-reset the phone by holding Vol down+up and power. Then waiting a while (because i couldn't see what was happening) and then pressed vol up to hard reset.
Then waited like 5 minutes and then tried to boot again by holding the power button.... Nothing
Then waited another 5 minutes, pulled out the battery and tried another boot.
No succes either.
Bottom-line now.
The phone is dead, won't react to anything, no charging no booting.
What can I do???
No stock rom, so i guess no warranty???
Really hope someone can help!!!

Ouch , you're right about the no guarantee rule but i don't know what u could do ..
Best of luck pal.

Maybe anyone got any experience with garanty+ a flashed rom.
Who brought therte phone back with a flashed rom without telling HTC and got their warranty?
Would be great if that worked (a)

Can you do anything with phone? Try taking battery out for 24hrs before re-inserting it and attempting to reboot. If you can still do nothing with device you may have bricked it and only thing which can be done is to return it, though warranty void. Have you tried asking within Android thread to see if anyone else has had similar issues?

Fallen Spartan said:
Can you do anything with phone? Try taking battery out for 24hrs before re-inserting it and attempting to reboot. If you can still do nothing with device you may have bricked it and only thing which can be done is to return it, though warranty void. Have you tried asking within Android thread to see if anyone else has had similar issues?
Click to expand...
Click to collapse
Thanks for the battery tip, i'll try that!
about an hour ago i did get a little response from my phone. It vibrated after pushing the on button!
And then nothing....
This only happens when the phone is not connected to usb(charger or pc, no difference).
I did post my problem in the android thread, however no response.
I'll also PM phhusson about my problem. Would be nasty if more people would brick their phone.
Still like to hear some experiences with the garanty-service of HTC if anyone has got any

if it is so "dead" nobody can say if the ROM was original or not. let them think is a hardware problem and replace yr device!!

KukurikU said:
if it is so "dead" nobody can say if the ROM was original or not. let them think is a hardware problem and replace yr device!!
Click to expand...
Click to collapse
Well that is probably what i'm gonna do/try if I can't reanimate is myself
Just hope there really is no way of telling by HTC themselves...

Maybe try to see if you can flash a ROM image on it again from the SD card - doing it blind, there are only a few keys to press to reflash, maybe the screen is not working but the device powers up occasionally ?

Ingmar89 said:
Well that is probably what i'm gonna do/try if I can't reanimate is myself
Just hope there really is no way of telling by HTC themselves...
Click to expand...
Click to collapse
Try to flash a new cooked rom. Remove battery, then wait 30 secs, then put back battery and push volume down and power button simultaneously. Then you can flash a new rom.
It worked for me.
(sorry for my "english")

intresting
so, tried to flash via RUU.exe+connecting to my pc.
What I did:
-Vol down+power button
-connect phone to my pc via usb.
-run RUU.exe with a dutty rom
-then RUU says it couldn't find my phone.
However, my pc (windows 7) does!
But not how it is supossed to do it.
Check out the screen to see what i mean.
Maybe something more can be doen now? Anyone knows what is going on here?

Ingmar89 said:
so, tried to flash via RUU.exe+connecting to my pc.
What I did:
-Vol down+power button
-connect phone to my pc via usb.
-run RUU.exe with a dutty rom
-then RUU says it couldn't find my phone.
However, my pc (windows 7) does!
But not how it is supossed to do it.
Check out the screen to see what i mean.
Maybe something more can be doen now? Anyone knows what is going on here?
Click to expand...
Click to collapse
Maybe you just need to change drivers??? Becouse sometimes Vista change it by itself, so I think 7 can work in the same way?!
Try it, as far as can see from your screen there are no drivers installed
""Manufacturer: Unknown
Device Status: The driver for this device are not installed.""

Go to - Windows Mobile Device Center, then select - Mobile Device Settings, Connection Settings, then uncheck - Allow USB Connections.
Normally this would be ticked to allow syncs etc but to flash a rom it needs to be unchecked.
I cant tell from your post if you have done this or not.
Hope it helps.
H
Here on Vista
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here on XP
I dont have W7 but would imagine it will be similar.

I don't really think it's compulsory to uncheck this. I have it checked and flash my roms without any problems.
But Blackstone is not a friend of Seven at first. You have to tell him to recognise the other.
I have installed the windows-mobile device center from microsoft website and then Windows 7 recognized my HD otherwise I got the same problem as you (no driver).
Hope it can help !
- Bya -

Bya said:
I don't really think it's compulsory to uncheck this. I have it checked and flash my roms without any problems.
Click to expand...
Click to collapse
You may be right but mine will not work with the check mark still on.
H

It does look like a driver issue. Follow this thread to get the necessary usb drivers.

Do you have the Hspl? If yes can't you try flashing from the sd card? (The connection issue you showed is when you are in active sync mode, isn't it?)

Have you tried to flash an original ROM? It should work regardless of your USB connection settings and if you manage to do that and still no life in your hd - you can return it with warranty. And one more suggestion - find a XP machine to do this. Btw - flashing through the SD card is a very, VERY good idea.

succesfull flash, no result.
First of all, a huge thanks to you guys!
The idea's and help u came up with really made my day.
Second, I got to flash my phone. With the right drivers installed everything worked like it supposed to work.
However, the same problems still persist....
So I think this problem is deeper then rom orientated (ideas?)
Anyhow, now I'm able to flash a original rom to my phone, which should help my warranty!
Great job guys, kudos to you
tkolev said:
Have you tried to flash an original ROM? It should work regardless of your USB connection settings and if you manage to do that and still no life in your hd - you can return it with warranty. And one more suggestion - find a XP machine to do this. Btw - flashing through the SD card is a very, VERY good idea.
Click to expand...
Click to collapse
I already tried flashing through the SD card. Normally this is the way to go for me, but it didn't seem to do any good this time (not sure if I performed it correctly, since my screen is "dead")

I'm a bit confused... you managed to flash rom? So your sync works? (on the other side you say your screen is dead?)

Goten said:
I'm a bit confused... you managed to flash rom? So your sync works? (on the other side you say your screen is dead?)
Click to expand...
Click to collapse
Sync works, screen is dead.
that's a 100% correct...

[Q] The Worst Luck Ever!!

First of all I would like to say hi and thanks to everyone who contributes to this forum. You guys are pure genius!! I own 2 HTC Heros from Sprint. I use one, my wife uses the other one. We were both growing extremely frustrated with the Hero's laggy, almost unuseable Sense UI. So I started reading a bunch on the threads about rooting, Froyo, etc. I decided to give it a try. I used the "Easy Root" method posted by tehdarkknight located here. It worked!! So then I went ahead and installed ROM Manager, flashed clockworkmod recovery, and then did a nandroid. I then flashed AOSP v0.9.9.1-Froyo 2.2.1. Everything was working GREAT!! What a difference from Sprint's crapware loaded ROM. So I showed my wife, and she wanted it, too.
I got it all dialed in on her phone last night before bed, and she was digging it today. Then she dropped her phone (for the 1,000th time); only this time, the screen cracked and split in about 40 different spots. So I did a nandroid recovery, and undid the root per tehdarkknight's instructions. It seems stock, except that when I tried to let the latest Sprint OTA software update download & install, it failed, and the clockworkmod recovery screen showed up.
Finally, my question: Is this going to be a problem when I go in to have the phone replaced (we pay $7/month for insurance)? If so, what are the steps to get rid of the clockworkmod recovery, and make this Hero EXACTLY how it was before I started. Please go easy on me, I searched this forum, and Google in general, and couldn't find a definitive answer. I also tried to just install the HTC/Sprint RUU from their website, and it fails with a 171 code. Please help if you can. It will be greatly appreciated!!
Matt

http://forum.xda-developers.com/showpost.php?p=6686401&postcount=2
Download and run the RUU, then you're all set!

kwg8t7 said:
http://forum.xda-developers.com/showpost.php?p=6686401&postcount=2
Download and run the RUU, then you're all set!
Click to expand...
Click to collapse
Thanks for the quick reply!! I downloaded the file & tried to install. I get the same error I got when I downloaded the file from HTC here. Here is a picture of the error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then, when I unplug the usb cable, my phone shows a white screen with the below text in green:
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.42.02.10.29
Mar 1 2010,16:02:39
RUU
The above "RUU" is orange, but the rest of the text is green. Also there are 3 droids on skateboards at the bottom of the screen. At this point, the only way to reboot my phone is to take out the battery. Also, it was pretty hard to read that text through the cracked screen:
It should be noted that the problem has nothing to do with the USB connection. I am able to move files to and from my computer and phone. I also used the same computer and usb cable & port to root the phone last night.
I think the hboot is the problem. It's not the stock version. How can I change the hboot back to stock?
Thanks again,
Matt

I have Windows 7 32-bit (no idea if that is the problem) and I get that error message every time I run the RUU. I unplug the USB and reconnect it, and re-run the RUU and it works every time.

The Fer-Shiz-Nizzle said:
I have Windows 7 32-bit (no idea if that is the problem) and I get that error message every time I run the RUU. I unplug the USB and reconnect it, and re-run the RUU and it works every time.
Click to expand...
Click to collapse
So, I wish I could just unplug the USB and redo it, like you. Unfortunately, once I get the error, the only way I can use my phone is to r & r the battery. FYI, I get a "waiting for bootloader" message for about 90 seconds or so before I get the 171 error.
I went ahead and rooted again. Maybe I should try to flash the RUU with ROM Manager?? I'm pretty stumped at this point. How "stock" does the phone have to be to get it replaced with insurance for the cracked screen?
Thanks again,
Matt

The Fer-Shiz-Nizzle said:
I have Windows 7 32-bit (no idea if that is the problem) and I get that error message every time I run the RUU. I unplug the USB and reconnect it, and re-run the RUU and it works every time.
Click to expand...
Click to collapse
Woaa!! I'm not sure if re-rooting did the trick or not, but it worked! I rooted again, then ran the RUU installer. Once again, I got the 171 error, closed out the RUU program, unplugged the usb cable, and got the same screen with the skateboarding android dudes. Then I did what you said, just plugged it back in, which brought up the same HTC screen on the Hero as before. Only this time when I started the RUU installer, it instantly made progress. Update radio, update system, etc.
THANK YOU so much for replying to my question with the correct answer. I would have taken forever to figure that out, IF I would have figured it out at all. FWIW, I am running W7 64 bit, and I just ran the RUU straight from the HTC web site.
Also, the phone just now did an update to 2.31.651.7 via WiFi with no problem at all. It also upgraded the voicemail app, and I am about to do the 2.32.651.2 update right now. If it takes, should I assume I'm good to go to the Sprint store for a replacement?
Grateful with much gratitude,
Matt

Great! Glad I could help. And yes, you should be good to go. I just went through the same thing 2 days ago so I could take it to Sprint for speaker replacement. Of course they wanted to do a "hard reset" to see if that would fix it, and they stressed the fact that it would wipe all user date. I wanted to LOL! Well good luck, and I hope they don't think a hard reset will fix ur issue

Hey, I just noticed that the clockworkmod recovery is still flashed to the phone. Is it safe to assume that Sprint won't notice or care about this when I take the phone in later?

maddog808 said:
Hey, I just noticed that the clockworkmod recovery is still flashed to the phone. Is it safe to assume that Sprint won't notice or care about this when I take the phone in later?
Click to expand...
Click to collapse
Really?
That's odd. If the RUU was successful, and it does seem that it was, your phone should be 100% reverted to the factory image. The only exception I know of would be S-off status. Personally, I use Amon-RA recovery, and I have only used Clockwork 1 time for about 10 minutes, out of curiousity. So, do you still have root access? The only other thing I can recommend is to search the dev thread. I remember seeing a recent thread with an RUU that was flashable from recovery, no pc needed.
To answer your question, I doubt Sprint would need to access your recovery at the time of exchange, but later on in the repair facility is another story Hopefully someone else can chime in with more info. Good luck

This Might Work??? For Some Reason...... When I Updated The ROM Manager App On My Phone From 2.5.0.4 To 2.5.0.7 And Reboot Into Recovery It Gets Stuck On The HTC Screen And Won't Do Anything, So Basically What You Can Do Is Upgrade ROM Manager, Then Just UnInstall The Rom Manager App From Phone, And It Should Lock The Recovery Screen If They Try To Get Into It!! Then Just Put On Your Best Poker Face, And Act Like You Don't Even Know What A Recovery Screen Is Or Does!!! Lol!! But I Doubt They'll Even Go That Far!!
Sent from my HERO200 using XDA App

have ypu taken the phone into sprint yet? just a heads up that you will have to pay to get the phone replaced. i payed the $7 a month for insurance and took my phone in and they said that my problem is covered under insurance but that i need to pay a $50 deductable :O so just letting you know if you didnt.

The Fer-Shiz-Nizzle said:
Really?
That's odd. If the RUU was successful, and it does seem that it was, your phone should be 100% reverted to the factory image. The only exception I know of would be S-off status. Personally, I use Amon-RA recovery, and I have only used Clockwork 1 time for about 10 minutes, out of curiousity. So, do you still have root access? The only other thing I can recommend is to search the dev thread. I remember seeing a recent thread with an RUU that was flashable from recovery, no pc needed.
To answer your question, I doubt Sprint would need to access your recovery at the time of exchange, but later on in the repair facility is another story Hopefully someone else can chime in with more info. Good luck
Click to expand...
Click to collapse
So I thought it was Clockworkmod, but it was actually just the stock hboot I was looking at.
Anyway, she took the phone to the Sprint store, and they told her the phone could be repaired. I thought they were crazy, but she left the phone with them. When she came back a couple hours later, they told her they didn't have the parts in stock to repair the screen. So, they ordered her a new phone. We didn't have to pay the deductible, because they said it was under warranty.
Only bad part, when she went to pick up the "new" phone yesterday, it is actually a refurbished one. I rooted it, flashed the latest AOSP v0.9.9.2, and the phone acted kind of weird. Long texts wouldn't go through, and the signal was really bad at our house. So I just wiped, and flashed the AOSP v0.9.9.1 (which is what I have on my phone, and it works great), and am waiting for the market to install all of her apps again. We'll see if the issue was with the 0.9.9.2, or this "new" refurbished phone.

maddog808 said:
First of all I would like to say hi and thanks to everyone who contributes to this forum. You guys are pure genius!! I own 2 HTC Heros from Sprint. I use one, my wife uses the other one. We were both growing extremely frustrated with the Hero's laggy, almost unuseable Sense UI. So I started reading a bunch on the threads about rooting, Froyo, etc. I decided to give it a try. I used the "Easy Root" method posted by tehdarkknight located here. It worked!! So then I went ahead and installed ROM Manager, flashed clockworkmod recovery, and then did a nandroid. I then flashed AOSP v0.9.9.1-Froyo 2.2.1. Everything was working GREAT!! What a difference from Sprint's crapware loaded ROM. So I showed my wife, and she wanted it, too.
I got it all dialed in on her phone last night before bed, and she was digging it today. Then she dropped her phone (for the 1,000th time); only this time, the screen cracked and split in about 40 different spots. So I did a nandroid recovery, and undid the root per tehdarkknight's instructions. It seems stock, except that when I tried to let the latest Sprint OTA software update download & install, it failed, and the clockworkmod recovery screen showed up.
Finally, my question: Is this going to be a problem when I go in to have the phone replaced (we pay $7/month for insurance)? If so, what are the steps to get rid of the clockworkmod recovery, and make this Hero EXACTLY how it was before I started. Please go easy on me, I searched this forum, and Google in general, and couldn't find a definitive answer. I also tried to just install the HTC/Sprint RUU from their website, and it fails with a 171 code. Please help if you can. It will be greatly appreciated!!
Matt
Click to expand...
Click to collapse
Insurance covers damage to the phone's hardware. Whatever you do to the software is fine by them. If you can't unroot your phone, send it in and they'll send you a new one.

When I ran over mine and cracked the screen I just told Alltel that I lost it, for $95 I got a new one. Now I use the old one as a dedicated battery charger and ROM tester ETC
When my moms phone stopped receiving texts for no reason I told them we lost it and sold it to my neighbor for the insurance claim.
Also I don't think Sprint will care about the software since you're going in about physical damage.
I've already handed Alltel 2 bricked Hero's and told them I lost 2, I'm sure they love me hahahaha

So what happened when sprint told your neighbor "hey that's a lost phone! In fact the person who lost it might be your neighbor."
Sent from my HERO200 using XDA App

[Q] [info] - [I9000m] Bell Galaxy S Vibrant - internal SD failure

Hi Guys,
Here's some history on the phone:
- Purchased in Aug 2010, came withJK3 (not sure but it was ECLAIR)
- Since then the phone has been performing unbelievable, I had put several ROMs on the phone custom and stock as well as multiple kernels to fix battery drain, etc.
- A few days back after flashing Hamster's 6.3 ROM (which I had been using for a month prior, thus is completely irrelevant to my issue - find it here), I tried to access an app I had recently used when the phone completely froze on me, even power button would not respond; so I did a hard reboot only to be greeted by the cwm recovery window notifying me that the FS partition had changed and what I would like to do.
Knowing I had not changed anything, I simply picked "remove new configuration and boot phone"
Thats where I crapped my pants, the phone would reboot itself every 2 seconds and would not go past the first samsung boot screen.
I tried everything without luck, when finally 2 days later with special thanks to the following people listed below I found out exactly what's wrong with the phone and how to actually get to recovery and get a working boot on the phone.
I tried many many combinations of ROMs and kernels through ODIN and nothing seemed to work, initially I could get past the first boot screen if I re-partitioned with 512 and flashed JM8, but even that stopped working eventually. Finally late last night, I got the phone to boot. Here's what I did:
re-partition the phone with 803
Flash the phone with stock JLU (you will need the complete ROM with PDA, PHONE and CSC files)
Flash JPY
FLASH CF ROOT
FLASH SPEEDMOD kernel k12j
After the final step above you should have working recovery with adb for the first time! so now try the following umount commands and if they work then you are okay and do not have a dead sdcard/controller
Code:
umount /dev/block/mmcblk0p1
umount /dev/block/mmcblk0p2
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
Thanks to codeworkx for the above commands. If you try the above and they dont work or recovery shows the errors such as:
E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
or cannot mount SD card
then most likely you have either a bad internal SD or bad controller.
Regardless, your phone should now boot. if you can mount your SD card, you should do a complete format in windows after running the commands above; otherwise you still will not be able to access your internal SD and even though you can boot, your data will be lost after each boot and you cannot download anything from market or update current apps.
-------------------------------------------------------------
So now, I have a phone that boots up and works but cannot mount internal nor external SDs, here's the error dmesg gives in this regard, which again codeworkx helped me disect out of the logs:
Code:
"mmc0: error -110 whilst initialising MMC card"
I recently opened the phone up to try and see if I could find the location of the internal SD and to my surprise it only took 5 minutes and a little help from diagrams at phonewreck.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I know where the internal SD is, but no clue where the controller would be and whether its even possible to replace or any otherway to get the data back from the current internal SD which MAY still be okay in my case...
Any help with this would be appreciated - at this point im willing to try anything.
Thanks and if you have any questions feel free to ask.
People to note and thank for spending hours with me, walking me through what they know: virnik0, Jim_Panse, codeworkx, Josaatt, uppon2 & eitama - thanks guys!

that's what they do when you send it back in for repair
they just replaces the damaged PCB with the internal SD
usually error code 303 or 330 something like that

Just an update here.
My "Brand New" replacement from Bell - mk 10.11 just had the exact same failure as above, running stock 2.2 with absolutely no mods.
edit: phone came this way from bell/samsung | last thing I remember doing on it was loading google maps, then it started rebooting... and would boot up to JL2, and after 10 seconds of usability would reboot again... I could still see the internal and external SD... through recovery and adb, all the files were there...
after that happened, I decided its time to flash a custom rom, and at the first step (repartitioning + JM8/JM4) phone went to the infamous boot loop and thats that.

Did you upgrade to UGJL2 via kies prior to installing 2.2.1? If you didn't, or if you did it in odin without ticking "phone bootloader update", that's your problem. There's a problem with the I9000m 2.1 bootloaders wear control on the sd card. If that's not updated before going to any 2.2 or 2.2.1 firmware, you're phone is going to die.
Sent from my GT-I9000M using XDA App

I did not touch the phone, it came with GJL2 on it 2.2 - that's what I had on it.

@tekkneak,
Firstly... Your first phone that you bought in August did NOT have JL2 firmware on it as JL2 is a FroYo firmware and did not come out until late December 2010. The firmware you had on your first phone was probably JH2 which is Eclair.
I bought my i9000M in August 2010 (on the 30th of the month as a matter of fact) but mine came with JG9 Eclair and I had to upgrade to JH2.
This being said and since you mistyped the firmware version in your first post, are you sure that your NEW phone diddnt come with JH2 and NOT JL2? If this is the case then Electroz theory would hold true.
It has been said by both Bell and Samsung that the JL2 Froyo firmware has a new .SBL file that fixes the crashing internal SD cards.
This being said... IF your new phone did have JL2 FroYo on it and it crashed and gave you the internal sd card failure then I would say that for your phone it was a LEGIT hardware issue.

@yiannisthegreek I'm really not sure what came with my phone originally to be honest, back then I didn't think I'm going to have all these problems or I would have paid more attention to what was on the phone prior to me messing with custom ROMs. It DID have eclair, originally.
The new phone have Froyo I9000UGJL2 and I did everything I could to revive and many (listed above) helped with various methods which I have re-attempted with the recently deceased. It is indeed another Hardware failure, but WHY? shouldnt it have been fixed in the new versions??

tekkneak said:
@yiannisthegreek I'm really not sure what came with my phone originally to be honest, back then I didn't think I'm going to have all these problems or I would have paid more attention to what was on the phone prior to me messing with custom ROMs. It DID have eclair, originally.
The new phone have Froyo I9000UGJL2 and I did everything I could to revive and many (listed above) helped with various methods which I have re-attempted with the recently deceased. It is indeed another Hardware failure, but WHY? shouldnt it have been fixed in the new versions??
Click to expand...
Click to collapse
I feel where you are coming from for sure. Yes... You would think that these issues should have / would have been fixed by now but... The general concensus regarding failing internal sd cards is that the MAJORITY of the failures were due to a software issue and NOT a hardware issue. That being said, as I mentioned before... Bell and Samsung have stated that the JL2 Firmware with the new .SBL Bootloader File has fixed the "software" issue that was causing our devices to suffer internal SD failure so that is why I am assuming that your new phone may actually have fallen prey to a TRUE "hardware" failure in which case there is no remedy other than to have it replaced or repaired.
For example... Last night I had flashed my phone with a few different files and it "soft bricked" to the point where I was scared that it was my internal sd card too. It would hit the Samsung animation screen, vibrate once, go black screen with the buttons lit up then vibrate with three small bursts. I could go into recovery and download mode no problem and I did NOT see any error message in recovery so what I did is a Factory Reset from recovery and it rebooted just fine.
I lost my contacts and apps but not my phone. Perhaps try a Factory Reset from recovery and see what it does if you have not tried already.
In any case... I wish you luck...

tekkneak said:
@yiannisthegreek I'm really not sure what came with my phone originally to be honest, back then I didn't think I'm going to have all these problems or I would have paid more attention to what was on the phone prior to me messing with custom ROMs. It DID have eclair, originally.
The new phone have Froyo I9000UGJL2 and I did everything I could to revive and many (listed above) helped with various methods which I have re-attempted with the recently deceased. It is indeed another Hardware failure, but WHY? shouldnt it have been fixed in the new versions??
Click to expand...
Click to collapse
It's probable that whoever update the phone to UGJL2 just forgot to hit the Phone Bootloader update option in Odin as well. After all, Odin is Samsung software released to their tech's. So, something that simple could have done it.
As one last chance, download UGJH2 and UGJL2 from Samfirmware.com and use Odin 1.7, no pit, no repartition.
Flash UGJH2 first, without bootloader update is fine..
Then, after that is flashed, go ahead and flash UGJL2. Make sure to click Phone Bootloader update.
Give that a try and see if it comes back to life.

Hi guys, I'm having the same issue that tekkneak is having, i was able to get mine to reboot with UGJL2 but I had to add the Speedmod-k12j-256hz Kernel. If i dont add the speedmod, the phone will either go into the boot loop or boot past the splash screen and then just give me the black screen with the lit up buttons.
When I boot now I dont seem to have any sort of memory space available, It says 0.0B available and i am unable to format the internal SD card and/or mount an external SD.
I've tried loading UGJH2 and then UGJL2 with bootloader update but like i said before if i dont load the speedmod kernel it will not boot.
Any ideas?

packers17-0 said:
Hi guys, I'm having the same issue that tekkneak is having, i was able to get mine to reboot with UGJL2 but I had to add the Speedmod-k12j-256hz Kernel. If i dont add the speedmod, the phone will either go into the boot loop or boot past the splash screen and then just give me the black screen with the lit up buttons.
When I boot now I dont seem to have any sort of memory space available, It says 0.0B available and i am unable to format the internal SD card and/or mount an external SD.
I've tried loading UGJH2 and then UGJL2 with bootloader update but like i said before if i dont load the speedmod kernel it will not boot.
Any ideas?
Click to expand...
Click to collapse
What error are you getting in recovery?

Samdroid_G_S said:
What error are you getting in recovery?
Click to expand...
Click to collapse
When i run the report error option in the "advanced ClockWorkMod features" i get this:
"E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0"
I've been reading that some people have been able to mount and or format their internal sd cards by using the adb console but I'm not really too familiar on how to do this. Anyone had any luck fixing this?

packers17-0
though that was not the final score, I would like to congratulate on you the win.
If you are getting that error, and you have tried the commands through adb on my first post without luck, then you have either a bad internal memory or a bad controller and will need to seek warranty options.
tekky

tekkneak said:
packers17-0
though that was not the final score, I would like to congratulate on you the win.
If you are getting that error, and you have tried the commands through adb on my first post without luck, then you have either a bad internal memory or a bad controller and will need to seek warranty options.
tekky
Click to expand...
Click to collapse
Haha Thanks! the 17-0 was supposed to be the season record but I must not have been thinking cuz there can't be a 17-0 regular season record - or at least not yet...
I think I may be out of luck on this as I do not have a bill of sale for this device. It was actually given to me by my work to test out user experience on our new network and I'm not sure where it was purchased from or how they got it. I also have a feeling that if i send it back to them I will not see it again or it will be traded for a lesser phone.
Any idea if Samsung will service it without a bill of sale? could they just go by the manufacture date maybe?
Thanks

Yes, they will accept it, I did not have it for my phone, they checked when it was sold on their system and said I still had 7 months of warranty left.
Tekky
packers17-0 said:
Haha Thanks! the 17-0 was supposed to be the season record but I must not have been thinking cuz there can't be a 17-0 regular season record - or at least not yet...
I think I may be out of luck on this as I do not have a bill of sale for this device. It was actually given to me by my work to test out user experience on our new network and I'm not sure where it was purchased from or how they got it. I also have a feeling that if i send it back to them I will not see it again or it will be traded for a lesser phone.
Any idea if Samsung will service it without a bill of sale? could they just go by the manufacture date maybe?
Thanks
Click to expand...
Click to collapse

[Q] Need help rooting kindle fire HD 7.30

I have rooted many devices in the past but my kindle fire HD has had me running in circles for months! I keep downloading files, but nothing works! I have the adb drivers downloaded and they are working, but that's as far as I can get. Any advice/ help would be greatly appreciated.

finzzzup said:
I have rooted many devices in the past but my kindle fire HD has had me running in circles for months! I keep downloading files, but nothing works! I have the adb drivers downloaded and they are working, but that's as far as I can get. Any advice/ help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2069117
Do you have a 64-bit computer by the way?

Protomartyr said:
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2069117
Do you have a 64-bit computer by the way?
Click to expand...
Click to collapse
I'm at crossroads too. Getting error "A server error has occurred. Retry or cancel and return to the previous screen." when launching Market App. Also, Root Check Freezes - black screen.

How do I Remove files in [xbin] folder from Failed [Root] attempts?
Okay, first time [Rooting] , I recently rooted my kindle HD 7, and yesterday my SU is no longer in its folder and my system appears semi wiped. I say semi because i have a ' Google market apk' that doesn't work and a apex launcher which still works somehow now embedded in the factory settings. That's one issue, the other is well, I tried a number of things, factory reset, fastboot with firstaide32, and reroot, but and they dont disappear and now when i try to do shell commands to the xbin folder I get this error, " cannot copy or install files to /system/xbin folder is full on device". Im stumped. How do i wipe the xbin folder so i can root again? Im still fresh to the linux coding commands.
Thank you to anyone with some insight.:confused
MadSkillz269

I got it working but can't exactly remember how
Sent from my KFTT using Tapatalk 2

ugh, this whole 7.3.0 thing is a disaster. i really screwed the pooch, thought i had blocked ota updates but i guess it didnt work. now my kindle wont connect properly to any of my pc's, all drivers i try install as unknown device. i just dont get it. i had such an easy time rooting it originally. anyone having a similar issue?
if i cant root this thing again im probably going to just use my new nail gun on it and go buy a nexus. i really hate the stock rom.

Do you have a factory cable?

soupmagnet said:
Do you have a factory cable?
Click to expand...
Click to collapse
if its gonna take a factory cable to maybe fix it then who wants to buy a 2 month old kindle?

I give 5 dolla
Sent from my GT-P3110 using xda app-developers app

mr.bobharris said:
if its gonna take a factory cable to maybe fix it then who wants to buy a 2 month old kindle?
Click to expand...
Click to collapse
I'll buy it, for the price of a factory cable.
You could always make one yourself...

http://forum.xda-developers.com/showthread.php?p=39569189
How to make one
Sent from my GT-P3110 using xda app-developers app

For me after weeks of searching believe I found the answer. When I first rooted my KFTT 7.2.3 it went smoothly. When it updated the same process wasn't working even though others on this site said it should. (Method used was Root with restore and Qemu Root) After receiving many ADB push errors and permission errors I decided to do a complete restore after reading a suggestion somewhere on the internet. I was hesitant to do this because I could not back up my app data and my Fruit Ninja high scores would be wiped, but I needed root to make my launcher wallpapers work. So I charged up my Kindle to 45% (40% required for restoring) and restored. Then I went to the rooting tool on my PC and presto not a single failed adb push in sight. All it needed was a little restore. Although RIP my poor hoghscores :crying:

its more about the effort-to-enjoyment ratio. i dont like the device enough to warrant the effort of getting it to work the way i want. it was free, so whatever i sell it for is free money to put towards a better device.
ive tried a restore and lost all my scrabble scores and games, but it did nothing for me. every pc in my house decided the kindle is now an unknown device, even when i install the adb drivers. ive tried deleting phantom installs, ive tried every tip in this forum, and nothing is working. thats why im giving up, its not for lack of trying or anything.

called amazon today, apparently theres a known bug theyre working on. 7.3.1 addresses some of them, but did not work for me. i was told another update is coming out within the next few weeks to fix all known bugs. they were very attentive and had me list all bugs im noticing, the first guy i talked to seemed happy to be dealing with someone who can spell usb, so he pumped me for info. i told him what drivers ive tried, how i switch to test mode, disable diver sig verification, etc...
the first call ended when i had to wait for 7.3.1 to dl and install by pressing sync. called back after the update didnt change anything and theyre replacing it. i'll have a new one in 2 days. you cant beat that kind of service imo. im gonna give the device a second chance simply because ive now seen how firmly theyre behind it, and because their customer service system is wonderfully painless.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_sib?ie=UTF8&nodeId=201016350

got the new one today. came with 7.3.1. plugged it in, rooted it, it works great. i dont know wtf happened to the old one.

[Q] AT&T stock rom reboot issue? any fix?

Hi all,
I am on AT&T ICS stock rom. Is there any solution to fix the random reboot issue? It is a real pain when you pick up the phone and find it is rebooting...
The phone will randomly reboot. It is totally random, it may happen 3 times a day or 1 time a week, it may happen when you are using it or in your pocket, and I can tell when I see a system message coming up: your phone is recovered from an error. I am really frustrated...
I searched on the forum but found no clue to fix it... Please help!
PS: I flashed CM10 and the in call volume issue bothers me. It is a perfect rom otherwise.
Thanks!

friedenhe said:
Hi all,
I am on AT&T ICS stock rom. Is there any solution to fix the random reboot issue? It is a real pain when you pick up the phone and find it is rebooting...
The phone will randomly reboot. It is totally random, it may happen 3 times a day or 1 time a week, it may happen when you are using it or in your pocket, and I can tell when I see a system message coming up: your phone is recovered from an error. I am really frustrated...
I searched on the forum but found no clue to fix it... Please help!
PS: I flashed CM10 and the in call volume issue bothers me. It is a perfect rom otherwise.
Thanks!
Click to expand...
Click to collapse
Did you flash from the RUU?

friedenhe said:
Hi all,
I am on AT&T ICS stock rom. Is there any solution to fix the random reboot issue? It is a real pain when you pick up the phone and find it is rebooting...
The phone will randomly reboot. It is totally random, it may happen 3 times a day or 1 time a week, it may happen when you are using it or in your pocket, and I can tell when I see a system message coming up: your phone is recovered from an error. I am really frustrated...
I searched on the forum but found no clue to fix it... Please help!
PS: I flashed CM10 and the in call volume issue bothers me. It is a perfect rom otherwise.
Thanks!
Click to expand...
Click to collapse
Check your software you install on your phone.

Orizence said:
Did you flash from the RUU?
Click to expand...
Click to collapse
Yes, I flashed from the RUU.
Actually, I got this phone and found the reboot issue, (ATT ship rom). So I flashed RUU and found the reboot issue is still here.
So you guys have no reboot issue on RUU rom?
Thanks

ktt9854 said:
Check your software you install on your phone.
Click to expand...
Click to collapse
I think it might not be the apps.
One extreme case, right after I flashed the RUU rom, I found the signal is a little poor so I turned on airplane mode and then off, once I did that, the phone rebooted... (no any app installed)

friedenhe said:
I think it might not be the apps.
One extreme case, right after I flashed the RUU rom, I found the signal is a little poor so I turned on airplane mode and then off, once I did that, the phone rebooted... (no any app installed)
Click to expand...
Click to collapse
You can try flash ROM here: http://forum.xda-developers.com/showthread.php?t=1631499 or here http://forum.xda-developers.com/showthread.php?t=1585373.
If your problem doesn't solve please check your hardware. I think you have trouble with your hardware.

The at&t stock rom is trash. So many issues. I flashed albinoman's cm 10.1 rom and have never looked back. I just use the speakerphone and put it against my ear backwards if I can't hear during a call. I'd rather do that then deal with the constant freezes and reboots (with 5-10 minute reboot time).

friedenhe said:
Hi all,
I am on AT&T ICS stock rom. Is there any solution to fix the random reboot issue? It is a real pain when you pick up the phone and find it is rebooting...
The phone will randomly reboot. It is totally random, it may happen 3 times a day or 1 time a week, it may happen when you are using it or in your pocket, and I can tell when I see a system message coming up: your phone is recovered from an error. I am really frustrated...
I searched on the forum but found no clue to fix it... Please help!
PS: I flashed CM10 and the in call volume issue bothers me. It is a perfect rom otherwise.
Thanks!
Click to expand...
Click to collapse
Why not try the Bell Canada RUU ? Are you S-Off ? You may have to be to flash the radio firmware, but if you're super-cid then the phone should accept a ROM from any carrier. See the attached instructions re: super-cid.
Bell has a few advantages right out of the box: tethering works, so does wifi hotspot.
You can try flashing it with super-cid but S-ON and see if it errors out. The AT&T radio should work just fine with the Bell firmware, unless someone can advise otherwise.
Rather than saying "4G", it will show "LTE" and there's some Bell bloatware installed which can safely be removed after you root again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Spazmogen said:
Why not try the Bell Canada RUU ? Are you S-Off ? You may have to be to flash the radio firmware, but if you're super-cid then the phone should accept a ROM from any carrier. See the attached instructions re: super-cid.
Bell has a few advantages right out of the box: tethering works, so does wifi hotspot.
You can try flashing it with super-cid but S-ON and see if it errors out. The AT&T radio should work just fine with the Bell firmware, unless someone can advise otherwise.
Rather than saying "4G", it will show "LTE" and there's some Bell bloatware installed which can safely be removed after you root again.
Click to expand...
Click to collapse
Spaz... Your PDF talks about clockworkmod... A vivid nono...
Sent from my Vivid 4G using Tapatalk 4

I've done the process with WCX already installed.
Just start from Step 4: Write Super CID if you already have a recovery installed. As mentioned in the post above, CWM does not play nice with the Vivid/Raider.
The .pdf is just a file I created from the thread here on XDA (search is down again) which I cannot locate. I am not the author of the post.
Also to note: The Bell RUU is ICS (official) and does not have the call drop issue that seems to plague the CM roms, but it is not as striking as the CM roms either.