Related
Hello this is my first post by the way and i really need help please i just rooted my lg nitro hd and was flashing the CWM on it and when i turned it off to check if it worked it will not turn back on at all not to cwm or regular boot please someone help me i just got this phone 2 days ago.
thanks in advance
What do you see when you turn the phone on?
does the charging screen come up when it is plugged in?
it doesnt power on at all and the charging screen doesnt come up either
mine too,it doesnt power on at all and the charging screen doesnt come up either,
anyone help!
I don't know a way to fix this problem but I have seen unbricking threads for this phone that may help. I'm not sure though because I haven't tried them. I did however also brick my nitro two days after I got and I brought it back to at&t and acted like I had no clue what was going on. Mine was stuck in a boot loop and possibly fixable but I needed it for work and didn't have time as I was on my way to work.
Sent from my LG-P930 using XDA
Hey try pulling the battery then reinserting it with USB plugged in to see if you can breathe any life into it if you can get anything to show on the screen that would be the first step then after that there may be a chance of rescue also try to let it charge for a while and come back to it, I brought a phone back because nothing would show up on the screen but when I brought it back to the store the Guy got it to bootloop if you can at least get it to do that you can work on unbricking it further
Sent from my LG-P930 using XDA
it doesnt power on at all and the charging screen doesnt come up either
Something like this happened to me when I did a battery pull. My battery wasn't dead at the time either, it had 37%. I ended up sending mine to LG for repair or if you have AT&T, you can get it fixed through them.
I have the same problem, mine just stucks at LG logo and then loops, i don't know what to do, please somebody help us!
warishuku said:
I have the same problem, mine just stucks at LG logo and then loops, i don't know what to do, please somebody help us!
Click to expand...
Click to collapse
Hold down volume down plus power until it goes to the factory reset screen. Press power to "reset" which really takes you to CWM (if you're rooted and have CWM installed). Then from CWM, do a factory reset/wipe data, then flash the zip/gapps (for CM 9), or another ROM if you prefer.
---------- Post added at 12:41 PM ---------- Previous post was at 12:40 PM ----------
kernelpan1c said:
Something like this happened to me when I did a battery pull. My battery wasn't dead at the time either, it had 37%. I ended up sending mine to LG for repair or if you have AT&T, you can get it fixed through them.
Click to expand...
Click to collapse
Agree with kernelpanic. Sounds like a hardware failure. AT&T also has device support centers in certain locations that can swap out your phone in some cases.
dnorthington said:
Hold down volume down plus power until it goes to the factory reset screen. Press power to "reset" which really takes you to CWM (if you're rooted and have CWM installed). Then from CWM, do a factory reset/wipe data, then flash the zip/gapps (for CM 9), or another ROM if you prefer.
---------- Post added at 12:41 PM ---------- Previous post was at 12:40 PM ----------
Click to expand...
Click to collapse
Is this all it takes to "flash a rom"?
Sent from my LG-P930 using XDA
dnorthington said:
Hold down volume down plus power until it goes to the factory reset screen. Press power to "reset" which really takes you to CWM (if you're rooted and have CWM installed). Then from CWM, do a factory reset/wipe data, then flash the zip/gapps (for CM 9), or another ROM if you prefer.
---------- Post added at 12:41 PM ---------- Previous post was at 12:40 PM ----------
Agree with kernelpanic. Sounds like a hardware failure. AT&T also has device support centers in certain locations that can swap out your phone in some cases.
Click to expand...
Click to collapse
Hi! thanks for answering!
Yes, I have CWM installed, when I try to enter with volume down and power, it ask me to click power twice to confirm (as usual), but then when CWM is going to boot, the phone resets, and loops again at the LG logo.
I already tried the unbrick method used here in the forum, but I have a problem with the R&D Test Tool, because when I try to click at "Upgrade Start" in CSE web upgrade test, the program opens LGMobile Support Tool, instead of the screen of "country and language", and finally, when I try to update via LGMobile Support Tool, it doesn't found my device (already put in Download Mode in USB), I don't know what to do, please, any information will be greatly apreciated.
Thanks in advance!
*****..:How to Install ClockWorkMod (CWM) on the Huawei Fusion 2:..*****
_________________________________________________________
Step 1: Download the CWM Recovery Tools File from here! Huawei Fusion 2 CWM Installation Tools
Step 2: Put your Huawei Fusion 2 into fastboot mode. (remember from the walkthrough?)
(Step 2 Continued.. Turn off the phone, once off hold down volume down and the power button simultaneously for 20 SECONDS, you will then see the phone freeze at the AT&T logo.. GOOD this is fastboot!)
Step 3: Open up the CWM Recovery Tools File, and run the "instalador.bat" now plug in your phone, and wait for your computer to recognize it.
Step 4: Once the computer has recognized the phone in fastboot, and you have instalador.bat running, hit the spacebar. It should say something about sending the recovery image (in spanish sorry) if you get stuck on waiting device the computer hasn't recognized the phone. Unplug and replug, now instalador should run. If not the phone isn't in fastboot, so unplug the phone, and take out the battery and go back to step 2 to get into fastboot!
Step 5: Wait for the phone to reboot... Once it does turn it off! (we want to check that CWM is installed..)
Step 6: Now that the phone is off simply hold down the volume UP (not down as in fastboot procedure) while pressing the power button simultaneously, DO NOT STOP HOLDING POWER AND VOLUME UP UNTIL YOUR DEVICE ENTERS RECOVERY MODE!!! (you will know your in recovery mode because you will see a nice fancy top hat with some gears in the middle.. if you successfully installed CWM... if not you will see an android guy and some options like reboot phone, wipe data.. similar options are found in CWM but with much more possibilities of customization unlike the stock recovery... YAY! CWM!
****IF THIS POST HELPED YOU IN ANY WAY PLEASE SHARE BY HITTING THANKS, LIKE, and if you feel so generous DONATE! (if you want to buy me a beer that is)
Works
It works. Got it installed with no problem.
Would post a link to the pic, but still blocked by the "new user" stuff.
If you post and thanks in all my threads on here youll get yourself further away from new member restrictions.
Sent from my GT-N8013 using Tapatalk HD
can you provide me the CWM for Huawei ascend y210d????
working great ..... thank you bro for helping usnow the time for custom rom i can't find a custom one to installi think gonna to learn cooking roms just to custom this fone lol:good:
nrzm said:
working great ..... thank you bro for helping usnow the time for custom rom i can't find a custom one to installi think gonna to learn cooking roms just to custom this fone lol:good:
Click to expand...
Click to collapse
We have a fairly stable cm7.2 not yet released and working on cm9. I'll let u know when cm7.2 is released!
Sent from my GT-N8013 using Tapatalk HD
How to install CWM on Fusion 2
Your post did not help me. When I tried installing CWM it say does not recognise program as internal and external command. I need help.
---------- Post added at 09:04 PM ---------- Previous post was at 08:52 PM ----------
I should also state that my phone is a U8665
dude when i connect my phone to the computer it does nothing
---------- Post added at 12:28 AM ---------- Previous post was at 12:18 AM ----------
i need help!!
tried this at least a half dozen times... Always fails and device is rooted. I can get instalador to erase and send, but when it goes to write the new recovery it fails with the following message (remote: flash write failure).
EDIT: forgot about the waiting for device part but still fails... >X(
EDIT 2: Never mind finally got it after like a bajillion times and a new user account on my computer
password
why is it asking for passwords
My N7 turned off abruptly (no messages) while I was watching a movie (wasn't hot or anything). After that, it won't turn on. It either turns off at the Google logo, or the bootanim. I tried going into recovery, but the tablet turns off. It won't always boot up or go into bootloader (the LED doesn't flash, holding the power button doesn't do anything). When it does boot into bootloader, fastboot works, but reboot commands just turn it off. I tried flashing the newest TWRP, but that didn't change anything.
Is there anything I can do that won't erase /data?
bootloader unlocked, using slimkat 6.6 weekly, flo 32GB.
When you boot into fastboot does a computer recognize the tablet? In that case you may be able to recover the tablet
sent from my nex7
---------- Post added at 10:31 AM ---------- Previous post was at 10:28 AM ----------
Also: do you have knowlage of fastboot commands? Have you tried flashing a custom recovery?
sent from my nex7
Yeah, fastboot works. As I said in the op, I tried flashing the newest twrp, and that changed nothing. Since my last post, the situation got worse - the tablet turns off while it's in bootloader mode, so I can't flash stock.
At this point I'm pretty sure it's a hardware fault, but I'm afraid they'll tell me my warranty is void, since I've got an unlocked bootloader.
Tapatalk'd
Hmm sounds like a hardware fault. Before giving up check out this thread: http://forum.xda-developers.com/showthread.php?t=2546558 this is for a 2012 model but it shows that a new recovery+kernel+bootloader+ROM can all be flashed at once to recover a device.
PS: have you tried the wugfresh toolkit?
sent from my nex7
Yeah, I tried it. Didn't work because either the bootloader would turn off before anything got done, or it wouldn't turn back on after a reboot-bootloader command.
I extracted the img files from the stock archive and flashed them through fastboot manually. It took a long time because I couldn't manage to turn it on after each shutdown. Then I relocked the bootloader.
Didn't help though. Still can't reliably boot up the bootloader (once every ~10 tries, once an hour?), no matter the whole thing. And the bootloader still crashes to off after a short while.
I think I'll tinker with it until Wednesday, and then I'll try to send it for repairs/exchange.
How about the wugfresh nexus toolkit? Did you try the unroot and flash system .img?
sent from my nex7
---------- Post added at 07:29 PM ---------- Previous post was at 06:52 PM ----------
Also: I'm pretty sure that a hard reset can fix random shutdowns and stuff like that so maybe you should try a hard reset through recovery if you're tablet will stay on long enough
sent from my nex7
Like I said a couple of times, it won't stay on long enough for the toolkit, and it won't boot up after the toolkit issues a reboot-bootloader command after the first step (flashing bootloader). I can't get into recovery, because it shuts down when I press power to select recover in the bootloader.
And it's not random reboots. It shuts down after 5 seconds in the bootloader. That has to be a hardware issue. I'm going to the retailer to exchange it tomorrow.
Tapatalk'd
Yep. Sounds pretty dead to me, you should just go exchange it.
sent from my nex7
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
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Queentus said:
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Click to expand...
Click to collapse
try this one here
if not, call harware support for a possible rma
reyscott said:
try this one here
if not, call harware support for a possible rma
Click to expand...
Click to collapse
Won't work cause I can't even get to the bootloader. Thx anyway.
call google support to initiate RMA.
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
Thanks for the reply.
My Pixel is already on it's way to RMA.
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Same thing happened to me last night. RMA is on its way, but this month old Pixel XL is dead.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
do you have an advanced guide to fix it? I have pixel past warranty that has the same problem
JimSmith94 said:
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Click to expand...
Click to collapse
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
fiverings said:
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
Click to expand...
Click to collapse
My post was over three months ago and as I said, I got a refurb replacement, which I have since sold and have a Pixel 2 XL. Guess I should have said that although my computer recognized it, adb didn't. That's why I was asking if there was any other way to retrieve the data. I ended up using a week old backup so it wasn't too bad.
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
Click to expand...
Click to collapse
I was able to get it to boot into twrp. Should be OK from here. Thank you.
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
I was able to get it to boot into twrp. Should be OK from here. Thank you.
Click to expand...
Click to collapse
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
I'm sorry I should have responded sooner. I don't remember much, but I had a feeling that it was still running because it was warm so I left it alone for a couple hours to see if it would die and then I could try to boot it again it's exactly what I did but what was funny was that it still had battery life when I turned it back on I hope you had some some luck.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
perfectswanson said:
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
Click to expand...
Click to collapse
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
nikinnikin said:
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
Click to expand...
Click to collapse
You gotta be kidding me. Last time I left the phone alone, and my hunch was that it would run out of power, and then you can atleast get into the bootloader. I fixed it before. I wish I could get a hold of software those guys use to repartition, or however they do it. We have Pixel 3 leaks, but no repair software. All I did was install TWRP, and it said no OS installed. It just kept booting up into TWRP. Then I switched slots to see if that would change it, but I think that might have been what screwed it up.
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
What version of TWRP did you use?
---------- Post added at 01:50 PM ---------- Previous post was at 01:37 PM ----------
I just got back into the bootloader. After a dozen times I just held down and power for like five seconds. Should I try recovery and try to remove Magisk, or should I just try to flash 9.0?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
What I did this time that was different, and I don't know if this is what helped or what, but this time I plugged in headphones and held power and vol down.
Putting the headphones in worked, or maybe it was just a fluke, but it worked on the first try. I got into Bootloader, "fastboot boot twrp.img", then I flashed the magisk uninstaller zip, the booted back to bootloader, and did flash-all.bat. It said it failed on the vendor partition, but everything still works.