Related
Ok guys, I feel this is just the end of the games... I was flashing back the Roto JME fw with the swype keyboard issue fixed that I have just made, when I accidentally unplugged the tab while starting flashing and in downloading mode.
Now all I get is a logo with a phone an alert symbol and a computer .
Windows as well as Odin see it, but I can't do anything, as Odin hangs on waiting for connection, or something like that.
Is there anything I can do?? Or do I really have to take it to the warranty? And if I will have to take it to the warranty will they see I have previously flashed a beta rooted image on it??
Here's what I am talking about
Please I need some help..
Thanks
Is there no recovery mode by buttons like the captivate? I hate seeing all the bricks
Sent from my SPH-P100 using XDA App
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Segnale007 said:
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Click to expand...
Click to collapse
Ops, it was the driver... damn windows ...
Solved btw.. I just realized I have lots of things to learn ... I have almost died of heart attack when I saw my tab stucked on that logo.. and now its back again..
Thank u falks
You need to make sure samsung kies are not running for sure unistall it and try it again
use odin. that is still download mode. might take you a couple of tries but works. i was in your shoes the other day
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Segnale007 said:
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
I've heard plenty of goofy stories about bricking devices over the years. You must conclude the following:
1.Flash your device in a locked room to avoid your wife/ child pulling cables or pressing buttons.
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
3.Read instructions carefully and write the procedure out in your own words if its your first time.
I've been flashing for years and haven't had a brick yet. Not crossing my fingers either because it has little to do with luck and much to do with care. In this way its a lot like making babies...
ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Good advice.
My only semi-bricks (that involved an hour or two of trial and error to unbrick) resulted from some manner of overzealous cable unplugging.
zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
This is what I have done
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Well, first of all thanks for ur nice words. Let me just say that I was about to disconnect another device from the hub where the GTAB was attached and flashing at that time, and yea, I accidentally unplugged the GTAB instead of the other device. I may be a moron, thanks, and thankfully not everyone believes themselves as god, which is a good reason to not help other people who are in troubles, even if for stupid things sometimes... If everyone were thinking like u we were probably still at the age of 1400 ...
Mate it wasn't a barb directed at you personally, but you weren't exactly careful were you?
I'm no god... but I've never bricked a device either, and I've been flashing for over five years now. To top it off I've almost never owned a device which could be taken back to the shop (90% of them come from other countries, not my local retailers). Perhaps this has taught me to be careful.
In any case, what I said holds true, and if you ask around I'm certain you find most will agree.
Dude, you have the best avatar! I can't keep my eyes away! Good luck, and don't worry about mistakes - that is one reason this forum exists.
Cannot start my Gtab after trying update JMC
...Hello everybody,
I am really worry about the fact my Gtab doesn't want to switch on after trying to flash it. I tried all process to put it on download mode or recovery but nothing work.
Do you have any idea about it ? Is there a specific procedure to switch on (eg : press power for 1 minutes + blablabla).
My provider doesn't want to take my Gtab in warenty before my contract is activated (the 4th of february).
Thank you for your answer
HELP, I have same problem, please explain how Hemidall can fix it?
Thanks
[email protected]
zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
I also had a semi-bricked VZW Tab, with the phone-triangle-computer warning graphic at start up. (I flashed a new boot loader, and failed to read the instructions closely enough. Either the file was incorrect for my device, or the drivers were not loaded correctly, but my tablet was borked.)
Using heimdall 1.3.2 (with the correct drivers, on a 32-bit windows system), I clicked the "close pc screen" option to clear the warning.
I then held the power button until it turned off, then held vol+ and power to re-enter download mode. Once in download mode, I used heimdall 1.1.1 to flash the zImage from SCH-I800-Stock-Rooted-2.3.5. My tablet (still unrooted, and still stock?) booted, but sat at the SAMSUNG logo for ten minutes or more. (It announced its progress, telling me periodically "five minutes remaining", etc.)
Once it finished, my tablet was revived. I will now follow the above advice and read all instructions very carefully, re-writing them in my own words to ensure I understand what I'm doing, before I try this again.
One year old thread......do you guys ever watch posting dates???
Sent from my GT-P1000 using Tapatalk 2
...like REALLY bricked
bumping this old thread in hopes that someone can point me in the right direction...
Got my p7510 (10.1" wifi retail) stuck pretty badly when trying to restore stock ROM coming from Overcome (it came rooted from ebay). From what I gather from the forums, seems like my bootloader is still locked.
whenever I attempt to flash a BOOTLOADER, PIT, or PDA using ODIN it connects, initializes, and gets stuck on "Flashing boot.img"
I think the recovery partition is damaged. When I boot using Power + Volume Down, I can get to the screen where you select recovery mode or download mode but recovery mode will not load. The screen flickers when I select recovery, but goes nowhere. Download mode works.
I tried using nvflash to force the right software onto it but I get error 0x4 (usb write failed).
There has to be a way to restore the stock bootloader and get this thing running again. Tablet will not boot android at this point. I have been searching the forums for about a week now, anyone have any ideas?
Hi All,
I just purchased my Captivate yesterday from Costco (Expecting to still get the 2.4 Eclair) but unfortunately I got the Froyo 2.2 on my new captivate.
I tried rooting it using superoneClick and it just gets stuck on "Waiting for Device". I have drivers properly installed on my windows 7 64 bit machine (because I can use the phone and access its internal SD card).
Can anyone have suggestion or faced similar problems?
I have tried disabling/re-enabling usb debgging while it says "Waiting for the device"
Search the forum. There are a few threads floating around on different ways to root the stock froyo build. I don't know why the superoneclick wont work in your case but a search will turn up some info for you.
thanks. I will search the the threads and will post my results here in this thread for someone like me struggling with the same problem.
If you were planning on flashing a custom ROM after rooting anyway, you could use Odin one-click from download mode to flash 2.1 eclair, and then go from there.
Are you sure you are enabling debugging? I just used superoneclick on my phone last night after I flashe dback to stock.
First thing I do is change the phone in settings to - Ask on Connection, then I enable debugging.
Also you could try a different USB port on your computer and also make sure you have all of your necessary drivers installed.
I hope you get it figured out!
PeteSeiler2010: I haven't tried different USB port yet. I will try tonight and see if it goes through.
For usb debugging, I tried that as I mentioned. Let me just conform what I did. When it says "Waiting for device" for several seconds, I disconnected USB cable from either phone or computer (because it says that if you are stuck on "waiting for device", disable and re-enable usb debugging) because without disconnecting the cable, phone didn't let me disable the USB debugging..
So looks like I am missing something here??
22andy2 said:
PeteSeiler2010: I haven't tried different USB port yet. I will try tonight and see if it goes through.
For usb debugging, I tried that as I mentioned. Let me just conform what I did. When it says "Waiting for device" for several seconds, I disconnected USB cable from either phone or computer (because it says that if you are stuck on "waiting for device", disable and re-enable usb debugging) because without disconnecting the cable, phone didn't let me disable the USB debugging..
So looks like I am missing something here??
Click to expand...
Click to collapse
want a much easier method? install speedmod kernel using odin, reboot into recovery, advanced features (not the CWM version), and choose the option that says something like "root phone" and choose the "simple" option. congratulations, you are now rooted and running a custom kernel with CWM that can install a custom ROM.
next time, please do not post this in development as this has NOTHING to do with development. Q&A or general next time, please.
How did someone with no posts, post a question in this section? I thought you had to have a minimum of 10 posts to post in here.
I am sorry if I have missed that rule for the new posting but I am new (just two days old) into the android world and for the xda forums as well..
22andy2 said:
I am sorry if I have missed that rule for the new posting but I am new (just two days old) into the android world and for the xda forums as well..
Click to expand...
Click to collapse
So why is your join date Dec 2007?
CB650 Wolf said:
So why is your join date Dec 2007?
Click to expand...
Click to collapse
thats when I just registered.. I will be the active member now as I officially own the android phone.
I really appreciate all of you guys work and I didn't mean to offend any one by posting the thread here.
I already apologize for missing the rule for the 10 minimum posts on forum before posting.
I rooted my device successfully by using odin. Thanks all of you for the suggestions.
I own a Galaxy S GT-i9000( bought at SFR)
When I connect it to computer I get the prompt that tells to choose between Storage, Kies...
But whatever I choose the computer tells me USB Device not recognised.
Now I was stupid enough to do the following:
I managed to root using Z4root by copying the APK file on external sd .
I got rom manager and updated my recovery.
I updated using the CM10-unofficial rom that is in the development forum: http://forum.xda-developers.com/showthread.php?t=1775169
The Mobile Network was not working so I did the following
I restored the nand that i did in recovery and now the phone is frozen on the first boot screen (Galaxy S GT-i9000 SCREEN)
Now I can go to Download mode but I can't go to recovery mode.
Let me remind you that my USB data connection is not working. So even though I enter into the Download mode I am not able to use Odin. If you know somthing that I am not doing, let me know.
So now I am looking for a solution that would permit me to flash without USB or allow me to go to recovery mode. Or a tutorial on how to change the usb port myself.
Thanks in advance.
kigordid said:
So now I am looking for a solution that would permit me to flash without USB or allow me to go to recovery mode. Or a tutorial on how to change the usb port myself. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=29464733&postcount=10
You can try using Mobile Odin.
Also, you can try Heimdall method: https://www.fixmystuff.in/FMS_Forum...-flashing-to-original-rom-using-heimdall.126/
Hey
have you tried to connect it in Download mode??
Need more solutions
Thanks again to all of you that have answered me so fast.
Well I just finished trying all that you suggested.
unfortunately am still at the same point. Whatever I do, whatever drivers am putting in, cleaning inside the USB port with methylated spirit... Not getting Odin or Kies to detect it.
I read somewhere that when the data connection works, I should see the device named Samsung Device even before installing the drivers, but all I am getting is Unknown device. I still went ahead uninstalling and installing the drivers you provided and there is no successful outcome so far.
I still have faith. I have a little knowledge in electronics. I can open my phone and get to the usb port. My problem is I don't get any tutorial on how to replace the usb port. The thing is the connections are very tiny. I can also do with a bypass way that could make me install a 2nd usb port temporarily just long enough to flash the phone.
Or a hardware solution if I have to remove and flash a specific IC in a certain manner.
Thank you in advance.
help
hi there,
after doing alot of stuff to your phone that wasnt nessacary i'm not surprised it doesnt work er sorry . the only thing i can think of is the following whenever i have a problem with windows i go to linux, which is faster , much more efficient . so i suggest that you install linux ( ubuntu the best ) and try using odin with the linux version, it often detects things that windows doesnt see. other than that sorry cant think of anything else .
see ya
Trying it
thesmegger said:
hi there,
so i suggest that you install linux ( ubuntu the best ) and try using odin with the linux version, it often detects things that windows doesnt see.
see ya
Click to expand...
Click to collapse
Thank you.
Am going to boot on linux right away. I will let you know.
Back to zero
kigordid said:
Thank you.
Am going to boot on linux right away. I will let you know.
Click to expand...
Click to collapse
It doesn't change anything.
Am back to my start point.
Thank you though.
Anything Else?
Does anyone have something else to suggest or I should consider my phone dead?
Look like a quite number of people are having this same issue and haven't got over it.
I just hang on and appeal to all of you cos I know XDA is the best place where I can get a solution.
Lemme know any suggestion... even the ones you are not sure can help. Am willing to do anything.
Thanks again all of you.
hi
hi there
if all else fails there is a jig
http://forum.xda-developers.com/showthread.php?t=1402286
this forces your phone into download mode and will help for sofy bricks so look it up on the link and try that , sometimes on local forums like we have in france members will comme over and lend you one , or just buy one eyc .
hope that helped
see ya :good:
Uninstall from PC Kies, instal samsung drivers, then download and flash mod 2.3.4 xxjvp stock? / Or other, 3.PDA, PHONE, CSC / pit is 512 and re-partition and start to turn in Odin.
my htc one (M7) (GSM) got hard bricked on its own (i never rooted it or anything), it shows up as QHSUSBDLOAD or something in the device manager in windows 8.1
i found this link to revive my phone: http://forum.xda-developers.com/showthread.php?t=2770684
I am a total noob and i know nothing about rooting or flashing roms or anything for that matter (i just think my phone is hard bricked because someone told me if it comes up as QHSUSBDLOAD in the dev manager, it means it is hard bricked). There is no response if i hold the power button, or the power and volume buttons under a bright light or not under a bright light, i tried charging it continuously for 5 days, nothing happened, LED is not flashing. Only when i connect it to windows via a usb cable, it recognised it as an unknown device, when i updated the driver, it showed QHSUSBDLOAD.
This link (same as above): http://forum.xda-developers.com/showthread.php?t=2770684
worked for many people. i'm a noob so can anyone please elaborate and give me a full detailed process on how to go about it. Again, i never ever rooted my phone.
And its out of the warranty period, and i dont really know what a jtag box is, but i heard it involves opening up your phone, and i really dont wanna do that. But, if theres a method of using jtag via a usb cable and reviving my phone without opening it up, then plz tell me that too.
otherwise, just elaborate on the same link ( http://forum.xda-developers.com/showthread.php?t=2770684)
and explain it to me like u would to a noob.
THANK YOU!!!!
Any help is appreciated.
Hi,
Thanks for using XDA Assist Please Standby When we move your post here HTC One Help and Troubleshooting
Good Luck !
ari4788 said:
my htc one (M7) (GSM) got hard bricked on its own (i never rooted it or anything), it shows up as QHSUSBDLOAD or something in the device manager in windows 8.1
i found this link to revive my phone: http://forum.xda-developers.com/showthread.php?t=2770684
I am a total noob and i know nothing about rooting or flashing roms or anything for that matter (i just think my phone is hard bricked because someone told me if it comes up as QHSUSBDLOAD in the dev manager, it means it is hard bricked). There is no response if i hold the power button, or the power and volume buttons under a bright light or not under a bright light, i tried charging it continuously for 5 days, nothing happened, LED is not flashing. Only when i connect it to windows via a usb cable, it recognised it as an unknown device, when i updated the driver, it showed QHSUSBDLOAD.
This link (same as above): http://forum.xda-developers.com/showthread.php?t=2770684
worked for many people. i'm a noob so can anyone please elaborate and give me a full detailed process on how to go about it. Again, i never ever rooted my phone.
And its out of the warranty period, and i dont really know what a jtag box is, but i heard it involves opening up your phone, and i really dont wanna do that. But, if theres a method of using jtag via a usb cable and reviving my phone without opening it up, then plz tell me that too.
otherwise, just elaborate on the same link ( http://forum.xda-developers.com/showthread.php?t=2770684)
and explain it to me like u would to a noob.
THANK YOU!!!!
Any help is appreciated.
Click to expand...
Click to collapse
First line of the guide:
This will fix devices which were bricked due to firmware incompatibility. This can be caused with the way HTC handles the firmware updates in it's m7's OTAs. If you've been flashing from a 3.x firmware to a 5.x firmware via OTA, or manually, you most likely have a device stuck in QHSUSB_DLOAD. This tool is for you
Click to expand...
Click to collapse
Doesnt apply to your situation:
my htc one (M7) (GSM) got hard bricked on its own(i never rooted it or anything),
Click to expand...
Click to collapse
Device entering QHSUSB DLOAD mode by themselves are usually devices with hardware problem and this guide won't fix anything. You'll probably have to replace the motherboard of your phone. You should however give this guide a try just to confirm its indeed an hardware problem. Just follow steps by steps and ask questions when you are stuck.
alray said:
First line of the guide:
Doesnt apply to your situation:
Device entering QHSUSB DLOAD mode by themselves are usually devices with hardware problem and this guide won't fix anything. You'll probably have to replace the motherboard of your phone. You should however give this guide a try just to confirm its indeed an hardware problem. Just follow steps by steps and ask questions when you are stuck.
Click to expand...
Click to collapse
thanks for the reply.
First of all, i don't know what all this is:
the appropriate package for the device
fastboot
distro utils: md5sum, strings, tail, grep, unzip ( all included in most linux distros)
some basic linux experience
root access on a linux machine
I've never touched Linux EVER. Only thing i know is that it's an operating system.
IF you have the time, can u please tell me:
1) ''which version'' of Linux i should install (is it 64 bit and 32 bit too?)
2) from where should i install it
3) how should i install it
4) what Ubuntu is. is it some form of linux. Can it be used in this case? If yes, then how?
5) what fastboot, distro utils, root access on linux means.
6) can linux be installed side by side on my windows pc along with the windows i already have? then how?
7) what all this means-
Boot the linux box and download the appropriate package for the device.
Remove the sim card from the phone. Do not connect yet
Extract the package in your working directory
Open up a terminal and cd to that directory
Run revive.sh as root and connect the device
Code:
sudo ./revive.sh
( i mean, i know how to remove the sim card, but whats a linux box?, how do you extract the package?, how to open u a terminal, what is a terminal?, how to open up a cd to that directory, which cd? how to "run revive .sh as root", what the code sudo ./revive.sh means and how and where do i use it?)
Thank You.
BTW, is there any way to tell for sure whether my problem is in the hardware or in the software?
Q&A for [GUIDE]How To Unbrick Your Galaxy Tab!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE]How To Unbrick Your Galaxy Tab!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Galaxy Tab 3 T210R / Bricked?
OK, I know I screwed this up b/c I was tired when I was working on the tablet. It's a Galaxy Tab 3 7.0 T210R (one of several I'm working on). Feel free to say I"m an idiot, I already know it was a stupid mistake.
I reset to factory specs using the operating system after installing the KitKat 4.4.2 firmware update and TWRP. This was that last thing I did before the current status.
Current status is that it won't start, yet Odin registers the tablet as connected, and seemed to be able to reinstall the firmware & TWRP with a positive result.
UPDATE: I was able to connect kies which also seemed to complete a system update, except that the tablet still has a black screen and seemingly unresponsive buttons. This is so weird.
Sooooo, not sure if it's bricked or not, since Odin registers it being connected. However, Kies can't find it. And none of the buttons appear to work.
I have it plugged into the outlet charging at the moment (not the laptop). It was nearly fully charged when I screwed it up.
I have SD cards, and an a couple exact model tablets that work just fine with the new Firmware (4.4.2) and TWRP (2.8.20). Is it possible to clone one of the working ones onto this one?
The one thing I haven't done is try to install a new ROM.
Help? Bricked? Or... ?
Much appreciate any expertise or suggestions. Thanks.
Bricked, or not bricked? Samsung Galaxy T210R
gtcreative said:
OK, I know I screwed this up b/c I was tired when I was working on the tablet. It's a Galaxy Tab 3 7.0 T210R (one of several I'm working on). Feel free to say I"m an idiot, I already know it was a stupid mistake.
I reset to factory specs using the operating system after installing the KitKat 4.4.2 firmware update and TWRP. This was that last thing I did before the current status.
Current status is that it won't start, yet Odin registers the tablet as connected, and seemed to be able to reinstall the firmware & TWRP with a positive result.
___________________________________________
UPDATE: I was able to connect kies which also seemed to complete a system update, except that the tablet still has a black screen and seemingly unresponsive buttons. This is so weird.
Sooooo, not sure if it's bricked or not, since Odin registers it being connected. However, Kies can't find it. And none of the buttons appear to work.
I have it plugged into the outlet charging at the moment (not the laptop). It was nearly fully charged when I screwed it up.
I have SD cards, and an a couple exact model tablets that work just fine with the new Firmware (4.4.2) and TWRP (2.8.20). Is it possible to clone one of the working ones onto this one?
The one thing I haven't done is try to install a new ROM.
Help? Bricked? Or... ?
Much appreciate any expertise or suggestions. Thanks.
Click to expand...
Click to collapse
____________________________________________
Update 07/07/2015
I let the tablet's battery run down (as was suggested in one of the threads), and when I plugged it in to the AC power, I got the Samsung Galaxy logo!
I was then able to restart in download mode, and reinstall the md5 file via Odin. Not sure why letting the battery run down works, but at this point, I don't really care. I'm glad that the tablet could be resurrected from the dead, in spite of my mistake.
I hope this is helpful! :victory:
tab not showing up in ODIN
I have my galaxy tab soft bricked, but when I plug it in to ODIN, the pc does not recognise the tablet and therefore I can't reinstall the firmware, although the tablet is connected to the pc, as it gets charging when plugged in.
I've tried reinstalling samsung drivers, killing every samsung keys program running in background, another cable and even three different ODIN versions (v.1.7 // v3.07 // v.3.09), but it is not showing up in any version.
I have been looking for a solution since last year. last year I had windows 8 and it didn't work; then I upgraded to win 8.1. again nothing, and with windows 10 the same story. can anyone help me please?
thank you very much.
internal memory read only my p3100
hi ..
thanks in advance
i dont know what happened to my tab p3100, i am not able place any files in internal memory.
it will get into the main screen and gives bunch of errors like process google play is not working... bla bla bla...
i can uninstal the function but after reboot it will be there in the phone. i am bit tensed what is this is this a bricked one or?
please help me out i tried odin, through odin i installed omia rom 5.1 after that this error i am getting please help me out to solve this.
my phone already rooted..
Once again thanks hooping for the fix.
please mail the fix to [email protected]