Related
hey guys,
i doubt anyone can be of any help. I have bricked my captivate in trying to odin flash the rom back to the stock js6, or whatever. Any help.. wont go into download or recovery mode.
http://forum.xda-developers.com/showthread.php?t=775911
If you don't even know what ROM you're trying to flash to, perhaps you should stick to stock.
rww265 said:
hey guys,
i doubt anyone can be of any help. I have bricked my captivate in trying to odin flash the rom back to the stock js6, or whatever. Any help.. wont go into download or recovery mode.
Click to expand...
Click to collapse
I really like how descriptive you are in telling us what exactly your problem is
Here's a simplified guide to fixing your phone:
1. Press the power button. Does something happen (anything?) If yes, go to step 2, otherwise jump to step 3.
2. Read what Miami_Son posted.
3. Your phone is dead. Mail it back to Samsung. Pray that they don't charge you an arm and a leg to restore the firmware.
Uh-oh
3. Your phone is dead. Mail it back to Samsung. Pray that they don't charge you an arm and a leg to restore the firmware.
Click to expand...
Click to collapse
Do you happen to know how much they may charge for this? I tried to flash back to stock last night and now have no reaction when I press the power button. I talked to Samsung, but couldn't get any good information from them about potential cost without telling them exactly what happened.
Does anyone know what the process involves? Can the tell from a phone that won't power what was done?
Sorry for the n00bish questions.
bmwenger said:
Do you happen to know how much they may charge for this? I tried to flash back to stock last night and now have no reaction when I press the power button. I talked to Samsung, but couldn't get any good information from them about potential cost without telling them exactly what happened.
Does anyone know what the process involves? Can the tell from a phone that won't power what was done?
Sorry for the n00bish questions.
Click to expand...
Click to collapse
Hard bricking with Odin takes some effort. Did you try everything in the thread I posted? If it didn't complete an Odin flash then they probably can't tell what happened or if it has a custom ROM on it. More likely they'll just strip it for repair parts or just reflash it without diagnosing it. Just say that it was suffering from random shutdowns and now it won't turn on.
Miami_Son said:
Hard bricking with Odin takes some effort. Did you try everything in the thread I posted? If it didn't complete an Odin flash then they probably can't tell what happened or if it has a custom ROM on it. More likely they'll just strip it for repair parts or just reflash it without diagnosing it. Just say that it was suffering from random shutdowns and now it won't turn on.
Click to expand...
Click to collapse
About the only thing I haven't tried is a jig, but from what I have read unless you have something happen when you push the power button that won't work. I didn't far enough to really tell where it is in the process. I had a recovery screen (2e I think) show up and then nothing responded to a button press. Next thing I know, it won't let me boot up.
Oh well, we'll see what happens with the phone and Samsung.
Thank you so much for all the help I have gotten over the past few weeks from this site.
Tried this but I have this error after Fastboot :
HBOOT > FASTBOOT > no image or wrong image
also, tried factory reset but it just freeze or nothing happens after I chose FACTORY RESET.
Please help.
MarlX said:
Tried this but I have this error after Fastboot :
HBOOT > FASTBOOT > no image or wrong image
also, tried factory reset but it just freeze or nothing happens after I chose FACTORY RESET.
Please help.
Click to expand...
Click to collapse
Some questions, is your phone a standard DESIRE S, S-ON, with standard HBOOT etc?
I'd wait for someone with more Android experience than myself to confirm this, but, I believe that you should attempt to re-flash your original ROM (RUU). Which you should hopefully find somewhere in this post http://forum.xda-developers.com/showthread.php?t=1002506
ben_pyett said:
Some questions, is your phone a standard DESIRE S, S-ON, with standard HBOOT etc?
I'd wait for someone with more Android experience than myself to confirm this, but, I believe that you should attempt to re-flash your original ROM (RUU). Which you should hopefully find somewhere in this post http://forum.xda-developers.com/showthread.php?t=1002506
Click to expand...
Click to collapse
Thanks for the reply.
It's S-ON, this is untouched so I guess standard HBOOT?
Is flash(ing) ROM can be done even phone is not rooted?
Also, been searching around and found this (almost) same problem encountered, regarding "No image...", but I'm hesitant coz now I have to start from scratch again after that(?). :/
http://forum.xda-developers.com/showthread.php?t=648864
MarlX said:
Thanks for the reply.
It's S-ON, this is untouched so I guess standard HBOOT?
Is flash(ing) ROM can be done even phone is not rooted?
Also, been searching around and found this (almost) same problem encountered, regarding "No image...", but I'm hesitant coz now I have to start from scratch again after that(?). :/
http://forum.xda-developers.com/showthread.php?t=648864
Click to expand...
Click to collapse
You should be able to flash an official HTC ROM, without ROOT. Although if you are operator locked ie T-Mobile/Vodafone etc you may have to install one of their ROMS. Although I'm a little out of my depth/comfort zone with all this...
I may be well off the mark here, but, have you tried it, without your SD card inserted? give it a go?
What you found is related to something different. and related to image files stored on your SD card used for updating....which is what made me make the above suggestion.
After a factory reset you will have to start a fresh anyway.
Ohh. So it's not related.
My phone looks like this :
SAGA PVT SHIP S-ON RL
HBOOT-0. 98. 0000
RADIO-38. 03. 02. 15_M
e-MMC-boot
Mar 10 2011, 14:58: 38
HBOOT
vol <up>......
vol <down>......
POWER
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
FASTBOOT goes to BOOTLOADER menu which shows me the "No image..."
RECOVERY works but then after the process it turns off, and vibrate several times.
FACTORY RESET if selected, nothing happens, like it froze or something.
Did you try it without an SD as suggested?
The IMAGE errors I think (but could be wrong) are as a result of FASTBOOT auto checking for the existence of update files on your SD and simply not finding any!
Does it say Checking.....
If you select FASTBOOT then REBOOT what happens? Phone hangs? with what screen?
Hopefully someone else will add some advice soon?
ben_pyett said:
Did you try it without an SD as suggested?
The IMAGE errors I think (but could be wrong) are as a result of FASTBOOT auto checking for the existence of update files on your SD and simply not finding any!
Does it say Checking.....
If you select FASTBOOT then REBOOT what happens? Phone hangs? with what screen?
Hopefully someone else will add some advice soon?
Click to expand...
Click to collapse
Yes, I did. It's same.
If I put the SD in it, when chosing FASTBOOT the errors looks like the attachment in this topic : http://forum.xda-developers.com/showthread.php?t=703761
Yes it say Checking...
Doing FASTBOOT then REBOOT shuts down the phone then restarts it and hangs at the green HTC logo.
I really wish someone can help me.
BTW, regarding the ROM's you provided above, what do you suggest is the one for me? I really don;t have any idea. I'm from Asia (Philippines) and phone is not locked by a mobile carrier.
MarlX said:
Regarding the ROM's you provided above, what do you suggest is the one for me? I really don;t have any idea. I'm from Asia (Philippines) and phone is not locked by a mobile carrier.
Click to expand...
Click to collapse
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Same problem
I had the same problem much times!
I had to Factory Reset my phone every time it freezes!
When i did a factory reset, it was all ok until it appeared again
The only solution i found was to factory reset the phone..
ben_pyett said:
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Click to expand...
Click to collapse
Yes, I also did that. Unfortunate, nothing happens, if it does not froze it boots to that green HTC logo and stops there.
I guess the only solution is to bring this to the store where I purchased it.
ben_pyett said:
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Click to expand...
Click to collapse
Yes, I also did that. Unfortunate, nothing happens, if it does not froze it boots to that green HTC logo and stops there.
I guess the only solution is to bring this to the store where I purchased it.
MarlX said:
I guess the only solution is to bring this to the store where I purchased it.
Click to expand...
Click to collapse
Did you read the very similar sounding thread that I found http://forum.xda-developers.com/showthread.php?t=1107016&highlight=boot? unfortunately this is what that person ended up doing
If someone can advise which ROM would be the best for you to select then I'd possibly try that before returning it?
Good luck...
I've seen another user @Skanob also from the Phillipines, if you look at the details within his signature in the following post http://forum.xda-developers.com/showpost.php?p=14748687&postcount=4 you should see details of the RUU ROM that you can/should try to flash.
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
MarlX said:
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
Click to expand...
Click to collapse
I'll be perfectly honest, I don't know if this voids warranty....sorry..
Ultimately, you're only putting back the same ROM as the phone has on it originally, but, bear in mind that in the other thread I posted above, re-flashing the original ROM didn't resolve the issue, so if there's any doubt that this might void the warranty - don't do it!
MarlX said:
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
Click to expand...
Click to collapse
Flashing RUU won't void the warranty. How long are you waiting on the htc logo screen? It can take a while after factory reset...
It might be that some files were corrupted so flashing RUU should help. If not, connect your device to computer and see what logcat is showing
Sent from my HTC Desire S using XDA App
The longest was 25 minutes, then had it reboot again coz nothing happened. Also, when doing the Factory Reset it just hangs/do nothing, can't choose any option from the menu, have to remove the battery to turn the device off.
I'm gonna bring the phone to the service center in a while.
Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
XHaGGeNx said:
Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
Click to expand...
Click to collapse
So you've relocked the bootloader, and then nothing else?
Run the RUU from the bootloader screen. Make sure the RUU is for YOUR phone
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
XHaGGeNx said:
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
Click to expand...
Click to collapse
Seeing as though you have relocked the bootloader you can either a. unlock the phone again so you can install a custom rom or b. run a ruu to get it back to stock.
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
XHaGGeNx said:
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
Click to expand...
Click to collapse
No no no. You said you wanted to go back to stock correct?
Download your stock RUU, and run from that white menu that says RE-LOCKED at the top. That's your bootloader
Ok, when you mean run from that white menu that says RELOCKED, how can I run it from that menu if I cant get into anything from this menu? Do you mean just run the RUU program from my computer and have my phone connected to the PC? I used to be able to go into that TWRP screen when i was in bootloader but now I can't.
XHaGGeNx said:
Ok, that's what I am doing already. I am downloading the RUU for my phone. Hope to gawd this will save my phone. I am just worried because it's literally stuck at this bootloader menu screen. I can't do anything else.
Click to expand...
Click to collapse
Believe me, the fact your screen is on is a sign you are not bricked. Run the RUU (Make sure it's one that is easily rootable, like the 1.85 for ATT), and go through the process of bootloader and unlock and rooting. Hope this helped
I am glad to hear that. It's almost done downloading, about 4 minutes left. I really want to thank you for helping me out here. I am such a screw up with this stuff. Sigh. anyways, I'll let you know what happens here shortly. Thank you so much once again. Really..
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
It's working! It's updating and everything. Phew! No offense taken, I hear ya and agree. Just being a noob at all this can put me into a lot of trouble. I have learned a lot of stuff though lol. Anyways, thank you everyone for helping me! I should be good from here
Glad to hear its working
Cheers man, good to hear everything is fixed.
If you need anything else, contact me. There are a bunch of ways to.
As for rooting again? Just read up and you'll be set.
mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
A simple "Be more careful next time because of ..." would have been just fine.
superchilpil said:
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
My apologies. We had been PMing for over an hour before this thread trying to get his phone back. I came off a little rude on that last post but he knows how hard I was trying to help him and that he can always come here for answers. Most forum guys would tell him to "search it"
please
how did you fix your phone i almost have same problem
He didn't delete ROM, recovery or anything. He relocked his bootloader. It just won't let you reboot unless you relock with a stock recovery flashed.
Sent from my One X using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1982968
Could u guys stop by my thread and help me out?
I kinda have the same problem, and RUU tells me phone is off, error 170.
Thanks
Starting with where I am now: my ATT One X is totally unresponsive. Power button held, Power plus either of the volume buttons held, nothing produces any response. When I plug it into a wall adapter, the charging LED doesn't light up. It is both looking and talking like a brick.
Here's how I got here, and I'm hoping someone may have some kind of suggestion .
I had been running Tachi91's original Sense JB ROM. TWRP recovery. I used the AT&T JB update RUU from HTC's site.
Before doing this, I rebooted to bootloader and re-locked the bootloader. After this, I seemed to be unable to reboot back into system, so I just ran the RUU while the phone was sitting in the bootloader (figuring that the first thing the RUU seems to have done in the past is reboot to the bootloader).
The RUU went through its usual lengthy, multi-reboot thing. No errors whatsoever, everything seemed totally fine. Clicked "Finish" at the end...and my phone's screen went black. I figured it was rebooting, but unless it's taken the past 40 minutes to reboot (which seems unlikely! ), something is obviously amiss. See beginning of post for what I've tried since and results.
Any suggestions?
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
I fear the worst.
Sent from my HOX w/CM10.1 4.2.2 s-off
subarudroid said:
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
I fear the worst.
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
...yeeeeah, total violation of item #1 on that list. And here I figured I was relatively safe with an RUU. Oops.
Thanks for pointing that post out to me. At least I know where I stand now! Better than sitting here making my thumbs go numb trying different power/volume combinations.
Why oh why do many people persist in thinking they don't need s-off??
Sent from my Nexus 7 using Tapatalk HD
Please help!
Hey, does any one know if there is any solution i can do myself? or do i have to send it to a jtag repair, because i just received it a month ago from a earlier brick. I just can not believe i bricked it again doing a RUU update. Thank you
buy a jtag
Nicobesso said:
Hey, does any one know if there is any solution i can do myself? or do i have to send it to a jtag repair, because i just received it a month ago from a earlier brick. I just can not believe i bricked it again doing a RUU update. Thank you
Click to expand...
Click to collapse
Could try the JET. Check the Development forum.
I'm currently on my 4th replacement from Verizon. Everytime the phone has either went into an endless bootloader loop where clicking start takes me back to the bootloader and when going to recovery it says "failed to boot to recovery" or turned off and wouldn't turn back on and essentially becomes a bricked phone. Is there anyone else with this problem?
Edit- I'm on stock Android 7.1.1 and not rooted.
Timtube said:
I'm currently on my 4th replacement from Verizon. Everytime the phone has either went into an endless bootloader loop where clicking start takes me back to the bootloader and when going to recovery it says "failed to boot to recovery" or turned off and wouldn't turn back on and essentially becomes a bricked phone. Is there anyone else with this problem?
Click to expand...
Click to collapse
Did it work in the Verizon store? I've perhaps seen this once or twice but a replacement device usually worked. But 4 devices? That just doesn't seem real. Not that you're making it up but you need to explain what you are doing before the device goes into a boot loop. Worst case scenario, go to a store and make sure the phone works before you leave.
Weird sounds like you are trying to use depixel8 on an unsupported firmware? And you are bootlooping the phone ?
happened to me on my first device, partly why i havent SU or TWRP yet....just unlocked for future fun...
Mine bricked inbetween twrp and SU....but im sure i messed up somewhere. TWRP worked but as soon as i did SU, it all went wrong for me.....Figured id wait to more stable stuff is out, before messing around again.
mine did the same thing as what your describing...
peace
byte
I did not unlock the bootloader. I am not rooted. I am using stock Verizon Pixel XL 7.1.1.
well that changes everything, sounds like just bad luck dude
bytethegroove said:
well that changes everything, sounds like just bad luck dude
Click to expand...
Click to collapse
I know it sucks. I really like the phone when it works.