Database Info

[q] screen of death on froyo :(

So this morning I was checking out the new choices in my Froyo leak - rooted Captivate, I clicked on every one of them to see what it is and then I clicked on one that said something like user accounts, well ever since then my phone has been a black screen only displaying the top clock and a no signal bar. What should I do next? Unfortunately Im stuck at work with no programs. So Im wondering what would you do, which Odin should I use? Ill be checkin in cause at least I can do this and plan fixing my phone for later

Im guessing you tried pulling the battery?
Sent from my SAMSUNG-SGH-I897 using XDA App

sure did tried the reboot screen.

and the other thing, now the phone wont go into sleep mode so my battery is slowly dying too

try to boot into recovery and clear out the cache...

I did that too and it clears and then i reboot then it goes right back to black screen

The same thing happened to me, but I wasn't digging around in the settings. Like previously mentioned, I booted into recovery, and cleared cache/factory wipe, and it booted back fresh. Luckily, I had a Titanium Backup from a few hours before it happened, so I didn't really lose anything.

I had something like this too. Can you get into Download mode and use Odin to return to stock rom? It took me several tries before Odin worked.

Well I still haven't heard anyone who has completely bricked there samsung captivate yet so I think you'll be alright. Just to be the 1 click Odin when you get home.
I'm pretty new myself at this But I think the only way were really screwed Is if we kill the bootloader.
Sent from my SAMSUNG-SGH-I897 using XDA App

i will try when i get home, im stuck at work unfortunately, at least i know im not the only one, i was also fooling with settings

thank you

Theres been a few people that have fully bricked their captivates... Including me.
If you got your captivate within the last couple weeks be careful using odin with a froyo kernel. Check the Q&A thread for a post titled "phone-pc something" (Using my phone otherwise I'd provide a link)

loserskater said:
Theres been a few people that have fully bricked their captivates... Including me.
If you got your captivate within the last couple weeks be careful using odin with a froyo kernel. Check the Q&A thread for a post titled "phone-pc something" (Using my phone otherwise I'd provide a link)
Click to expand...
Click to collapse
Well that sucks.
Sent from my SAMSUNG-SGH-I897 using XDA App

theMaginator said:
Well I still haven't heard anyone who has completely bricked there samsung captivate yet so I think you'll be alright. Just to be the 1 click Odin when you get home.
I'm pretty new myself at this But I think the only way were really screwed Is if we kill the bootloader.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I had one. OTA update. And I wasn't the only one. I couldn't even get into download mode.

yeah, bricked here too trying to go to Froyo. Sent to Samsung, they fixed it.

theMaginator said:
Well I still haven't heard anyone who has completely bricked there samsung captivate yet so I think you'll be alright. Just to be the 1 click Odin when you get home.
I'm pretty new myself at this But I think the only way were really screwed Is if we kill the bootloader.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
lol its happened to many people, myself included.

Damnit, Tmobile

MyTouch 4g, perm-rooted, S-OFF. I pushed a custom kernel (for overclocking). The device is fine. T-mobile tried to push an update (which kept nagging me), so I eventually applied it. When I did it failed to reboot. Good job, T-mobile.
That would have been fine except that I also had to return the computer I did this all on to work. I've created a new system and ADB only appears to detect the device when it's in recovery mode. I'm running gentoo, so I had to hack the udev rules myself. The identifiers match lsusb, but recovery is the only time I don't get a blank console under "List of devices attached".
/etc/udev/rules.d/50-android.rules
SUBSYSTEMS=="usb, ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c94", OWNER=="poseidon1157" #Normal
SUBSYSTEMS=="usb, ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c96", OWNER=="poseidon1157" #Recovery
SUBSYSTEMS=="usb, ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", OWNER=="poseidon1157" #Fastboot
lsusb:
Bus 001 Device 018: ID 0bb4:0fff High Tech Computer Corp.
OR
Bus 001 Device 018: ID 0bb4:0c94 High Tech Computer Corp.
OR
Bus 001 Device 018: ID 0bb4:0c96 High Tech Computer Corp.
In recovery mode:
List of devices attached
HT0... recovery
else
List of devices attached
So wtf?
Ultimately I want to push cyanogenmod to the phone, but I can't do that very well if it's not detecting the phone.
Please help. I really need that thing. Both for work and for my personal life.

I forgot that you use a separate fastboot binary. Looking for that now. Did they remove that from the default sdk?

poseidon1157 said:
MyTouch 4g, perm-rooted, S-OFF. I pushed a custom kernel (for overclocking). The device is fine. T-mobile tried to push an update (which kept nagging me), so I eventually applied it. When I did it failed to reboot. Good job, T-mobile.
Click to expand...
Click to collapse
Um, you blame T-Mobile for hacking your phone and then f***ing it up by applying a stock update to a non-stock phone? What was the update, 2.2.1? What kernel did you have on it? Anything other than a custom kernel?
Try applying this in Recovery.

This is T-Mobile's fault how? You failed, not them. Thumbs down to you.

Part Four said:
This is T-Mobile's fault how? You failed, not them. Thumbs down to you.
Click to expand...
Click to collapse
+ Juan to this post.
if you can get into recovery just do a nandroid restore.
if you can still get into Bootloader store the PD15IMG and start over fresh.

Wow most ppl complain about tmo not sending out updates! This is a first!
Sent from my HTC Glacier

lisap006 said:
Wow most ppl complain about tmo not sending out updates! This is a first!
Sent from my HTC Glacier
Click to expand...
Click to collapse
Lmfao so so tru
CM7 wtf else....

lisap006 said:
Wow most ppl complain about tmo not sending out updates! This is a first!
Sent from my HTC Glacier
Click to expand...
Click to collapse
Good point! another reason to rename this thread "Damnit, my own hands..."

Figures. I post a technical problem and everyone chimes in on something I said while frustrated. Not the problem. Thank you very much setzer for the recommended fix.
Personally, I would greatly appreciate it if none of the rest of you replied to my posts. Ever. Again.
And for the record you're right, I shouldn't have applied the update. Repeated attempts to find the update file failed, the notification stayed there, and my clockworkmod backup apparently disappeared with my photos and media and so I was stuck with a system I couldn't recover.

So did it work? I am not sure why you applied it in first place as most do warn and why would people accept stock OTA on custom setup is beyond me. Hopefully it works by restoring the PD15IMG or you have to social TMo to get replacement.
Sent from my HTC Glacier

Hey guys, is there a way to turn off system updates so this doesn't happen to me when my girlfriend had my phone lol.
Sent from my HTC Glacier using XDA App

Essenar said:
Hey guys, is there a way to turn off system updates so this doesn't happen to me when my girlfriend had my phone lol.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
honestly wait till after the update has been pushed to mess with the phone.
just call T-Mobile, tell them you haven't seen the update and they can push the update to you.
the other option you have is do a nandroid back up of the OS in the rooted stated, then unroot and turn s=on Do the update, re-root then flash the nandroid back up. and you are good to go.
I called T-Mobile and they cannot prevent the system from pushing the update notification to your phone.
poseidon1157 said:
Figures. I post a technical problem and everyone chimes in on something I said while frustrated. Not the problem. Thank you very much setzer for the recommended fix.
Personally, I would greatly appreciate it if none of the rest of you replied to my posts. Ever. Again.
And for the record you're right, I shouldn't have applied the update. Repeated attempts to find the update file failed, the notification stayed there, and my clockworkmod backup apparently disappeared with my photos and media and so I was stuck with a system I couldn't recover.
Click to expand...
Click to collapse
hold on there slick, i did provide insight full information. It's a simple mistake to make, but it's not 100% T-Mobile fault. infact it's not that fault at a 1% level.

Flashed recovery
For other idiots besides myself who think that custom stock-based kernels could be compatible with the update: they are not.
I did get this fixed. Personally I'm more comfortable with fastboot than I am with adb (no command-line completion, and imho it's the appropriate tool). After flashing clockwork recovery:
fastboot erase recovery&&fastboot flash recovery ${fastboot_location};
You can subsequentially mount it as a usb device (through recovery > mount... > USB). Copying a zip is necessary because (to my knowledge) tools to package the directories directly into a .img for fastboot have yet to be written.
Running a relatively stable cyanogenmod 7 nightly #18 with IMT/BT/GPS/SCCP. 801.11 drivers aren't working just yet. I might check through the git to see if there are pertinent commits.

Agreed
Hopefully you got it to work....
Sent from my HTC Glacier using XDA App

poseidon1157 said:
Figures. I post a technical problem and everyone chimes in on something I said while frustrated. Not the problem. Thank you very much setzer for the recommended fix.
Click to expand...
Click to collapse
Yeah, I guess your right, everyone did focus on that part, but it was the first thing you said. And you have to admit that the way your wrote your post you blamed TMO for messing up your phone. To most, that just seems stupid as it wasn't TMO that did anything wrong. All they did was try to push an update.
I'm sorry you had an issue, but you should have started out saying YOU messed something up. It's like having someone else root your phone and they say, "I'll try but there is a chance it will brick". And you saying, "it's cool dude, just give it a shot". Then when it bricks you blame them even after the warning.
Sorry, just trying to point out why everyone here thinks your post is lame. Please don't take offense to everyone, just realize that you blamed someone else for your OWN mistakes and then expect everyone to 'read your mind' and KNOW it was because you were frustrated.

I've just done a cleanup of the thread and had to remove half of the posts. I suggest if you have nothing helpful to say, please don't post at all.

On the edge about installing roms. Is it a risk?

Here's my delimma...
After a huge ordeal with Verizon I managed to get myself an early upgrade to this s3.
Part of that deal was that I accept the best equipment protection they have so next time they won't deal with me asking for another early upgrade.
That being said I love stock Android... I tried to use touchwiz and although I'm sure it's fine for some I can't get behind it.
Does rooting and flashing ever really bother me? No... But the flash counter I've been reading about does.
I can with almost 100% certainty tell you that I will end up doing a warranty claim on this device, and at which point I may get rejected due to software.
I've read the methods of getting the flash count back to zero or stock. How reliable are these?
I hope I don't come off as too paranoid.
Thx in advance!
Sent from my SCH-I535 using xda app-developers app

stevenjcampbell said:
I can with almost 100% certainty tell you that I will end up doing a warranty claim on this device, and at which point I may get rejected due to software.
Click to expand...
Click to collapse
Wait until after, if you're so sure.
The only time I've ever heard of the flash counter even being accessed was when a device was sent directly back to Samsung from the user.
There is of course a risk. Some have lost their IMEI. We can recovery that now, but some have been stuck on roaming indefinitely with no fix.
I have no idea if the flash counter resets actually work for this device or not, though. These forums are filled with lots of information (such as the old IMEI recovery thread that was unreliable and could not recover from an IMEI=0).

ExodusC said:
Wait until after, if you're so sure.
The only time I've ever heard of the flash counter even being accessed was when a device was sent directly back to Samsung from the user.
There is of course a risk. Some have lost their IMEI. We can recovery that now, but some have been stuck on roaming indefinitely with no fix.
I have no idea if the flash counter resets actually work for this device or not, though. These forums are filled with lots of information (such as the old IMEI recovery thread that was unreliable and could not recover from an IMEI=0).
Click to expand...
Click to collapse
Well, I as hard as I am on devices I mean. I'm using it heavy, plus the circumstances ibusenit such as gum hiking etc.
Seems that I will have to risk it. if software there is always a fix it seems...
Sent from my SCH-I535 using xda app-developers app

stevenjcampbell said:
Well, I as hard as I am on devices I mean. I'm using it heavy, plus the circumstances ibusenit such as gum hiking etc.
Seems that I will have to risk it. if software there is always a fix it seems...
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
yep pretty much just follow the instructions to the t, always take your time when flashing brand new rom like reading over the threads to see the problem and always make a backup. Yes the reset flash counter thing works i've had to send in a s3 due to the charging port and haven't been denied of my warranty. At the end of the day their is always a risk that your problem will be hardware related but that's a very slim chance. Other than that you should be good to go I've never had a problem other than now and this my third rooted phone.

joka10 said:
yep pretty much just follow the instructions to the t, always take your time when flashing brand new rom like reading over the threads to see the problem and always make a backup. Yes the reset flash counter thing works i've had to send in a s3 due to the charging port and haven't been denied of my warranty. At the end of the day their is always a risk that your problem will be hardware related but that's a very slim chance. Other than that you should be good to go I've never had a problem other than now and this my third rooted phone.
Click to expand...
Click to collapse
Okay thank you. I loved paranoid android rom on the incredible 2 but it had no camera support. Looking forward to see what this could do with it!!
What method to reset flash count did you use? The model number of my current device is SCH-I535 whereas the model in the triangle app is always i9300.
Sent from my SCH-I535 using xda app-developers app

stevenjcampbell said:
Okay thank you. I loved paranoid android rom on the incredible 2 but it had no camera support. Looking forward to see what this could do with it!!
What method to reset flash count did you use? The model number of my current device is SCH-I535 whereas the model in the triangle app is always i9300.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used the adb one where you type in
1.)adb devices (should a number if you set it up right)
2.) adb shell
3.) su
4.) echo -n '\x00' | dd obs=1 count=1 seek=4193796 of=/dev/block/mmcblk0
but if your not comfortable with adb then triangle away works but i forget if you have to change anything

joka10 said:
I used the adb one where you type in
1.)adb devices (should a number if you set it up right)
2.) adb shell
3.) su
4.) echo -n '\x00' | dd obs=1 count=1 seek=4193796 of=/dev/block/mmcblk0
but if your not comfortable with adb then triangle away works but i forget if you have to change anything
Click to expand...
Click to collapse
No I'm okay with command prompts. I assume that
1) adb is something installed on my pc
2) these commands are done via a cmd prompt with admin permissions.
I can Google how to install adb android... Not worried there.
When I can get back to a pc ill be sure to thank you proper.
Sent from my SCH-I535 using xda app-developers app

I just came to Android after 5 years of running Blackberry (Storm,Storm 2, 9850) which were all keyboard-less BB. I knew them inside out, was creating my own OS mods and could pretty much create (within Blackberry reason) anything I wanted in it. Android is COMPLETELY different, but with a lot of reading and the great Devs within the community, I got it rather quickly and am running a custom rom with a modified kernel, while adding some MOD zips to get even more customizations to my liking. All that said, if you spend just a little time reading through the 101 of rooting and getting back to stock, you'll be just fine. I've flashed 15 times already, trying just about everything out there to get a look and to also get familiar with the how to and what if process. My counter never changed from "0". And if it would have, I am confident after reading throughout here at I could get that back to factory very easily.

[Q] I think my phone is bricked

as title states hard bricked after install of orthus eight then rebooted and nothing. followed instructions and still bricked. i have flashed many roms i don't know what went wrong with this flash. Will a jig work to unbrick to download mode? I have tried several methods to get into download and cant seem to succeed.

Re: [Q] Orthus eight hard bricked phone
I don't think the rom had anything to do with it. I've flashed it and it's fine.
What was the best thing before sliced bread?

baddogie said:
as title states hard bricked after install of orthus eight then rebooted and nothing. followed instructions and still bricked. i have flashed many roms i don't know what went wrong with this flash. Will a jig work to unbrick to download mode? I have tried several methods to get into download and cant seem to succeed.
Click to expand...
Click to collapse
What exactly did you do? And don't just say, "I followed the instructions." I need to know exactly what you did every step of the way from downloading Orthus Eight to laying the cornerstone of your new brick house.
I'll ask this first obvious question because so often it reveals the true problem: what kind of phone do you have?

Lets not go straight in to flaming a user just because he has no posts. I know for a fact there is a brick problem in AOSP 4.2.2. Lets hear him out.

baddogie said:
Will a jig work to unbrick to download mode?
Click to expand...
Click to collapse
I'm not an expert but if you really hard brick the phone then jig would be your solution.
You may want to read the posts on "[ROM][10.1]SUPERLITE CM10.1 JB 4.2.2 > 79mb < | SLGAPPS 10MB | FEB28/13" page 2 and 3 and try to get in touch with the user who bricked the phone and was going to try "JTAG brick repair"
BTW I also installed the ROM and is working smooth.
P.S. I don't think anyone is blaming Ortus8 ROM while the question ... and request for support ... was regarding jig

Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
Lets not go straight in to flaming a user just because he has no posts. I know for a fact there is a brick problem in AOSP 4.2.2. Lets hear him out.
Click to expand...
Click to collapse
A Randomly appearing brick that only affects some and not others this i want proof of sir mod or not i want validation.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 05:28 AM ---------- Previous post was at 05:27 AM ----------
err1max1 said:
I'm not an expert but if you really hard brick the phone then jig would be your solution.
You may want to read the posts on "[ROM][10.1]SUPERLITE CM10.1 JB 4.2.2 > 79mb < | SLGAPPS 10MB | FEB28/13" page 2 and 3 and try to get in touch with the user who bricked the phone and was going to try "JTAG brick repair"
BTW I also installed the ROM and is working smooth.
P.S. I don't think anyone is blaming Ortus8 ROM while the question ... and request for support ... was regarding jig
Click to expand...
Click to collapse
A jig does nothing for a hard brick. You don't need a jig to get to DL mode if soft brick. In short a jig is worthless.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mtdew said:
A Randomly appearing brick that only affects some and not others this i want proof of sir mod or not i want validation.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 05:28 AM ---------- Previous post was at 05:27 AM ----------
A jig does nothing for a hard brick. You don't need a jig to get to DL mode if soft brick. In short a jig is worthless.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
In my opinion it has to do with the kernel, course I could be wrong. However I had 2 testers brick with CM's kernel. I've seen similar reports with the 4.2.2 AOKP around here. In the 2 cases I'm sure the phone booted and ran fine, then randomly locked up and dead. No life afterwards. I understand we all make mistake by both my testers where doing something different when it happen, and the fact the device booted fine THEN bricked (again my particular case) means it flashed fine and whole booted something happen (I believe it blew partitions, possibly secondary or third, if this device has a third, bootloader). If I had any better proof I would have found a solution, or tried to already.

Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
In my opinion it has to do with the kernel, course I could be wrong. However I had 2 testers brick with CM's kernel. I've seen similar reports with the 4.2.2 AOKP around here. In the 2 cases I'm sure the phone booted and ran fine, then randomly locked up and dead. No life afterwards. I understand we all make mistake by both my testers where doing something different when it happen, and the fact the device booted fine THEN bricked (again my particular case) means it flashed fine and whole booted something happen (I believe it blew partitions, possibly secondary or third, if this device has a third, bootloader). If I had any better proof I would have found a solution, or tried to already.
Click to expand...
Click to collapse
I find it hard to believe this was random or attributed to to cm's kernel if nothing else it would be based on something particular to their hardware or your build as you would see a ton of these on cm's thread. You are placing blame in an unlikely place as well.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
mtdew said:
I find it hard to believe this was random or attributed to to cm's kernel if nothing else it would be based on something particular to their hardware or your build as you would see a ton of these on cm's thread. You are placing blame in an unlikely place as well.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Well I was using cms device folders and my qcom hardware folders are constabtly updated with cms commits. Only difference are overlays files and that we use slim.mk which is mostly a copied cm.mk only fixed source locations. Don't know what I did different to create a brick zip. Not my first rodeo, though I'm no expert that's for sure.
Sent from my Nexus 4 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
Well I was using cms device folders and my qcom hardware folders are constabtly updated with cms commits. Only difference are overlays files and that we use slim.mk which is mostly a copied cm.mk only fixed source locations. Don't know what I did different to create a brick zip. Not my first rodeo, though I'm no expert that's for sure.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Again if it was cm's doing this would be far more widespread. Something's not adding up, also several people have successfully flashed orthus this is user error nothing more.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mtdew said:
Again if it was cm's doing this would be far more widespread. Something's not adding up, also several people have successfully flashed orthus this is user error nothing more.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Mate Tell me something I don't know. Same thing with Slim. My test builds where flashed by 50+ people only 2 bricked, so happen both I had most communication with as they where helping me debug the camera problem I had. Like I said if I had a better idea of where the problem laid I wouldn't have stopped working with it (I still fiddle with the code) I just don't have any concrete evidence to work with to merit the chance of bricking other members devices. I originally thought it was me but not the case. There has been posts about this happening on AOKP, I believe on CM (not sure if it was here or not). I'm not saying its a wide spread problem, however its there.

Re: [Q] Orthus eight hard bricked phone
Aokp for this device? Cm for this device? Were the members who bricked very experienced? I'm not saying you don't know what you're talking about but i never trust testers and i especially don't trust people saying such and such ROM bricked my device. I've seen this all too often and all it does is spread fear and give good devs bad names.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
Just as an fyi, I loaded Orthus onto my skyrocket just now. Booted fine, restoring apps now
Sent from my SGH-I317 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
Been running it since it dropped absolutely no issues smoothest 4.2.2 ROM out.
Sent from my SGH-I727 using xda premium

Re: [Q] Orthus eight hard bricked phone
I'd love to try and help this user.
What methods have you tried to get into download mode?
You said you can reboot, then get nothing. Is that a blank screen? Does the backlight come on?
What recovery were you on? What steps to flash?
Can you get to the device via adb?
Even if I can't help you, maybe we can narrow down the issue.. Whatever it may be.
Sent from my SGH-I727 using Tapatalk 2

damn another brick bug, i thought it was all done with
as for blaming the op, if he had the sr and flashed an sr rom whichever rom that would be, we cant blame the op since theres nothing he could do wrong to actually hardbrick the phone , yes he could softbrick but not hardbrick it.
definition of the bug imo is its totally random, 1 out of x phones it will happen to

T.J. Bender said:
What exactly did you do? And don't just say, "I followed the instructions." I need to know exactly what you did every step of the way from downloading Orthus Eight to laying the cornerstone of your new brick house.
I'll ask this first obvious question because so often it reveals the true problem: what kind of phone do you have?
Click to expand...
Click to collapse
I have a samsung galaxy s2 skyrocket sigh i727. I downloaded the rom from the forums here (i think the link was goo.im) and transfered to my internal sd. I wiped data factory reset, wiped cache patroon, wiped system, wiped delvil cache then flash downloaded zip and half way through the android in background fell over and triangle showed up. I tried restoring backups and eving wiping did not work so I went to advance and restart recovery and the device turned off and now will not respond to anything.

Re: [Q] Orthus eight hard bricked phone
Be careful with goo. I've never been sure what I've downloaded from it.
Most likely not a problem with the rom.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

mtdew said:
Aokp for this device? Cm for this device? Were the members who bricked very experienced? I'm not saying you don't know what you're talking about but i never trust testers and i especially don't trust people saying such and such ROM bricked my device. I've seen this all too often and all it does is spread fear and give good devs bad names.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I'm not trying to give any dev a bad name I was just trying to specify what rom I was flashing when this happend

baddogie said:
I have a samsung galaxy s2 skyrocket sigh i727. I downloaded the rom from the forums here (i think the link was goo.im) and transfered to my internal sd. I wiped data factory reset, wiped cache patroon, wiped system, wiped delvil cache then flash downloaded zip and half way through the android in background fell over and triangle showed up. I tried restoring backups and eving wiping did not work so I went to advance and restart recovery and the device turned off and now will not respond to anything.
Click to expand...
Click to collapse
OK. Moving the file from external to internal could cause a corruption. It could have been a bad DL from the start. Hence the reason checking MD5s is so imortant. Either way you should still be able to enter recovery. No ROM that is flashable touches the recovery partition. Pull out your external sdcard and access it with a comp. Copy that files full name here.

[Q] Hard Bricked? Don't see how....

Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan

ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?

Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app

exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!

ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.

mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.

ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app

ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...

mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.

pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.

mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.

pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...

I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app

3 words: Dropbox Camera Upload.

exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app

iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.

I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app

phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off

anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app

31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question