Database Users

[GUIDE] Recover your bricked Bell (or other download mode disabled SGS)

I went and bricked my SGS again and thought great.. time to exchange again right? Wrong.
My Bell SGS is one of those cute ones that has no download mode. I thought all hope was lost. It wasn't.
It's simple, adb reboot recovery works fine. But trying to adb is a pain in the ass. Easy solution.
1) Get the one click root/unroot tool: http://forum.xda-developers.com/showthread.php?t=742403
2) Use the tool--any setting is fine, all we're using this for is getting into recovery mode. I clicked unroot 2.1.
3) Surprise! The tool can communicate with the phone just fine even though the phone is failing to boot. You're now in recovery mode.
4) Wipe the data and the cache on the device, and you're good as new. No flashing of update.zip required.

I guess that:
adb reboot recovery
would also work then?

Mithent said:
I guess that:
adb reboot recovery
would also work then?
Click to expand...
Click to collapse
You know, I have no idea. I'm assuming so since that's what I believe his software calls upon, but I've never actually tried it.

define your "bricked"
did you get this screen of
pc-!-phone ?
because in that screen, the phone is not recognized by windows when you plug in the USB cable
so ADB doesn't work when it's the phone is not listening to the PC

Mithent said:
I guess that:
adb reboot recovery
would also work then?
Click to expand...
Click to collapse
AllGamer said:
define your "bricked"
did you get this screen of
pc-!-phone ?
because in that screen, the phone is not recognized by windows when you plug in the USB cable
so ADB doesn't work when it's the phone is not listening to the PC
Click to expand...
Click to collapse
No, I did not get that screen. For me, it just blacked out and locked on bootup.

scouzer said:
No, I did not get that screen. For me, it just blacked out and locked on bootup.
Click to expand...
Click to collapse
then that is not bricked
that is just a software error
when you are truly bricked the phone will not do anything but show you only that screen

AllGamer said:
then that is not bricked
that is just a software error
when you are truly bricked the phone will not do anything but show you only that screen
Click to expand...
Click to collapse
Well I did not know this, and I doubt many people here do either. So I think it's helpful.

picture here
{
"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"
}
* adding it to wiki

Hope I never see that screen then, so if you see that is it game over....no chance of recovery?

galaxysman said:
Hope I never see that screen then, so if you see that is it game over....no chance of recovery?
Click to expand...
Click to collapse
If your phone is 3 button disabled, no chance of recovery. If you have 3 button recovery enabled, it's no big deal.

Cant you just send it into Samsung to recover it if its under warentee??

Cant you just send it into Samsung to recover it if its under warranty??

d3a said:
Cant you just send it into Samsung to recover it if its under warentee??
Click to expand...
Click to collapse
yes you can
actually i did that to mine the one that had the 3 buttons disabled
the new one i picked up have the 3 buttons working properly

Can the 3 button be enabled through a potential future software update?
Or is it something thats so hard-coded in, that it cannot he ever fixed

Ziostilon said:
Can the 3 button be enabled through a potential future software update?
Or is it something thats so hard-coded in, that it cannot he ever fixed
Click to expand...
Click to collapse
it's called a SPL, it might be possible to be fixed if some developers figures out how to copy a good SPL over the defective SPL, but at the moment there is no fix

When i press "3 button" i go to downloading mod, how to get in recovery ? Except from rom manager...

micri said:
When i press "3 button" i go to downloading mod, how to get in recovery ? Except from rom manager...
Click to expand...
Click to collapse
same 3 button, but use volume up instead of down
see the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/Vibrant_GT-I9000M

Someone please help
I was trying to run the DTJG4 with the 512 PITT through ODIN when it failed.
I tried again and it didnt flash, so I tried rebooting the phone.
Now I get nothing... just a black screen.
Plug in the power, nothing, plug in the USB, nothing.
Battery removed several times and tried powering up just with power and battery, and trying 3 button combo that didnt work before, but still nothing.
Any ideas?
Thanks

AllGamer said:
picture here
* adding it to wiki
Click to expand...
Click to collapse
I had I9000M do this, 3 button mode was not working and had to return it. It happened during a kies update, luckly, 20 minutes after I had bought it. So I went to a different store and got my current phone. This phone is the best one of the three I've owned. Either 3 button mode just works, and the g-sensor calibration is much closer to being dead on. So there are good ones out there.
I've had 3 total. Here's a breakdown.
1. Purchased august 6th. First phone sold in the store. Download and Recovery modes worked 25% of the time. G-sensor calibration was horrible. Also could not be unlocked.
2. August 21st. Could not get the phone into either mode with button presses. Phone unlocked, but bricked via kies update. Never got to test the g-sensor. Last phone in same store as first purchase.
3. August 21st. Near perfect phone. 100% sucess gettung into download or recovery modes. Unlocked easily, and G-sensor is just slightly off. No need for calibration, unless using as leveling device. Purchased at a store that got initial stock on august 8th.
So, there ARE good phones out there. But the majority by the sounds of it are less than good. Which is unforunate.
As a former samsung owner as well, this is dissapointing. The original galaxy i7500L is still officially running android 1.5 in canada. I just hope and pray samsung doesn't drop this device from their dev cycles. And better yet.. Can fix all these problems with an update somehow...
Sent from my GT-I9000M using XDA App

So, only that specific screen counts as a brick?
On mine the 3 button combo doesn't work (I can only get to some weird "upload mode"), and the phone is stuck on the "Samsung Galaxy S GT-I9000" screen when I boot it up.
Does that mean I should still be able to use ADB with it? The PC seems to recognize the phone (as "SAMSUNG USB Composite Device"), as well as Odin, but ADB doesn't.

[Q] Brick phone maybe? help me out

So I got a htc mytouch 4g And it has that phone icon with a triangle and exclamtion mark. I dont know anything about this phone since I have a att captivate From what I read is that if you have recovery you might be able to do it.
Also when I plug in the usb I go into recover and I Get a fasboot screen and other sorts of menus i have put a pd15img.zip in my external sd card and it loads installs It I guess but still boots into the same Icon.
from what I also read is that you can fix this by loading a stock rom pushing into your sdcard via adb but make sure is name update.zip but when I do that I get Invalid Operation.
when in recovery I have this message E:cant't open /cache/recovery/command also phone boots right into that icon.
{
"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"
}
I assume this is a soft brick since I get into recover and the other fasboot menu when I plug in USB any help is appreciated
This is my first time with a phone like this so I'm doing what I would normaly do with a captivate ish

I answered in your other thread here. However, now that you've posted a screenshot, I see that the phone isn't even rooted. I have no idea how you get into a custom recovery without root.

I connect usb while the phoneis off and then press volume up + power and that appears.

chibixzero said:
I connect usb while the phoneis off and then press volume up + power and that appears.
Click to expand...
Click to collapse
Yeah, see where it says "S-ON"? That means the phone isn't rooted. You need to perm root and it install CWM recovery, but with those cache errors you're getting, I'm not sure there's any point since those usually indicate a failed eMMC.

Guess my options are
1. call t-mobile and tell them what happen maybe they will replace it but I didnt buy it with contract I'm att and was going to ask my friend to get me unlock code, But idk if its possible I drop it and theres a crack on the phone
2. sell it for parts...
>.< money down the drain I guess fuggin phone

You're booting into stock recovery by default, that's the "triange". That might happen if you have a VolumeDown key/trackpad stuck.
The error in the recovery is natural - stock recovery expects a command when booted into, but finds nothing.
Check that you're indeed installing a correct PD15IMG that contains a complete system image, and if you are and it still doesn't help - try to shake the phone on the side / upside down, to try and release the possibly stuck buttons. If it doesn't help - the phone needs warranty repair. T-Mobile or HTC directly, your choice. To send it to HTC, you pay the shipping. But in any case it's under warranty, unless it has water damage or something.

download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe

atifsh said:
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
Click to expand...
Click to collapse
That appears to be the Gingerbread leak from the Canadian HTC Panache, but you might want to describe to the OP what exactly it is. Most people won't blindly flash something to their phone without a little info first. Also, could that be flashed to a non-rooted device?

yes thats the official RUU of panache which is glacier inside.
yes u can flash as its RUU.exe u dont need root.
u can even comeback to official mytouch RUU.zip using this exe later if wanted.
because its exe it will reflash everything boot, recovery, splash, radio every thing, thus fixing any problem thats not hardware.

atifsh said:
download this go into fastboot/bootloader then run the ruu and flash, if after this u still get to recovery than its something else.
http://dl.dropbox.com/u/25823285/RUU_Glacier_Gingerbread_S_Videotron_CA_2.10.1530.1_Radio_12.55.60.25_26.09.04.26_M_release_188466_signed.exe
Click to expand...
Click to collapse
i used this as noted but I get this error
Customer ID error (131) I read on these forums is has something todo with a goldcard?
Edit-
I manage to load a stock rom into a External sd card. it updated it everything pass exept step 8 it skip it and the said finish updateing press power to reboot. Rebooted but the whole (second) mytouch splash was going for a long time. I try to use the RUU.exe and it wont boot into bootloatder just boots and stays on the splash screen.
this is what I get now and is stuck on That screen updating radio

Damn.
That would be the first completely stock Mytouch4G in the forum that has a failed eMMC chip.
Yes, it's bricked, you need to exchange it.
But it's also a good proof that gfree has nothing to do with failed eMMC, extra write cycles of flashing ROMs most probably just speed up the destruction process.

you got one large scratch on screen, how good have you kept your phone? have you droped it badly once or twice?
when you used the RUU.exe when did u get that error, does it go upto where it showed you the rom version?
if u got there than you can try one more time but this time with official mytouch RUU.zip. i'll tell you how to do that, later if u got upto that part.

edit nevermind my post cameback above this

If it shows "Fail-PU" in bootloader - then the eMMC isn't functional anymore. No flashing will help him in this case, only warranty repair.

hmm too bad, feel sorry for him

[Q] Need Help restoring Nexus 10!!

Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
{
"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 finally figured out the problem... I had to completely flah the stock image from fastboot, but my drivers were not up-to-date... so I guess it was kinda my own fault... sorry.... but let it be a cautionary tale for everyone, DRIVERS DO MATTER!!

Mancini_Rafael said:
Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
View attachment 2410610
View attachment 2410611
View attachment 2410612
View attachment 2410613
Click to expand...
Click to collapse
Pm'ed you.
Sent from my Galaxy Nexus using XDA Premium HD app

I like wugfresh's Nexus Root Toolkit.

I had the same problem.
As suggested above, get the wugfresh nexus root toolkit. That has the option of flashing a stock rom from a soft-bricked device so long as you can get to the bootloader (which is where you are).

I had the same issue - I'm wondering how many others are getting this too. I'm in no way conversant with this kind of technical challenge so I had a few hours of stress thinking my tablet was knackered.
I tried mskips and wug's toolkits on my bootcamp partition in but couldnt get them to work. I tried following the manual fastboot recovery then ADB sideloading the image but that kept failing too.
In the end, I use the mac toolkits (here: http://forum.xda-developers.com/showthread.php?t=2063042) to get back to android 4.2, then let the device receive OTAs. The 4.4 OTA installed fine this way around.

Nexus 4 dead on 4.4.3 official

Hello, i whant to put 4.4.3 on N4 and with normal flash-all.bat(did it many times before on 4.4.2) and then phone was flashing booloader..waiting devices...and nothing.Phone screen is black only a sound on windows when i connect it.
How can i fix my nexus?
Edit: 1)if i shutdown with pwrbutton 10 sec and turn on via pwr+volume i hear as i connected the phone
2)if turn on normal red light a few sec..
Bricked???

Are you able to get to bootloader? Was it unlocked before you flashed the 4.4 3 image
Sent from my HTC One using Tapatalk

mrao said:
Are you able to get to bootloader? Was it unlocked before you flashed the 4.4 3 image
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
1)I had PA before on it
2)Yes i was unlocked
3)Black screen...nothing.Just a beep like i connect it to pc....and a red dot a few seconds.

krystyuc said:
1)I had PA before on it
2)Yes i was unlocked
3)Black screen...nothing.Just a beep like i connect it to pc....and a red dot a few seconds.
Click to expand...
Click to collapse
Just a wag, but have you tried letting it charge first?
Sent with my Nexus® 10 minus 3

Berrydroidcafe said:
Just a wag, but have you tried letting it charge first?
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
Yes.
Edit: If i plugit into a new pc it shows me
{
"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"
}
After some serch i think it's bricked....only Jtag can fix it

Don't think its bricked. Try type "fastboot devices" in a command prompt in your fastboot folder. If it shows up under listed devices its not bricked. I've had this happen where just the file that makes the screen light up didn't get installed. Just have to reinstall the bootloader. No big deal.
Scratch that!
I'll buy it from you for $5

M3drvr said:
Don't think its bricked. Try type "fastboot devices" in a command prompt in your fastboot folder. If it shows up under listed devices its not bricked. I've had this happen where just the file that makes the screen light up didn't get installed. Just have to reinstall the bootloader. No big deal.
Scratch that!
I'll buy it from you for $5
Click to expand...
Click to collapse
1)Already tryed that and the adb devices...no luck
2)Nothing is displayed on my n4 screen,absolutly black,but it's still on
3)my pc dose a sound when i connect/disconnect the phone
I found something
"Seems that while flashing that ROM you have managed to destroy parts of the Bootloader, wich finaly results in the device doing nothing. (Black Screen etc)
Partitialy you are right yes "QHS-USB Mode" means your device is hard bricked an in the so called QHS-USB Download Mode
but this mode is meant for vendors to flash bootloaders etc on the devices.
To access the device in a propper way u need some "non-public" tools wich QCOM usaly only supplies to vendors not to endusers!
Without thoose programs u will be not able to access the device in any way, even with thoose tools without the expierience and knowledge and files u need, i guess u will not be able to recover it yourself.
I do not want to risk some trouble with QCom at all so i do not can point u to the propper tools to use but i'm sure when using google u will be able to find out what tools i'm talking about.
In my mind the best way for you to recover that device is a JTAG
So my suggestion is to search for a JTAG in your region a JTAG in europe usaly is arround 30 euro but price can differ in your country"

So.....no luck till now,the phone is hardbricked.I'll send it monday to warranty,maybe they will fix it for free if not....then this is an excuse to buy N5

Need to turn on Moto X Pure *without* power button (not rooted)

Hello all,
I'm in a jam here and hoping one of you can help me out.
The power button on my Moto X Pure Edition, which is not rooted, has stopped working completely. The battery died overnight and, obviously, the phone powered off. Now I can't turn it back on. I'd like to get it turned on or at least get my personal data off of it. Does anyone have any ideas?
I have figured out how to get it into AP Fastboot Flash Mode by holding down the Volume Up & Volume Down buttons simultaneously while plugging it into a power source. But, I cannot select "START" (or anything else) from Fastboot because my power button doesn't work.
Hoping I can figure out how to do this without taking apart the phone, which will void my warranty and probably won't result in me being able to fix it anyway.
Thanks so much for your help!

lowbar said:
Hello all,
I'm in a jam here and hoping one of you can help me out.
The power button on my Moto X Pure Edition, which is not rooted, has stopped working completely. The battery died overnight and, obviously, the phone powered off. Now I can't turn it back on. I'd like to get it turned on or at least get my personal data off of it. Does anyone have any ideas?
I have figured out how to get it into AP Fastboot Flash Mode by holding down the Volume Up & Volume Down buttons simultaneously while plugging it into a power source. But, I cannot select "START" (or anything else) from Fastboot because my power button doesn't work.
Hoping I can figure out how to do this without taking apart the phone, which will void my warranty and probably won't result in me being able to fix it anyway.
Thanks so much for your help!
Click to expand...
Click to collapse
Do you have fastboot installed on your computer? If you do then issue the following command : fastboot reboot
Your phone will now start up.
If you don't, install it. You will have to research how to do it for your system. I'm on Arch Linux, so won't know how to help you, but there will be a google guide.

sr.perro said:
Do you have fastboot installed on your computer? If you do then issue the following command : fastboot reboot
Your phone will now start up.
If you don't, install it. You will have to research how to do it for your system. I'm on Arch Linux, so won't know how to help you, but there will be a google guide.
Click to expand...
Click to collapse
Thank you for the suggestion. Got fastboot installed (used this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118) but it doesn't appear to be recognizing my device. See attached image. Still working on it.
{
"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"
}

lowbar said:
Thank you for the suggestion. Got fastboot installed (used this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118) but it doesn't appear to be recognizing my device. See attached image. Still working on it.
Click to expand...
Click to collapse
Hilarious. After an hour of fumbling around I figured out the USB port I had the phone plugged into was bad. Plugged it into one on the other side of the computer, recognized, rebooted, good to go.
Thanks so much for your help.

lowbar said:
Hilarious. After an hour of fumbling around I figured out the USB port I had the phone plugged into was bad. Plugged it into one on the other side of the computer, recognized, rebooted, good to go.
Thanks so much for your help.
Click to expand...
Click to collapse
Glad you sorted it.

sr.perro said:
Glad you sorted it.
Click to expand...
Click to collapse
hey man. Im having the same issue with my phone, but no matter what i do my pc still wont detect my phone. i don tknow what to do please help.