Related
Hi,
I've been do many flash last 24 hours on my Galaxy S4(Model SGH-I337M, Telus). Initialy, i've the factory stock rom, rooted. So, yesterday, i've decided to install Cyanogen mods nightly on my phone. Not the first time i've been used it on my phone. No problem before. So, this night, after a friend show me the release canditate release seem to be more stable, i've been try to put it on my phone. So, accidentaly wipe all the data on my phone. When i'm back home, i've put again the samsung original rom from my operator(4.2.2), found here, on the website, whit odin. All completed succefully, but i've noticed that the wifi won't turn on after the flash, and no sound from the speaker. So, i've put Cyanogen nigthlies again to test if it rom relative, but same issues here, no sound, but the wifi was working. The phone was very instable, so. Then, finaly, put the original rom again, without any rooting. Stuck on samsung logo, that i've finaly got fixed by clear the data and cache. But, no sound, and no wifi. Instable too.
Precision about phone: Unlocked whit the service mode(work), and enabled AWS whit a software and file(tutorial found here)
My question is: Anything else i can do to make my phone work fine again, and does it's possible to make the phone totaly stock? When i boot up, i've noticed that the phone, whit all rom i've try, said on samsung logo: Kernel is not sendroid enfonced, warranty status: kernel, so i can't go to return my phone on warranty whit that. How i can erase that line, and make my phone seem to be no modified?
Just to specify, it's not the first time i flash a phone. Do many flash, whit galaxy s2, s3 and s4, and sure, mine. Got try Cyanogen, stock, know how Odin work and all, try many rom, and before today, never has any problem to do turn back, but now, it's seem to be impossible.
Thank you very much for your help, very appreciated!
I would flash the stock firmware with odin again. After flashing do a factory reset in the stock recovery.
jd1639 said:
I would flash the stock firmware with odin again. After flashing do a factory reset in the stock recovery.
Click to expand...
Click to collapse
I've just try this. Flash the stock rom whit odin, and factory reset on original recovery after. Same, no wifi, no any sound.
Just see yesterday, when i'm flashing, i'm flashing on the bootloader in odin(whit the tar for the stock rom). Today, correct this by flash on the pda section, still not work. Found here on the forum the stock bootloader, rom, csc, and modem, but when i do this whit odin, odin said fail.
Thank very much, i think my phone is dead, and nothing to do to exchange it on warranty.
I think Kies has an emergency firmware recovery mode.... maybe that'll work.
Found a nice guide here: http://forum.xda-developers.com/showthread.php?t=2261153
saj222 said:
I think Kies has an emergency firmware recovery mode.... maybe that'll work.
Found a nice guide here: http://forum.xda-developers.com/showthread.php?t=2261153
Click to expand...
Click to collapse
Just try this. Kies is the worst software i've ever see. The software completely freeze random. When i go to the emergency menu, never, kies recognize my phone here. I've tried to plug my phone, no recognized. Tried without plug it, no recognized. When i plug it, kies said connection in progress, and can stay here 30 min.
I'm a idea of what is my problem. Before do install of cyanogen, i've been applied the samsung official 4.3 update, whit knox. And, according to what i read on many forum, knox is not ereasable, So, it's completely freeze my phone, and nothing to do.
Anyone have the factory telus bootloader and other factory stock items because i want to put it stock.
Thank.
Finally get problems fixed by take the TELUS stock 4.3 ROM and flash it whit Odin. After, can flash cyanogen nightlies again and the phone work well again.
Whit the stock ROM, didn't see any line on the Samsung boot logo that i've rooted. After root this appear again. Knox regardless of ROM installed said 0x1.
If anyone have a fix to put it again 0x0 very appreciated otherwise the phone work fine and thank you very much for your help.
dardares said:
Just try this. Kies is the worst software i've ever see. The software completely freeze random. When i go to the emergency menu, never, kies recognize my phone here. I've tried to plug my phone, no recognized. Tried without plug it, no recognized. When i plug it, kies said connection in progress, and can stay here 30 min.
I'm a idea of what is my problem. Before do install of cyanogen, i've been applied the samsung official 4.3 update, whit knox. And, according to what i read on many forum, knox is not ereasable, So, it's completely freeze my phone, and nothing to do.
Anyone have the factory telus bootloader and other factory stock items because i want to put it stock.
Thank.
Click to expand...
Click to collapse
I've seen worse software, it's no better or worse than iTunes.
Sent from my SGH-I337M using Tapatalk
dardares said:
Finally get problems fixed by take the TELUS stock 4.3 ROM and flash it whit Odin. After, can flash cyanogen nightlies again and the phone work well again.
Whit the stock ROM, didn't see any line on the Samsung boot logo that i've rooted. After root this appear again. Knox regardless of ROM installed said 0x1.
If anyone have a fix to put it again 0x0 very appreciated otherwise the phone work fine and thank you very much for your help.
Click to expand...
Click to collapse
can u plz give me link for the flash file u just flash
i have same problem here after i flash with 4.2.2 no sound and phone freez all time
i like to flash 4.3 so i can fix my phone
thanks
mps5566 said:
can u plz give me link for the flash file u just flash
i have same problem here after i flash with 4.2.2 no sound and phone freez all time
i like to flash 4.3 so i can fix my phone
thanks
Click to expand...
Click to collapse
This is the link i've found whit all the factory stock operator ROM. This is what rescue me.
http://forum.xda-developers.com/showthread.php?t=2269304
@Spacemonkie4207 never my itune was freeze, and i can do basic operation like transfer music or create playlist without any problem. My kies stay on connection in progress, and turn, turn, turn, but never connect. And when it connect, only one operation, and kies completely freeze, stop responding, need to close it, and open it again. Tried many cable, usb cable, reinstalling software, two other computer, but nothing to do.
I recovered back to stock from custom to 4.3 however if you do so, depending on carrier you could lose root and the ability to install custom recovery.
I would revert back to 4.2.2 (as it's knox free) go to samsungupdates (google it) and pull the 4.2.2 for your region and carrier. flash with odin 3.9
you'll lose root, but you can always perform again as long as not on 4.3 (with 4.3 u can still root if you remove all the knox stuff, u just lose warranty).
Az
Sup guys. I have a problem with my S4. I doubt anyone will be able to help me find a fix but its worth a try. I hope someone will help.
Anyway, I flashed my GT-i9500 (Galaxy S4) from 4.2.2 to 4.3. Now it doesnt boot, It just gets stuck at the 2nd boot screen. Its not even a bootloop. It just hangs there. The S4 sound that plays gets cut like halfway.
I tried flashing a lot of different ROMS, and it still does the same thing. When I rooted it, I noticed the boot welcome sound plays full, but it still hangs after that.
I used Philz Recovery and mounted all the folders etc, but efs says invalid. So that means the EFS folder is messed. I get that, but I cannot repair the EFS if I cant boot the phone, I need the Samsung MTP **** for Samsung Tool to work. I have an N7100 (Note 2) Where I repaired the EFS with Samsung Tool, I was able to boot the phone.
I looked ALL over the net including this forum and found nothing. Right now the phone is just worth nothing. This is my last option, to ask here myself. If it cant be fixed I just cut my losses and get another phone.
I also flashed a PIT file, CSC file, Modem file during the period I was trying to get this fixed. If anybody knows this problem, It'll be very helpful.
Thanks.
you could try upgrading to 4.4, i have all the files for omega v21
heres the link for all the stuff from my google drive.
https://drive.google.com/folderview?id=0B_trhAurRvdmb0RkNGpoTkVNU0k&usp=sharing
instal the bootloader and phone file via odin, bl = bootloader cp = goes into the phone part of odin
then fash the rom via philz recovery, worth a try !!
good luck
That wouldn't work, thats for the Snapdragon variant I think. The i9505. I have the i9500. I'll download the Omega ROM for i9500 and try it anyway.
Thanks.
Still doesnt work.
StickyBomb said:
Still doesnt work.
Click to expand...
Click to collapse
Did you tried complete of phone, than power and vol up, at the buzz lose vol up and at loge lose power button.
and then flash with odin bl. and modem
etc.
I've flashed with Odin & Recovery.
I flashed another bootloader, XXUEMK8 & Odexed Knox Free Stock ROM XXEUMK8 & it still does the same. I dont know whats wrong with it.
Another thing I forgot to mention is if I root it using Odin, the welcome sound plays full and it hangs, and if I reboot it, the welcome sound goes back to cutting off again.
This phone probably cant be fixed. I dont know wtf's wrong with this phone. This is WORSE than hard bricked.
oh & as I mentioned before, I have a Galaxy Note 2 & had an EFS problem with it. I fixed it, the difference was this Note 2 actually booted properly with any ROM installed. I used a Z3X Box & Samsung Tool to fix up the EFS. Maybe this problem is only with i9500 or with i9500 & newer models.
Eeeer don't mean to point out the obvious here but you did do a factory reset in stock recovery after flashing stock 4.3 in Odin? That's all you needed to do at the start.
When I went from 4.2 to 4.3 I couldn't get it to boot at all unless I performed factory reset after flash.
Sent from my GT-I9505 using XDA Premium HD app
I came from a rooted Samsung org. rom 4.3 to omega v21.1 Android 4.4.2
After this i tried slimkat, and had from first start the same issue, no booting.
Nothing works
only starting with power and vol. up as descried above, I could flash XXUFNA5 bootloader & modems.
After this twrp.
And at last I flashed S4 Google Edition - 4.4.2, a ROM for the Samsung Galaxy S 4
Thanks for the help people.
I gave up on trying. I tried everything even factory reset after flashing, different ROMS, different Android versions. 4.1.2, 4.2.2 & 4.3. Today I ended up selling the phone's LCD. Atleast I didnt everything. lol. Wouldn't be buying another Samsung EVER. I was thinking I need another box and stuff, like NSPRO but I dont have that.
Hello,
I've got (had) an SM-G900W8 running the XtreStoLite v2.0 LP BETA5 ROM on the XXU1BOA3 kernel. I installed TWRP 2.7 via Odin, and left the latest modem and bootloader updates I got through KIES3.
At which point I got the chance to sell the handset on Kijiji, provided I could get the stock ROM back on.
I downloaded the latest Odin (3.09) and the correct Firmware for my handset from sam mobile, and factory reset the device. I pulled the battery, let it sit, and tried to flash once I got it back up in download mode, and it wouldn't work.
This isn't too much of a surprise to me, because since I flashed TWRP, Odin hasn't ever worked for me. Regardless of how many times I've tried to flash the modem and/or BL that XtreStoLite asked me to use in their how to thread, it wouldn't work. I was willing to ignore it b/c the ROM worked with the modem and BL it was running.
My problem is that once I tried to reboot, the system hung at the BL animation. I went back into recovery, and tried to move my backups off my external storage (I had 2 back ups that were about 2 or 3 gigs each, too much for the local storage) to the local card and restore (b/c TWRP won't restore from the external card) and the back ups failed.
Now I've got the BL screen, but it won't advance to the animation, and it won't boot to TWRP either.
I tried to restore from KEIS, but it says my device isn't supported by KIES 3 (it is). I could really use a hand here. Every time I try something this gets worse. I'm no pro, but I've had no problem figuring this out on my old HTC handsets.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Note 4 Stuck in Boot Loop - Help
I have a Note 4 SM-N910F, never been rooted, stock rom upgraded to 5.1.1 back in October, working fine until yesterday when it got stuck in a Boot loop.
Not sure what caused it but before it got stuck I was messing around with Google Photos which was running a bit slow.
Also I put it on the Qi Charger just before the loop started. It has an aftermarket Fone charger stuck to the battery. I’ve had this and the Qi Charger for 6mths with no problems before now.
It gets to the Samsung page waits a couple of seconds then boots again.
Here’s what I’ve tried - unsuccessfully - to fix the boot loop:
1: recovery mode.
I can get the little recovery text to appear in the top left but after a few seconds it boots again.
2: volume down, home
This gets me to the screen with up/down for continue/cancel.
This is the _only_ screen I can get to stay up without rebooting. It sits there waiting for input.
- Cancel, causes restart, of course, but back into the bootloop
3: Mashing on power button. Banging it, wiggling it, blowing on it.
I read somewhere this could cause a boot loop, but I doubt it is my case because
a. I’ve never had problems with the power button before
b: When I take out the battery and put it back in, it does NOT turn on. If I do the same holding the power button, it powers into the boot loop. So if the button were jammed on I would expect it to never remain off with the battery in.
3: flashing stock rom
I’m not 100% sure what build I had before. I know it was stock 5.1.1 OTA, and I’m pretty sure it was unlocked (my wife bought the phone and i inserted my old sim, but she may have bought it from my carrier and can’t remember)
So anyway I tried all three versions of TPH (unlocked) 5.1.1 from Sammobile.
Installed Odin 3.10.7 and flashed them.
It reboots to recovery but immediately boot loops again.
I doubt its to do with the version of the rom anyway since the symptoms are identical after flashing. Only now the boot loop always shows the little ‘recovery booting...’ text in the top left.
Here’s what I have NOT tried but am thinking about:
A: Re-partition option in Odin
B: Nand Erase All option in Odin
C: Buying a new battery.
On A/B: as far as I can tell what I have done so far should have left the data intact. I’m prepared to wipe all my data if it fixes my phone (no lectures about backups please!) and I’m tempted to do one of these on the off chance that the problem is caused by data or the “disk" problems.
But I don’t want to brick it. Can someone recommend how likely these are to help
And what they actually do?
(Please refrain from responses I see elsewhere like “this will brick your phone if you don’t know what you’re doing”. I don’t know what I’m doing, thats why I’m asking - just the facts please)
On C: the battery seems ok in that the power is solid even after not being plugged in for a long time, but since it was on the Qi Charger with that aftermarket thing stuck to it when it happened, I’m suspicious. Can any one say if this is a likely cause?
If so, it might be worth waiting till I get a new batter before doing A or B (can I wait days for Amazon!?)
[UPDATE] Got a new (genuine) battery at a local electronics store. No dice. Same problem, so it's not the battery. Shall I go ahead and re-partition.
[UPDATE] Got a PIT file from another forum, and flashed again with re-partition checked and PIT loaded. same results.
Is Nand-rease worth trying?
The phone is still under warranty so maybe I can return it.
But in that case I want to erase what's on it first.
thanks for any help
rhubarb
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
You can flash TWRP through ODIN while on COJ5 bootloader. It's locked but you still can flash recoveries and kernel and 5.1.1 ROMS
I am very interested in this thread. I have the EXACT same problem as you have after installing SimplRom, which was a ROM prior to COJ5. It could indeed be that our bootloaders are locked now?
I am using the N910F and just like you, installing any ROM/Custom Recovery/Bootloader/Kernel doesn't help. Perhaps installing a COJ5 ROM might help. I will give that a try, but I've recently used Kies to install the latest official firmware, but it didn't fix the issue.
I will report back here and we'll work on this together to make our phones work again!
Osama lakdawala said:
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Click to expand...
Click to collapse
Thanks but:
1: I have no custom rom. I have never had a custom rom on this device. I want to take it to Samsung, but want to clear the memory first. How can I do that?
2: I _am_ a software engineer_
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
roverrhubarb said:
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Click to expand...
Click to collapse
I have the exact same as you. I did install a custom recovery (multiple) and still get the bootloop. From my tries yesterday, I indeed also suspect it may be a hardware issue. Perhaps to do with the battery/charging port. When I have my device unplugged and try to start in recovery/normalboot, it does not have a bootloop but simply turns off (and then doesn't respond until I pull the battery out). I think a NAND erase wouldn't do anything as I've personally tried that already.
Have you prior (upto a week) before you got the issues had your phone in a moist environment (bathroom while showering for example). I got my problems a week after I accidentally left my phone in the bathroom and installed custom ROM (which was done earlier and had no issues).
I've read online that it may have caused oxidation on the inside and may need some cleaning/drying with alcohol.
I still hold hope that we just have a software issue as download mode is working fine (apart from the Power off not working unless we pull out the battery).
Anybody have any experience with oxidation on their phone? Perhaps have had a similar bootloop due to hardware failure?
roverrhubarb said:
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
Click to expand...
Click to collapse
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
dork997 said:
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
Click to expand...
Click to collapse
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
Since you can get into download mode I'd flash firmware through ODIN again after verifying it's correct.
I'm seeing off the sammobile site for the 910F not all are the COJ5 locked bootloader.
Since you did update in Oct you may be on the COJ3. I'd try one of those and see if it works.
If it doesn't work and stops on the sboot.bin file then you have the COJ5
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
i am sorry i don't know any way to remove personal data other than doing it via recovery. There is an option of "nand erase" in odin it is used while flashing firmware and it wipes everything on the phone but i have never used it (and also don't know whether it can help you or not) ... Senior members kindly help us with this.
Any update to your situation?
very interested as I am in the same situation as you are. Download mode works, recovery+normal boot not. No matter what ROMs/recoveries I install
Same issue I think
I am also in the same situation, although I can enter the recovery mode - home power and volume up - I have tried the wipe cache and then factory wipe to no avail - I have also entered download mode and flashed the stock recovery and even though Odin says pass, it is still in a boot loop. Also when I go to the download screen it has a line saying knox warranty void 0x1(4) does this mean I have voided the warranty even though I only used Odin to flash stock recovery?
Did anyone found a solution
Did anyone ever found a solution to this problem I'm having the exact same issue on a note 4 smn910a
I have a slightly different issue with my Note 4 SM-N910G, wherein am not able to start the phone at all, it is completely dead, if i put the cell phone on charge then also there is no LED on the top but if i connect the device to the PC it does make the connected sound on the PC but Odin is still not able to recognize the device neither kies. I tried draining the power by removing the battery, connected the device to PC without battery and then inserting it but the same problem. Please suggest me any resolution for this dead body am carrying from past few weeks.
hi Op,
did you find any solution for this issue?
Hello all. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
Hey guys,
I could use your expertise and help.
After updating my stock Note 4 Att variant from 5.1.1. to 6.0.1, I came back to my phone powered off. After turning it back on it freezes at the Att logo screen. Trying to boot into safe mode was a no go so I tried booting into recovery. Everything looked go for a second, I was greeted with an installing updates animation but that quickly was shut down and I got the "dm-verity verification failed..." error.
I tried wiping the cache and doing a factory reset. Talking with att technical support was no help at all. They basically told me if wiping the cache and factory reset didn't work I would have to get the phone replaced and pay a $150 deductible. I'm not paying them another dime when their update bricked my phone
So I'm here heart in hand hoping you guys could help me out. I did root my note 2 back in the day but forgot most of what it entails and was pretty bummed when I found out there was no root for the note 4. So I'm not a total noob but bear with me.
I did try Kies 3 but my phone wont connect. I tried off, on and in recovery still nothing.
Searching online it seems like most of the solutions require root access which this phone doesn't have. It also looks like it needs the stock firmware but most of the links I found here and elsewhere are dead, and sammobile doesn't have them either.
So what should I do? Am I out of options? Should I junk it cause Att sucks? Any sort of direction would be a big help! :highfive:
Mal-0 said:
Hey guys,
I could use your expertise and help.
After updating my stock Note 4 Att variant from 5.1.1. to 6.0.1, I came back to my phone powered off. After turning it back on it freezes at the Att logo screen. Trying to boot into safe mode was a no go so I tried booting into recovery. Everything looked go for a second, I was greeted with an installing updates animation but that quickly was shut down and I got the "dm-verity verification failed..." error.
I tried wiping the cache and doing a factory reset. Talking with att technical support was no help at all. They basically told me if wiping the cache and factory reset didn't work I would have to get the phone replaced and pay a $150 deductible. I'm not paying them another dime when their update bricked my phone
So I'm here heart in hand hoping you guys could help me out. I did root my note 2 back in the day but forgot most of what it entails and was pretty bummed when I found out there was no root for the note 4. So I'm not a total noob but bear with me.
I did try Kies 3 but my phone wont connect. I tried off, on and in recovery still nothing.
Searching online it seems like most of the solutions require root access which this phone doesn't have. It also looks like it needs the stock firmware but most of the links I found here and elsewhere are dead, and sammobile doesn't have them either.
So what should I do? Am I out of options? Should I junk it cause Att sucks? Any sort of direction would be a big help! :highfive:
Click to expand...
Click to collapse
Make sure samsung kies or samsung usb drivers are installed on your pc.
Download stock marshmallow firmware and flash through odin .this method does not require root.
After flashing dont let the phone boot just go to recovery and wipe cache+wipe data factory reset then reboot.
Wait 10 to 15 minutes.
Stock rom link.
https://www.androidfilehost.com/?fid=24651430732238073
Extract file and choose AP tab in odin.
Upload firmware file then connct device via usb cable to pc.
Hit start in odin.
You're the man! Not only did you save my phone, you stuck it to Att's money grubbing hands in one fell swoop. People will write songs about you, you'll go down in the history books as the man, the myth, the legend! People will swoon in your presence!
In all seriousness though you're awesome! Thank you!
One last question, will I be able to use the ota updates from here? Not that I would be too comfortable using them after this debacle, just wondering if they should work.
Mal-0 said:
You're the man! Not only did you save my phone, you stuck it to Att's money grubbing hands in one fell swoop. People will write songs about you, you'll go down in the history books as the man, the myth, the legend! People will swoon in your presence!
In all seriousness though you're awesome! Thank you!
One last question, will I be able to use the ota updates from here? Not that I would be too comfortable using them after this debacle, just wondering if they should work.
Click to expand...
Click to collapse
Thanks for the compliment. you just made me feel like i am a Hercules :victory:
If you want my advice dont ever take ota updates.
Just go to www.sammobiles.com/firmwares and grab latest rom for your model and flash in odin as you did.
Latest rom comes with the same security patch update the 1 comes in ota.
I personally do this way all the time.
Hope that helps and have a good day.