Related
Earlier today, I ran the updated 15/10/11 version of the ace hack kit. Like it was suggested, I read through the manual then I re-read it and re-read it again. As suggested, I disabled / uninstalled all security software on my pc and the other superfluous services. Ran the executable drivers file then I set the phone to charge only and usb debugging was ticked.
I then ran the hack-ace.cmd file as administrator and let the program do it's thing.
It appeared to have completed without any glitches in the suggested 6 minutes.
However, on the phone, all was not well. Since running this, the screen remains blank. When I power on, I get the HTC logo and then it disappears / disintegrates into a blank screen and nothing happens.
The only reason I ran this was to get rid of the irritating apps that I never use but have to Kill every day.
Can anyone help to overcome this problem? This was a replacement handset that I had to fight with my insurance company to get only for this to happen.
I am literaly at my wits end.
Thanks
anomander0108 said:
Earlier today, I ran the updated 15/10/11 version of the ace hack kit. Like it was suggested, I read through the manual then I re-read it and re-read it again. As suggested, I disabled / uninstalled all security software on my pc and the other superfluous services. Ran the executable drivers file then I set the phone to charge only and usb debugging was ticked.
I then ran the hack-ace.cmd file as administrator and let the program do it's thing.
It appeared to have completed without any glitches in the suggested 6 minutes.
However, on the phone, all was not well. Since running this, the screen remains blank. When I power on, I get the HTC logo and then it disappears / disintegrates into a blank screen and nothing happens.
The only reason I ran this was to get rid of the irritating apps that I never use but have to Kill every day.
Can anyone help to overcome this problem? This was a replacement handset that I had to fight with my insurance company to get only for this to happen.
I am literaly at my wits end.
Thanks
Click to expand...
Click to collapse
i think you need to install custom rom and flash it in recovery follow the steps in instruction in ace hack kit because it happen to me also when I ran the ace hack kit..
avnr said:
i think you need to install custom rom and flash it in recovery follow the steps in instruction in ace hack kit because it happen to me also when I ran the ace hack kit..
Click to expand...
Click to collapse
Yes this is the best thing to do. Something must have corrupted your stock ROM. If AAHK completed properly, then you should have ClockworkMod recovery installed.
The first thing I did was install 4EXT recovery but thats not necessary, that was just a personal choice.
So these are the steps you should take:
1: Download a new ROM and put it on your SD card in a convenient place (I recommend the RCMIX32 Runny 3.1 ROM)
2: Remove the battery and reinsert the battery
3: Hold down the volume down button and then hold down the power button. You will get to a white screen with some green robots on the bottom. This is the bootloader screen. You will have to wait a bit for it to finish scanning the SD card. It will tell you when it is finished
4: Use the volume buttons to select recovery and press the power button to select it
5: After a few seconds the recovery environment will appear
6: Go to the wipe menu. Wipe data, cache and dalvik cache (and system if you have the option. I havent used Clockworkmod in a while so I cant really remember what options you have there)
7: Go a few menu's back and select Install zip from SD card
8: Select the zip file
9: Press yes on the confirmation screen
10: When it is finished, click reboot now. It might be on the menu back
This will install a new ROM and it should work properly. If you have any problems along the way just say and we will help to the best of our ability
Thanks for the responses.
I don't think ClockworkMod is installed as there are no options available when I select recovery. It just reboots the device back to the HTC splash screen which as mentioned then fades / deteriorates to a black screen. I had tried the Android HD Revolution rom but no difference.
One thing I did yesterday in my panic was to select 'Factory reset'. Will this have usb debugging setting?
Finally, when I connect to a pc, it doesn't see it. Is this because it's still set on charge only mode?
I'm probably my own worst enemy
If you finally press "Factory reset" you will reset USB debugging, then you can't root your phone using this tools kit. Try to reinstall the stock rom.
If you didn't root your DHD. Phone may still under warranty.
Hi Guys
I've managed to get this back up and running again.
After a lot of playing about with various file downloads last night, I finally managed to get my pc to see the phone. After that, I just downloaded a stock rom and installed it.
After this fright, I am reluctantly going to stick with this and not bother with rooting / custom roms.
Anyway, many thanks for all your responses, I really appreciate the time you took to helpo me out.
This forum absolutely rocks.
Hi,
I've just downloaded, I read the 'effen' manual and then ran ace-hack, it seems to have worked except I can't see clockwork mod recovery?
I can see superuser and ROMmanager, is it still ok to try and download and flash a custom ROM?
---------- Post added at 09:46 PM ---------- Previous post was at 09:03 PM ----------
Well to confirm my noob status I have now found that clockwork mod recovery is indeed installed (I assume you're not meant to be able to see it as an app as it sits at a lower level).
I downloaded the CM7 ROM, so have booted up into recovery mode, have wiped/formatted as instructed but when I choose the zip file from SD card it appears to start then aborts installation...help!!!!
Hi juicyp
juicyp said:
Hi,
I've just downloaded, I read the 'effen' manual and then ran ace-hack, it seems to have worked except I can't see clockwork mod recovery?
I can see superuser and ROMmanager, is it still ok to try and download and flash a custom ROM?
---------- Post added at 09:46 PM ---------- Previous post was at 09:03 PM ----------
Well to confirm my noob status I have now found that clockwork mod recovery is indeed installed (I assume you're not meant to be able to see it as an app as it sits at a lower level).
I downloaded the CM7 ROM, so have booted up into recovery mode, have wiped/formatted as instructed but when I choose the zip file from SD card it appears to start then aborts installation...help!!!!
Click to expand...
Click to collapse
Did you check the MD5 Checksum of the .zip before you copied it to your SD Card? as it might is some way have got corrupted.
Here is a link to what I always use before I copy anything to my SD Card or install on my OS System:- MD5 Check 2.1.
Take Care
TheQuest
Thanks!
I'm all sorted (I think, fingers crossed).
It was principally because of the mac unzipping (Safari preferences not checked), this was the original and prime fault.
That caused me to doubt my partitions on the SD card (google is sometimes your enemy) which I altered.
So what then happened was CM7 installed but upon reboot looped continuously on the android skateboarding screen.
I finally resorted to formatting the SD Card, reapplying the CM7 zip and the google zips and so far it looks good.
Of course I (me and me alone) has stuffed up all the user data I had on the SD card. I might try to recover some photos but stuff like contacts I can regenerate no major loss there.
Thanks for replying!!
CM7 - the experience thus far
Well its 72 hours since I took the plunge!
Initially it looked odd and felt flakey, the Market refused to download 80% of the apps I tried. I resolved this (not sure if it was the right way) by going into recovery and clearing the cache 2-3 times and eventually downloaded all of my old apps.
Some apps cause frequent force-closes, I assume because they've not been updated for Gingerbread? Thats a very minor irritant, I can easily live without these apps anyway.
Battery life hasn't noticeably altered yet but I suppose I have been constantly been tinkering, playing with settings, trying wifi (seems a little less sensitive to signals) and gauging how the radio is working - I seem to get HSPDA a lot less and resort to 3G more than I previously did?
So, done it, like it despite some minor reservations - now what, is there anything else I can do to improve the experience?
I must add one thing this has shown me - I really really know very little about what goes on under the hood. Despite 20+ years experience in CIS this is a very different world and all credit to those who have developed CM7!!
Please help if you can.. please
Hello!!
I am desperately seeking some guidance. Please.
So, I used to have a HTC Inspire 4G and in June I rooted it successfully.. then installed Cyanogenmod 7 etc.. everything worked great. I unfortunately lost the phone and because of insurance got a new one.
When I rooted the first time I used the old school method that was in the XDA forum.. ADB..etc.. but today... with the new replacement..
I downloaded Advance ace hack kit 29102011 (ahhk 29102011.zip) which after reading all the stuff I thought would be just a quicker way to get rooted. I used the same PC that I used before.
This time, unfortunately I am getting a black screen, right after the HTC splash screen shows up.. it fades to black.
I can get to the "Hboot" screen but removing the battery, then restarting by holding the power and the down vol button.
Tried Factory reset.. still fades to back
Tried Recovery .. still fades to back
The device will not be recognized on my laptop when connected to USB..
Am I stuck? Do I have any options?
I should have done what I did before.. but am at a loss right now.. will you please help me.
Please.
Thanks a million in advance for your responses.
Please help.
ravennyc said:
Hello!!
I am desperately seeking some guidance. Please.
So, I used to have a HTC Inspire 4G and in June I rooted it successfully.. then installed Cyanogenmod 7 etc.. everything worked great. I unfortunately lost the phone and because of insurance got a new one.
When I rooted the first time I used the old school method that was in the XDA forum.. ADB..etc.. but today... with the new replacement..
I downloaded Advance ace hack kit 29102011 (ahhk 29102011.zip) which after reading all the stuff I thought would be just a quicker way to get rooted. I used the same PC that I used before.
This time, unfortunately I am getting a black screen, right after the HTC splash screen shows up.. it fades to black.
I can get to the "Hboot" screen but removing the battery, then restarting by holding the power and the down vol button.
Tried Factory reset.. still fades to back
Tried Recovery .. still fades to back
The device will not be recognized on my laptop when connected to USB..
Am I stuck? Do I have any options?
I should have done what I did before.. but am at a loss right now.. will you please help me.
Please.
Thanks a million in advance for your responses.
Please help.
Click to expand...
Click to collapse
Try to run the latest RUU.
Similar Issue
Hi all,
Similar issue as the thread, during AAHK had a "file not found" issue and now, only get HTC screen fading to black. Getting into HBOOT works fine.
I do have S-OFF but;
Have tried recovery, nothing.
Any RUU nothing
ADB shows device is offline
running any other option in AAHK device offline
Any help would be greatly appreciated.
Cheers!
I might ruined my defy+
When I bought it, it was in German, i changed it to dutch and had android 2.3.6
Flashed it with the all-in-one Defy beginners guide
Had a working android version afterwards, only calling/sms/2g and 3g didn't work. Didn't try to fix it because i wanted to flash the latest cm7.2.
Don't know what i did after that (afterwards we went to carnaval, so i drank to much). I know I installed a uk rom 2.3.6 version and here it went wrong. It went into a bootloop. Got the M logo and spinning white thing around. Tried installing differnt roms, none worked. And now my phone doesnt do anything, wont start or go in to bootloader. RDS light find it but white led wont go on.
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1040020f1fab3a0a0000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public ID: 9aff8fe986ef65565a0a1e805942bbeaa8460f87
BP Public ID: 0000000000000000000000000000000000000000
Tried different roms, didn't work. Tried the following
"Common Problems/Questions
Black Screens when booting up: (!) Tried to install a version of Android with a lower CG Version than the one currently on the phone.
Weird behavior after installing a Fixed SBF: Install a matching Nandroid backup with your SBF, and remember to clear Cache/Dalvik Cache using Recovery.
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backupwent wrong here, multiupload is gone so couldnt continue
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot"
Anyone got a answer for this? I am searching this forum for over 6 hours in the last days.
Mate, when you say it doesn't start... Nothing happens when you hold the power button? Not even the M logo (bootscreen) shows up?
Can you access stock recovery? When your phone is off, press and hold Volume UP button and power button. Does anything happen?
When you enter the bootloader, what does it say? Please write everything down.
I'm 99% sure that your phone isn't dead, you've just flashed some wrong stuff. First of all, CM7.2 is not compatible with 2.3.6. There is a CM7.2 DEFY+ version, but it works with 2.3.4 only. If you used a normal defy CM7.2, it's for Froyo only. Anyway, whatever version you used, it's not strange that it wasn't successful.
P.S I've done the same thing first time I've tried to update to some custom ROM
One more thing. After CM7.2 flashing resulted in a frozen bootscreen (M logo), please write down all the steps you did? It's kinda hard to figure out from that guide you've posted..!
niksy+ said:
Mate, when you say it doesn't start... Nothing happens when you hold the power button? Not even the M logo (bootscreen) shows up? Yes nothing shows, looks like the batt is empty but that isn't the case
Can you access stock recovery? When your phone is off, press and hold Volume UP button and power button. Does anything happen?
No nothing
When you enter the bootloader, what does it say? Please write everything down.
I'm 99% sure that your phone isn't dead, you've just flashed some wrong stuff. First of all, CM7.2 is not compatible with 2.3.6. There is a CM7.2 DEFY+ version, but it works with 2.3.4 only. If you used a normal defy CM7.2, it's for Froyo only. Anyway, whatever version you used, it's not strange that it wasn't successful.
P.S I've done the same thing first time I've tried to update to some custom ROM
One more thing. After CM7.2 flashing resulted in a frozen bootscreen (M logo), please write down all the steps you did? It's kinda hard to figure out from that guide you've posted..!Didn't came to that
Click to expand...
Click to collapse
Do you have a good link witch describes how to go from 2.3.6 to 2.3.4? For when my phone works again.
thank you.
taarmen said:
Do you have a good link witch describes how to go from 2.3.6 to 2.3.4? For when my phone works again.
thank you.
Click to expand...
Click to collapse
Not really, buddy :-/
You should have answered my questions, that way I could have written you a step-by-step guide
What you should do:
0. Phone's off
1. Enter stock recovery
2. Wipe data and wipe cache
3. Turn off phone
4. Enter bootloader
5. Flash full stock 2.3.4 sbf - http://www.mirrorcreator.com/files/1HLS00W4/
6. Your phone should boot up normally after the process is done
If you can not enter stock recovery, then just enter bootloader and flash the sbf. The thing is, those fixed sbf's don't have all the codegroups, so some stuff from CM7.2 has probably remained in your system. Full sbf should do a much better job. But, it would be great if you can enter stock recovery. That way the flashing must be successful.
Note, I haven't tried that 2.3.4 sbf! But it's the only one I could find. I need it too and I will test it tomorrow morning, so if you want, you can wait for me to test it first. (I need it cause my defy+ is on Froyo now, and Froyo and defy+ don't really like each other ) I have tested one 2.3.5 sbf, I can point it to it if you wish so. (It doesn't matter which android version it is, as they all have version 6 signed codegroups, so you can switch between them without worrying! Only some latest 2.3.6 ROM's are signed as version 7, but it's highly unlikely that you have flashed your phone with one such)
I Agree with niksy+, can't help, I have a Green Lens Defy, so all i have to say is good luck, and a step-by-step would have been nice
Thank you for the effort, my defy+ is braindead. When i connect it to my pc the white top led goes on. And that is it, nothing on RSD, wont boot, wont go in the bootloader
There's a trick for that i think i remeber it's:
Plug phone it with rsd ready (the phone should be dead with white led)
Pull battery out and press vol up + down
Put battery back in
It might not be exactly that but i can assure you i read somewhere what to do with your issue
Sent from my 1Ghz CM7 + CM9 Defy
crakeron said:
There's a trick for that i think i remeber it's:
Plug phone it with rsd ready (the phone should be dead with white led)
Pull battery out and press vol up + down
Put battery back in
It might not be exactly that but i can assure you i read somewhere what to do with your issue
Click to expand...
Click to collapse
That process is called "force bootloader method" and it can be done on any and every Motorola, as far as I know..! (I've done it on my previous E398, ROKR E1 and ROKR E8 phones (yeah, I've killed all my phones dozens of times )) and, yes, sometimes it does get you into the bootloader when the normal way doesn't!
So, as crakeron said:
1. Battery out
2. Wait couple of seconds (to make sure the phone goes completely out of power > completely off)
3. Start up RSDlite (v5.3.1 minimum!)
4. Connect your phone to the usb (yes, without the battery)
5. Now, you need to press and hold a combination of buttons and insert the battery WHILE holding the buttons pressed and keep them pressed for couple of seconds.
*I'm not sure what the combination of keys is it, but I would try:
a) Volume UP and Volume Down
b) Volume UP and Power Button
c) Volume Down and Power Button
d) Volume UP and Volume Down and Power Button (this one is the least likely, I think)
6. Your phone should show up in RSDlite and you can flash it then. The bootloader maybe won't show up on the phone screen, but if it shows up in RSDlite - it's all that you need!
This forcebootloader thing isn't quite easy and it may take couple of tries to hit the exact needed timing, so try all combinations a couple of times. Let us know if you pull this off!
i have the popcorn out for this one - fun thread! will the defy be rescued??? tune in next time, same bat board, same bat sub board!
taarmen said:
I know I installed a uk rom 2.3.6 version and here it went wrong. It went into a bootloop. Got the M logo and spinning white thing around. Tried installing differnt roms, none worked. And now my phone doesnt do anything, wont start or go in to bootloader. RDS light find it but white led wont go on.
Click to expand...
Click to collapse
If the UK 2.3.6 ROM you installed was this one then you will not be able to downgrade to any other 2.3.6 ROM (except I think this one), let alone 2.3.5, 2.3.4 or Froyo (it does say that in the thread you linked).
You should still be able to flash either of those 2.3.6 ROMs with RSD Lite. But no other ROM - until some more with CG 7 or above become available - and it's currently not rootable either. So no chance of CM7 or other such like goodies. At least you should be able to get a working phone that you can sell on eBay if you desperately don't want to be stuck with the T-Mobile 2.3.6 ROM.
Morals of the story:
1) Read before you flash
2) Keep a written record of what you did (I know, boring)
Good luck, let us know how you get on.
niksy+ said:
That process is called "force bootloader method" and it can be done on any and every Motorola, as far as I know..! (I've done it on my previous E398, ROKR E1 and ROKR E8 phones (yeah, I've killed all my phones dozens of times )) and, yes, sometimes it does get you into the bootloader when the normal way doesn't!
So, as crakeron said:
1. Battery out
2. Wait couple of seconds (to make sure the phone goes completely out of power > completely off)
3. Start up RSDlite (v5.3.1 minimum!)
4. Connect your phone to the usb (yes, without the battery)
5. Now, you need to press and hold a combination of buttons and insert the battery WHILE holding the buttons pressed and keep them pressed for couple of seconds.
*I'm not sure what the combination of keys is it, but I would try:
a) Volume UP and Volume Down
b) Volume UP and Power Button
c) Volume Down and Power Button
d) Volume UP and Volume Down and Power Button (this one is the least likely, I think)
6. Your phone should show up in RSDlite and you can flash it then. The bootloader maybe won't show up on the phone screen, but if it shows up in RSDlite - it's all that you need!
This forcebootloader thing isn't quite easy and it may take couple of tries to hit the exact needed timing, so try all combinations a couple of times. Let us know if you pull this off!
Click to expand...
Click to collapse
Wel I hope that iolinux333 has enough popcorn because non of the mentioned forced bootloader steps works
When i put my + on the usb nothing happens for a few minutes after that a withe led will shine. Thats all.
Thank you all!
I asked you already on tweakers.net, but I'll ask the same questions here:
What's the status of your battery? (Full, empty, half-full?) What version of RSD-lite did you use? What version of drivers are installed on your computer? How many times did you try the different key combinations after pulling out battery, connecting to your computer? What did you see at each step?
Fotogravin said:
I asked you already on tweakers.net, but I'll ask the same questions here:
What's the status of your battery? (Full, empty, half-full?) What version of RSD-lite did you use? What version of drivers are installed on your computer? How many times did you try the different key combinations after pulling out battery, connecting to your computer? What did you see at each step?
Click to expand...
Click to collapse
Been away for a few days. Back and ready to repair, I appreciate all your help.
no sim and sd-card
win7 64-bit
Battery is Full
RSD Lite version 5.6
motorola 5.4.0 usb drivers 64-bit
Tried all combinations at least 10 times. First I disconnect usb -> take out bat -> make combination and count to ten -> put in bat -> holds for minimum of 10seconds -> click on "show device" on RSD -> Nothing show
Nothing ever shows.
You really should give us more... What happens when you try to power it on? I think you only get black so, does power+vol(+) give you something or do you get a white led when you plug it in the pc?
If yes, it should be recognizable. I don't think you can get into bootloader mode when power-on gives nothing. Maybe by putting the battery back while holding the volume(+) I think and the power button. (like stated earlier) But I thought the white led was enough.
If you don't get the white LED and you only get black screen, maybe try to borrow a battery from someone...
If you get the white LED but RSD doesn't find it: try a few ports, maybe other PC, ....
I also think a Win7 window should pop up first with something like: 'Motorola diag... device found' (or maybe something completely different)
Then I think the easiest = warranty. I'm from Belgium. Had to send it to a repair center in the Netherlands (for a totally different reason) and it took them a while to fix it (it needed to be send elsewhere, .. ).
Just tell them you tried to update your rom and it wend wrong. Anyway, it takes about a month I think...
labsin said:
You really should give us more... What happens when you try to power it on?
Compleet black nothing happens
I think you only get black so, does power+vol(+) give you something
Still nothing
or do you get a white led when you plug it in the pc?
Yes I got that
If yes, it should be recognizable. I don't think you can get into bootloader mode when power-on gives nothing. Maybe by putting the battery back while holding the volume(+) I think and the power button.
Still nothing, not even the white led
(like stated earlier) But I thought the white led was enough.
If you don't get the white LED and you only get black screen, maybe try to borrow a battery from someone...
If you get the white LED but RSD doesn't find it: try a few ports, maybe other PC, ....
Haven't been able to trie different pc's. Tried differt usb ports, even those of my mouse and keyboard so I know they fully function, only white led
I also think a Win7 window should pop up first with something like: 'Motorola diag... device found' (or maybe something completely different)
nothing to show
Then I think the easiest = warranty. I'm from Belgium. Had to send it to a repair center in the Netherlands (for a totally different reason) and it took them a while to fix it (it needed to be send elsewhere, .. ).
Just tell them you tried to update your rom and it wend wrong. Anyway, it takes about a month I think...
Think i got to trie it,what can hapen if they found out i lied?
Click to expand...
Click to collapse
Thank you for helping me, I just tried RSD Lite 5.7 and also nothing.
Sorry a bit late. You didn't lie
I should be recognizable. Especially with a full battery. If not, you might have had a bad install and they might have to replace the botherboard.
If you don't mind waiting a couple of days longer, bring it to the place you bought it. Then the delivery costs are free. But could take 1-2 weeks longer.
IF they do conclude it is your fault then you have to pay an amount of money to deliver it back or you can pay for repairing it (for motherboard could be 80-100 or more, actually don't know). Again when you went trough shop this takes a week or so. (motorola => shop => 3 days nothing => you => 3 days nothing => motorola).
They are not that picky at motorola except for water damage maybe (check for a red sticker below the battery. If it is still white => no prob)
Thank you all. I've sent my phone to the store where i bought it, on friday and the next friday i got it back. With a fresh stock rom.
T-Mobile SGH-T989. Will power on, splash screen will appear, and screen will go black. No further activity allowed. Can use vol up/down + power to get into Android System Recovery, but wipe data/factory reset OR wipe cache partition options change nothing.
Daughter states OTA Update was in process, when she drove into area without signal. (The OTA Update occurred 02/06/13). Phone would not leave OTA status. She took out battery, and the above condition began.
No attempts have been made to manually change/upgrade ROM on phone.
DownloadedKies, and the phone is not recognized/not connect to PC
And of course, T-Mobile is no help, only offering to sell me a new phone.
Curious if others have/had similar issues, and if so, how they corrected. Otherwise, would like some assistance in installing a new ROM is possible.
(p.s. I have searched forums/threads and did not discover anything similar)
Seems like power button is funk up
Sent from my SGH-T989 using xda app-developers app
Badwill said:
T-Mobile SGH-T989. Will power on, splash screen will appear, and screen will go black. No further activity allowed. Can use vol up/down + power to get into Android System Recovery, but wipe data/factory reset OR wipe cache partition options change nothing.
Daughter states OTA Update was in process, when she drove into area without signal. (The OTA Update occurred 02/06/13). Phone would not leave OTA status. She took out battery, and the above condition began.
No attempts have been made to manually change/upgrade ROM on phone.
DownloadedKies, and the phone is not recognized/not connect to PC
And of course, T-Mobile is no help, only offering to sell me a new phone.
Curious if others have/had similar issues, and if so, how they corrected. Otherwise, would like some assistance in installing a new ROM is possible.
(p.s. I have searched forums/threads and did not discover anything similar)
Click to expand...
Click to collapse
Try to boot into recovery mode or download mode, if you can then there's still hope. Try this: http://www.icsforums.com/forum/showthread/6351
If u can get into download mode you can Odin a recovery and then flash a ROM of your choosing, including stock gingerbread or ice cream, just as the phone was prior except with a custom recovery.
In short....follow tutorials on rooting your phone. When it comes time to "flash ROM" flash to whatever u had before the incident - only if u want to.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Badwill said:
T-Mobile SGH-T989. Will power on, splash screen will appear, and screen will go black. No further activity allowed. Can use vol up/down + power to get into Android System Recovery, but wipe data/factory reset OR wipe cache partition options change nothing.
Daughter states OTA Update was in process, when she drove into area without signal. (The OTA Update occurred 02/06/13). Phone would not leave OTA status. She took out battery, and the above condition began.
No attempts have been made to manually change/upgrade ROM on phone.
DownloadedKies, and the phone is not recognized/not connect to PC
And of course, T-Mobile is no help, only offering to sell me a new phone.
Curious if others have/had similar issues, and if so, how they corrected. Otherwise, would like some assistance in installing a new ROM is possible.
(p.s. I have searched forums/threads and did not discover anything similar)
Click to expand...
Click to collapse
Yeah, you can get a stock ROM that can be flashed via Odin usually in a thread talking about unrooting (or returning phone to stock thread in development and/or general section).
Download the file (should be a good 200-300M area)
Basically, you need Odin (2.65 I believe and yes Odin version matters so if one doesn't try another).
Then, this is tricky, have USB cable connected to computer and other end of the same cable in your hand right as you boot the phone holding the vol keys as you would to enter recovery but plug the USB in as soon as you feel the boot vibrate (there is a real trick to it, it may take a few good tries until you get it).
You will then see a warning screen stating not to disconnect it or power off phone during the flash should be vol down to enter download mode.
Now you should see a driver install go on on computer. If it fails be sure to install Samsung kies and that has the drivers if not installed.
Now open Odin, you should see a yellow square appear on one of the com port boxes meaning it sees the phone.
Click the browser button to select the ROM in the pda box in Odin and hit flash or start or whatever.
Be patient, it may seem like it's taking too long at times don't touch the phone or computer, just wait the status window in lower left of Odin will say when it's done.
Just follow any unrooting guides as stated for a stock ROM file and the correct version of Odin.
Sent from my SAMSUNG-SGH-T989 using Xparent Green Tapatalk 2
---------- Post added at 09:53 AM ---------- Previous post was at 08:55 AM ----------
Here is the thread you want. View the very first page and post and that should give you all the files and directions in detail: http://forum.xda-developers.com/sho...WTO]Restore to Stock/Recover from a Bad Flash
Sent from my SAMSUNG-SGH-T989 using Xparent Green Tapatalk 2
I have a Hard bricked Samsung Galaxy Note 4 Sprint sm-n910p all stock carrying the Qualcomm 805 Snapdragon processor. Like a week after it updated OTA to the Lollipop 5.1.1 it just died in my hands one day after i rebooted it because it kept freezing up. It's a relatively new phone, i had it for about 9 months. I can't get it to boot in download mode nor recovery mode. I tried a USB Jig to get it into download mode but it did not help. Odin does not recognize it, my computer only recognizes it as QHSUSB_BULK 9008. I have another Note 4 same model and carrier as mine running the same Lolipop 5.1.1. I swapped the battery and it still did not boot. I was wondering if anyone on here happens to have a debrick image file for this model that they can assist me with. I have researched on here but so far i have only encountered debrick files and debrick methods for most other models except for the sm-n910p model. I have also tried using my other note 4 to create a debrick file but i was unsuccessful with the create debrick program i tried to run on the second note 4. No one seems to be able to JTAG the note 4 well at least not just yet. The second note 4 i have is not rooted nor do i have any custom roms or custom recovery installed on it, i don't really want to void my warranty or have that second phone bricked as well. Is there anyone on here who may have a debrick image for this model or is there a way i can create a working debrick file from my working note 4 so i can write it to an SDcard to revive my dead note 4? Any assistance given would be greatly appreciated!
I am having the same issue http://forum.xda-developers.com/note-4-sprint/help/note-4-boot-t3423362 My device will not boot into any mode and my computer does not recognize the device the only thing it does(my computer) is play the sound notification when a device is plugged in and taken out. Does anyone have suggestions on how to solve this problem?
http://forum.xda-developers.com/note-4-sprint/help/sprint-note-4-n910p-boot-failure-t3431069 might help.
ME too !!!!!
BrightSoundz said:
I am having the same issue http://forum.xda-developers.com/note-4-sprint/help/note-4-boot-t3423362 My device will not boot into any mode and my computer does not recognize the device the only thing it does(my computer) is play the sound notification when a device is plugged in and taken out. Does anyone have suggestions on how to solve this problem?
Click to expand...
Click to collapse
ME too bro , exactly like you , i don't know what to do
Will the debrick img work for it ? i downloaded it already.
---------- Post added at 11:26 PM ---------- Previous post was at 11:19 PM ----------
i think this thread may help you
---------- Post added at 11:38 PM ---------- Previous post was at 11:26 PM ----------
BrightSoundz said:
I am having the same issue http://forum.xda-developers.com/note-4-sprint/help/note-4-boot-t3423362 My device will not boot into any mode and my computer does not recognize the device the only thing it does(my computer) is play the sound notification when a device is plugged in and taken out. Does anyone have suggestions on how to solve this problem?
Click to expand...
Click to collapse
does it show on your pc device manager under disk drives this : (QHUSB 9008 mode) ???
---------- Post added at 11:48 PM ---------- Previous post was at 11:38 PM ----------
BrightSoundz said:
I am having the same issue http://forum.xda-developers.com/note-4-sprint/help/note-4-boot-t3423362 My device will not boot into any mode and my computer does not recognize the device the only thing it does(my computer) is play the sound notification when a device is plugged in and taken out. Does anyone have suggestions on how to solve this problem?
Click to expand...
Click to collapse
does it show on your pc device manager under disk drives this : (QHUSB 9008 mode) ???
Try going here
Hey i updated my note 4 spirit version using wi fi and then installed it but after the installation the phone never rebooted. And now aftr removing the battery for sometime and pressing power button for a min i.e soft bricking it. It starts but again goes to the same installation thing and the same thing happens.What should i do can ny1 suggest ? Thank you
vihitshah said:
Hey i updated my note 4 spirit version using wi fi and then installed it but after the installation the phone never rebooted. And now aftr removing the battery for sometime and pressing power button for a min i.e soft bricking it. It starts but again goes to the same installation thing and the same thing happens.What should i do can ny1 suggest ? Thank you
Click to expand...
Click to collapse
Not sure what installation screen you're seeing but hopefully it's either booting to system and going through the update prompts or booting to download or recovery modes(?)
Since you're trying to update over the air (OTA), can I properly guess you're not rooted? If you're unsure why it rebooted during the update, ask yourself, did it go back to recovery or did it try to boot as usual?
Without specifics of error, I'm not sure if your phone boots to system OS or not? It's possible the update file was corrupt or rejected for some reason. Reasons that should be included in your request for help.
But there is a simple solution for OTA not cooperating. Rather than trying to remedy that, you could try to update with Smart Switch or KIES or even Odin.
If it's more serious than that, you could include actual screen shots or message(s) you see on phone and PC if using one of the programs above to flash update.
If the phone doesn't boot, you can try this with KIES emergency recovery:
https://forum.xda-developers.com/showpost.php?p=40966346&postcount=1
If that doesn't work, you'll need to learn Odin. But you need to be able to boot to download mode. You can find what you need to get started with here:
https://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
Sent from my SM-N920P using Tapatalk
samep said:
Not sure what installation screen you're seeing but hopefully it's either booting to system and going through the update prompts or booting to download or recovery modes(?)
Since you're trying to update over the air (OTA), can I properly guess you're not rooted? If you're unsure why it rebooted during the update, ask yourself, did it go back to recovery or did it try to boot as usual?
Without specifics of error, I'm not sure if your phone boots to system OS or not? It's possible the update file was corrupt or rejected for some reason. Reasons that should be included in your request for help.
But there is a simple solution for OTA not cooperating. Rather than trying to remedy that, you could try to update with Smart Switch or KIES or even Odin.
If it's more serious than that, you could include actual screen shots or message(s) you see on phone and PC if using one of the programs above to flash update.
If the phone doesn't boot, you can try this with KIES emergency recovery:
https://forum.xda-developers.com/showpost.php?p=40966346&postcount=1
If that doesn't work, you'll need to learn Odin. But you need to be able to boot to download mode. You can find what you need to get started with here:
https://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
Click to expand...
Click to collapse
No the device isnt rooted. It shows that screen in which its written loading recovery or something in blue on top left corner and then it automatically starts installing he update and then it doesn't start at all. It just acts likr a dead phone. Well the phone doesnt respond to any keys now i guess its just dead.
I have attatched a pic showin the error which was displayed earlier mayb it cn help
vihitshah said:
No the device isnt rooted. It shows that screen in which its written loading recovery or something in blue on top left corner and then it automatically starts installing he update and then it doesn't start at all. It just acts likr a dead phone. Well the phone doesnt respond to any keys now i guess its just dead.
I have attatched a pic showin the error which was displayed earlier mayb it cn help
Click to expand...
Click to collapse
mmc_read error is troubling but I'm not sure if the problem is corrupt download or failure to read properly, TBH. I haven't seen that issue in person and from what you describe, I've never heard of the phone continually try to load the same update? But I'm not thinking it's dead just yet.
What condition is your battery? Over 12 months old? Fully charged or at least 80%? Your battery could be a contributing factor here.
Can you get to recovery by pulling battery, discharging power circuit by holding power button down for a minute, reinstalling battery and holding power + vol-up + home together until it vibrates? Try deleting the cache partitions first and try to reboot. If not try factory reset next and try to reboot.
You'll have to decide if you want to wipe data or not but if you get that far, you may consider just flashing with one of the programs I mentioned earlier.
If you want to skip that, I think you can boot into download manually without it trying to flash that update. If it boots to download mode (hold power + vol-down + home until it boots) and waits for you to install something with prompt to press volume up if proceeding to flash, then Smart Switch, KIES or Odin are alternatives to try. Since you're not rooted, you could try the first two and save Odin for last if you prefer less interaction. I'm not sure but maybe Odin is the only alternative unless the other 2 can recognize phone in those states (recovery or download).
The troubling part is that it could be your internal memory failing (eMMC). If that's the issue, you may not succeed in recovering it but possibly temporarily restoring function. I think it may too early to say component failure. Best to try the least invasive, least risky things to give a fair chance of recovery before everything at it.
Give that a try, deciding what steps are applicable. Ask if you have additional questions. I'll need to know what works, what didn't, and what you tried so taking notes is best.
Edit: If you do decide to go with Odin, make sure your PC's task manager doesn't show any open sessions of KIES or Smart Switch, install the Samsung driver from Samsung support for Note 4 and unless you have Windows 10, launch Odin as administrator only.
Sent from my SM-N920P using Tapatalk
samep said:
mmc_read error is troubling but I'm not sure if the problem is corrupt download or failure to read properly, TBH. I haven't seen that issue in person and from what you describe, I've never heard of the phone continually try to load the same update? But I'm not thinking it's dead just yet.
What condition is your battery? Over 12 months old? Fully charged or at least 80%? Your battery could be a contributing factor here.
Can you get to recovery by pulling battery, discharging power circuit by holding power button down for a minute, reinstalling battery and holding power + vol-up + home together until it vibrates? Try deleting the cache partitions first and try to reboot. If not try factory reset next and try to reboot.
You'll have to decide if you want to wipe data or not but if you get that far, you may consider just flashing with one of the programs I mentioned earlier.
If you want to skip that, I think you can boot into download manually without it trying to flash that update. If it boots to download mode (hold power + vol-down + home until it boots) and waits for you to install something with prompt to press volume up if proceeding to flash, then Smart Switch, KIES or Odin are alternatives to try. Since you're not rooted, you could try the first two and save Odin for last if you prefer less interaction. I'm not sure but maybe Odin is the only alternative unless the other 2 can recognize phone in those states (recovery or download).
The troubling part is that it could be your internal memory failing (eMMC). If that's the issue, you may not succeed in recovering it but possibly temporarily restoring function. I think it may too early to say component failure. Best to try the least invasive, least risky things to give a fair chance of recovery before everything at it.
Give that a try, deciding what steps are applicable. Ask if you have additional questions. I'll need to know what works, what didn't, and what you tried so taking notes is best.
Edit: If you do decide to go with Odin, make sure your PC's task manager doesn't show any open sessions of KIES or Smart Switch, install the Samsung driver from Samsung support for Note 4 and unless you have Windows 10, launch Odin as administrator only.
Click to expand...
Click to collapse
Yes until yest i was able to get to recovery by draining the starting circuit by removing battery and pushing power button bt idk nw i m nt able to. Battery is like 1.5 yr old mayb. I hd charged it to 100%
vihitshah said:
Yes until yest i was able to get to recovery by draining the starting circuit by removing battery and pushing power button bt idk nw i m nt able to. Battery is like 1.5 yr old mayb. I hd charged it to 100%
Click to expand...
Click to collapse
I'd advise replacing that battery before trying to recover the phone.
If you were having to pull battery to get to recovery before, I would not have attempted to update with an old and defective battery. It seems that is a symptom of either bad battery or failing eMMC.
I can't say if your eMMC is defective or even if the battery could have contributed to its potential demise.
Hopefully with a new battery fully charged, it flashes and doesn't exhibit such behavior again. Do you have the original USB cable fully functional? If not, consider original replacement for it as well while you're finding replacement battery. As for battery, I'm not sure of a good replacement but others here recommend original or Anker. I wish you success.
I'm interested to hear of your outcome so hopefully the OP doesn't mind the updates; the original failure posted isn't quite the same as yours.
Sent from my SM-N920P using Tapatalk
The battery wasnt working properly earlier and so while updating it mst hv stopped. Inalready replaced it with new original battery
---------- Post added at 06:28 AM ---------- Previous post was at 06:24 AM ----------
hello i have samsung galaxy note 4 version SM-N910P Whenever i turn on the phone it automatically boots into recovery mode and starts installing system update and then after 100 % it switches off and never turns on back. Please Suggest me some remedy. Thank you
---------- Post added at 06:30 AM ---------- Previous post was at 06:28 AM ----------
samep said:
I'd advise replacing that battery before trying to recover the phone.
If you were having to pull battery to get to recovery before, I would not have attempted to update with an old and defective battery. It seems that is a symptom of either bad battery or failing eMMC.
I can't say if your eMMC is defective or even if the battery could have contributed to its potential demise.
Hopefully with a new battery fully charged, it flashes and doesn't exhibit such behavior again. Do you have the original USB cable fully functional? If not, consider original replacement for it as well while you're finding replacement battery. As for battery, I'm not sure of a good replacement but others here recommend original or Anker. I wish you success.
I'm interested to hear of your outcome so hopefully the OP doesn't mind the updates; the original failure posted isn't quite the same as yours.
Click to expand...
Click to collapse
Hey thank you i replaced my battery and now i am facing an issue of installing system update boot loop. The phone automatically keeps on doing that. Please suggest me some remedy
Thank you
vihitshah said:
The battery wasnt working properly earlier and so while updating it mst hv stopped. Inalready replaced it with new original battery
---------- Post added at 06:28 AM ---------- Previous post was at 06:24 AM ----------
hello i have samsung galaxy note 4 version SM-N910P Whenever i turn on the phone it automatically boots into recovery mode and starts installing system update and then after 100 % it switches off and never turns on back. Please Suggest me some remedy. Thank you
---------- Post added at 06:30 AM ---------- Previous post was at 06:28 AM ----------
Hey thank you i replaced my battery and now i am facing an issue of installing system update boot loop. The phone automatically keeps on doing that. Please suggest me some remedy
Thank you
Click to expand...
Click to collapse
If you're not rooted, you may be able to recover it with KIES or Smart Switch on your PC. Google these if you need them. These offer more automation and convenience than Odin but these also may only work on a phone that's not rooted or modified.
Otherwise, close those sessions on PC's task manager and download Odin and stock tar and flash firmware with that. You would also need to install the USB driver for your phone. You can find stock tar and Odin in a thread in this forum's general thread. Samsung USB driver can be found on Samsung support for Note 4.
Have you had failure to boot that booted into download and mentioned abnormal boot with eMMC read or write failure? Hopefully not; you just need to flash with one of those utilities.
eMMC failures are too often inevitable hardware failure but some manage to continue unlocking phone without having to pull battery using a wake lock app from Google Play. Any reboot, forced or not may duplicate the issue so they avoid reboots to avoid the frustration of trying to boot without flashing again. Ultimately, a reboot or flash could possibly end the life of a failing eMMC. Some have come back days or hours after removing battery. With a sufficient charge, phone may boot again after being in the battery removed state for long periods.
As far as I know, there's only theories about why eMMC fails. I've often thought heat and having shutdowns with old defective battery may speed the failure before it's life expectancy. Others believe that flashing a lot will reach an early demise but I've also read posts of phones never rooted to fail eMMC; these phones may not have been flashed so much.
Sent from my SM-N920P using Tapatalk
no its not rooted pr modified . so i should try with kies right ?
vihitshah said:
no its not rooted pr modified . so i should try with kies right ?
Click to expand...
Click to collapse
I would say yes to KIES unless you're comfortable with Odin. There's an emergency recovery mode in KIES that may just be as close to plug and play you could hope for. You still have to find it in the UI. It's been a while but I thought it was on a middle tab, middle of screen when launching KIES.
KIES may offer a prompt to recover and will download the firmware automatically. Just read and verify the prompt to ensure it properly recognized your phone model and suggested firmware.
Or do it manually and less convenient with Odin.
Sent from my SM-N920P using Tapatalk
thanks man i did it using emergency software recovery using samsung smart switch. kies is for phones before note 3
vihitshah said:
thanks man i did it using emergency software recovery using samsung smart switch. kies is for phones before note 3
Click to expand...
Click to collapse
You're welcome. And thanks for clarifying.
It boots now?
Sent from my SM-N920P using Tapatalk
samep said:
You're welcome. And thanks for clarifying.
It boots now?
Click to expand...
Click to collapse
yes fit and fine
samep said:
I would say yes to KIES unless you're comfortable with Odin. There's an emergency recovery mode in KIES that may just be as close to plug and play you could hope for. You still have to find it in the UI. It's been a while but I thought it was on a middle tab, middle of screen when launching KIES.
KIES may offer a prompt to recover and will download the firmware automatically. Just read and verify the prompt to ensure it properly recognized your phone model and suggested firmware.
Or do it manually and less convenient with Odin.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I am still facing the issue and the issue is even greater as i am not able to go to download mode. The phone i guess goes into deep sleep mode whenever i try to restart it. I want to flash new firmware using odin as i think as per as some thread here .IS there any way i can go to download mode now ? i think it took place due to inturupted software update .
It used to show eMMC failed. But sometimes the phone boots normally
vihitshah said:
I am still facing the issue and the issue is even greater as i am not able to go to download mode. The phone i guess goes into deep sleep mode whenever i try to restart it. I want to flash new firmware using odin as i think as per as some thread here .IS there any way i can go to download mode now ? i think it took place due to inturupted software update .
It used to show eMMC failed. But sometimes the phone boots normally
Click to expand...
Click to collapse
The only suggestion I can give is pulling the battery for longer periods may temporarily help to get to download mode or boot. Some suggest also discharging the power circuit with battery pulled (hold power button) may decrease these extended battery pulls but I don't know if that helps.
The eMMC needs replacing. Samsung Support can do this fairly economically but there's about a week turnaround.
Battery pull and wake lock app is just a bandaid. Flashing firmware is likely the same.
Wish there were better solutions but I think replacement or repair is your best option.
Sent from my SM-N920P using Tapatalk
Hi all,
I am encountering this strange bug randomly: sometimes the device Is rebooting itself and it goes automatically in recovery mode, sometimes after a reboot it does the same. The error is always: Can’t load Android system. clicking on “try again” solves the issue (sometimes at the first retry, sometimes after some retries).
I’m attaching the error screens, also because the error message is not every time the same (Attaching also a normal way to enter recovery).
Has someone encounter this bug?
Any hints on how to solve this? I haven’t already do a full reset of the phone, but i think it wilL be the next step I’ll do if the phone is continuing like this.
Thanks!
Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.
Arobase40 said:
This mostly happens when you did some tricky things on your phone. lol
If full reset is not enough (specially when the system is missing....) you'd have to restock it with an official Samsung firmware... ^^
Click to expand...
Click to collapse
Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.
Arobase40 said:
Well ok, in your case try to flash back a stock firmware from Samsung with Frija or Samfw (don't forget to supply the correct model and CSC) using PC Odin.
If that don't fix the problem then get in touch with your local Samsung website and you should find a phone number for the after sale service and they will give you the nearest Samsung official repair center from your home.
They should fix this issue very quickly using most probably the same tool which is PC Odin.
If you go to the repair center don't forget to backup all your apps and data, remove your scard if you have one and also your sim card...
Click to expand...
Click to collapse
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)
IvanCattaneo95 said:
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)
Click to expand...
Click to collapse
Idk, seems like a hardware issue to me. Try and have a go at where you've bought it and have them check it over.
My first thought too is hardware.
A few years ago I had something similar with a different phone (Moto G) - as a last ditch effort I popped out the SIM and SD cards and reseated them and it worked perfectly after that. If you have an SD card you might even want to leave it out a few days just to see.
Not saying this is your issue but couldn't hurt to try!