Related
I tell you I unlock it first, then I had problems with some widgets and I learned some new updates.
Then, I made a backup with Sony_Ericsson_Backup_and_restore.
After searching, I root my phone with "GINGERBREAK" downloaded from the internet (GingerBreak-v1.20) and finally settled "Titanium Backup" to remove some applications from my operator, then install the CLOCKWORDMOD (do not know what for) and and finally I started to flash ...
After root, flashing with FlashTool_0.2.9.1.
I suggested steps for flashing and inserted this update: "LT15i_4.0.A.2.368_Generic Global", with "wiped ...", which is to delete everything and set it to zero ..
Normal work for me ... I sent version 2.3.2 to 2.3.3 (thinking I would send to 2.3.4). It was great ... Then I appeared a notice of samsung (on phone), to install version 2.3.4 (4.0.1.A.0.283 I think it was that number) and when it started to install warned me he was going to shut down, spent 6 or 7 minutes and not lit. I tried to turn it on and vibrated, then vibrate him again and try to turn rang again, but soon ...
Then I could not turn ...
Once this happened I was like crazy trying to fix the COMPANIOM, but nothing ...
I flash again, this time with this "LT15i_4.0.2.A.0.42_ (1247-1041). Ftf" but did not recognize the flashtool as the first time coming out of the mobile code when you open the program loads and displays the model number of the phone, it did not appear.
Finally, press flash and began. (To this already, before, try reinstalling the Global LT15i_4.0.A.2.368_Generic where my computer does not recognize, nor giving flash, just not recognized out in red letters)
When flashing with the latest LT15i_4.0.2.A.0.42_ (1247-1041). Ftf, the normal flashing until the end. But my phone just did not work. The light that was on the side of my phone was green ...
I sent a technician and he said he could not ....=/
I hope you can help and serve as a case to be resolved.
Thank you very much, good luck!
With bootloader unlocked by other methods different to setool one you will get bricked after try to install an OTA update
In order to get phone back to life just flash this with flashtool
http://www.mediafire.com/download.php?v4d3jdf136ymaxr
If you are interested in fix that annoying problem with ota update check this thread
http://forum.xda-developers.com/showthread.php?t=1126358
Greetings
ozfred said:
.... then install the CLOCKWORDMOD (do not know what for) ......
Click to expand...
Click to collapse
Lol dude, don't install things if you don't know what are those for
But i did it...u_U! So, now?
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
Hello
My phone suddenly faced a bootloop, i was on cyanogen 13. just looping the Lenovo logo. Not able to get into recocery.. But QFIL detecting phone, and i even flashed the kitkat version of stock.. The process shows success but still im stuck at bootloop, even tried various method.. Your valuable help appreciated here
any help ?
mjtirur said:
any help ?
Click to expand...
Click to collapse
I think it's some hardware problem. The phone when first came to market has one of the best specifications. Other players had significantly higher prices of their phones providing same hardware. So, I think that Lenovo compromised on the hardware components to provide the SD410 and 2gigs of RAM for this price. I many times had problems with proximity and light sensor. Also the battery sometimes awkwardly dies giving very bad backup and only when you decide to replace it, it automatically starts working fine, for some time atleast. Then same thing happens again.
So, I think its problem with some hardware component. Otherwise, flashing from QFIL successfully, would have unbricked the phone.
Im facing the exact same problem as of now...
Managed to boot into recovery somehow and flashed a ROM but then again it went back to bootloop while unlocking the lockscreen
i have solution.
First off all remove battery then insert it again , after this press vol. Up + vol. Down + power on button by doing this your device completely boot recovery which one is now installed with software.
You said previously that your device is on only showning logo , its mean you have 60℅ chance to get your device in working condition.
Bro if you flashed stock kikat firmware then without flashing any software again just simply flash kitkat twrp recovery through adb . After this flash any kitkat rom ( recommended cm 11 by ed300 ) , huree you get your device live.
OR
If you recently flashed stock lolipop then without flashing any software again just simply flash lolipop twrp recovery through adb . After this flash any lolipop based or marshmallow based or naughat based rom , after that any rom from these android version will work , hurreee you got your phone alive but remember dont again directly flash kitkat rom over any lollipop , marshmallow, naughat rom otherwise you will again got bootloop . But you can directly only flash stock kitkat over stock lolipop or stock lolipop over stock kitkat only . I hope you understand what to do :good:
If you have any problem you can simply tell me via my WhatsApp no. - +91 9205097520 (indian no.) Or simply reply me on xda or simply mail me - [email protected] . I have other tricky solution steps ,which were really used and tested by me. Bye friends.......... And Don't forget to tell me about your device problem .
sasukay said:
I think it's some hardware problem. The phone when first came to market has one of the best specifications. Other players had significantly higher prices of their phones providing same hardware. So, I think that Lenovo compromised on the hardware components to provide the SD410 and 2gigs of RAM for this price. I many times had problems with proximity and light sensor. Also the battery sometimes awkwardly dies giving very bad backup and only when you decide to replace it, it automatically starts working fine, for some time atleast. Then same thing happens again.
So, I think its problem with some hardware component. Otherwise, flashing from QFIL successfully, would have unbricked the phone.
Click to expand...
Click to collapse
Okey Bro
nk41319 said:
First off all remove battery then insert it again , after this press vol. Up + vol. Down + power on button by doing this your device completely boot recovery which one is now installed with software.
You said previously that your device is on only showning logo , its mean you have 60℅ chance to get your device in working condition.
Bro if you flashed stock kikat firmware then without flashing any software again just simply flash kitkat twrp recovery through adb . After this flash any kitkat rom ( recommended cm 11 by ed300 ) , huree you get your device live.
OR
If you recently flashed stock lolipop then without flashing any software again just simply flash lolipop twrp recovery through adb . After this flash any lolipop based or marshmallow based or naughat based rom , after that any rom from these android version will work , hurreee you got your phone alive but remember dont again directly flash kitkat rom over any lollipop , marshmallow, naughat rom otherwise you will again got bootloop . But you can directly only flash stock kitkat over stock lolipop or stock lolipop over stock kitkat only . I hope you understand what to do :good:
Click to expand...
Click to collapse
Thanks bro... i will try this and let you know !!!
AmythD said:
Im facing the exact same problem as of now...
Managed to boot into recovery somehow and flashed a ROM but then again it went back to bootloop while unlocking the lockscreen
Click to expand...
Click to collapse
yes man gonna try the above solution.. lets c
Hi.. I have recently rooted my Samsung galaxy note 4 SM-N910F and I am wanting to downgrade from marshmallow 6.0.1 to Lollipop 5.1.1. I really need a dummy guide as I don't know how to do it and help will bbe appreciated
Hey there. Downgrading to an older version of Android means you'll have to factory wipe, but other than that it's pretty straightforward. Seeing as you have already rooted your phone, I assume you know how to use Odin, but here's all the steps anyway:
1. Download Odin
2. Find a Lollipop firmware for your device from SamMobile
3. Back up important data, and factory reset. You can do this in settings or in recovery.
4. Turn off your device, then hold power + vol down + home to put it in download mode
5. Open Odin, and put the firmware file you downloaded in the AP slot
6. Plug your phone in. If it isn't recognized, you probably don't have all the drivers installed - the easiest way to get those is to install Kies or SmartSwitch from Samsung.
7. Click Flash, and wait until it's done. Do not unplug the cable under any circumstance!
You're done!
EDIT: Oh, and by the way: Welcome to the forums! Remember to title your threads according to their content. Generic titles such as "help please" don't really invite people to click on them.
Can i downgrade my note 4 n910g from 6.o.1 to 5.1.1 im now on dr.ketans m12 rom
But now my mobile is stuck on download mode
Plz guide me thanks
bathijavinod said:
Can i downgrade my note 4 n910g from 6.o.1 to 5.1.1 im now on dr.ketans m12 rom
But now my mobile is stuck on download mode
Plz guide me thanks
Click to expand...
Click to collapse
describe here everything you did until now, step by step
First i wiped all data then i installes latest TWRP after that i installed dr.ketans rom M12 then again i wiped all data and rebooted the mobile its works for 3days perfectly
But now automatically shutdowns or restarting
And one time suddenly stuck on download mode
I removed battery and installed after few minutes
And it works fine
Rebooting issue is still there
I notice that somthing written on upper left side of corner kernels in yellow words
Should i have to change my kernel?
Right now my kernel is Hvitamin .
Plz suggest me what to do?
Thanks for reply
bathijavinod said:
First i wiped all data then i installes latest TWRP after that i installed dr.ketans rom M12 then again i wiped all data and rebooted the mobile its works for 3days perfectly
But now automatically shutdowns or restarting
And one time suddenly stuck on download mode
I removed battery and installed after few minutes
And it works fine
Rebooting issue is still there
I notice that somthing written on upper left side of corner kernels in yellow words
Should i have to change my kernel?
Right now my kernel is Hvitamin .
Plz suggest me what to do?
Thanks for reply
Click to expand...
Click to collapse
Did you ask/search in the rom thread?
Maybe someone else had the same problem.
It could be a kernel issue, try other kernel.
I don't use a G but a C version, so I can't test to see.
Also consider the eMMC issue of the 910 SnapDragon, search about this.
Thanks for reply dear
Can i update or change kernel ?right now im on H-vitamin any other kernel can you suggest me is better then H-vitamin?thank for your support
My note 4, randomly crashed, running completely stock.
Began bootlooping and hasn't stopped.
Have downloaded firmwares from Samsung-Firmware . org, as SamMobile will literally not allow me to download anything for free??
No firmware has worked on the device, Have tried numerous PDA versions as I am unsure which the phone originally is.
The first firmware gave the error "dm-verity verification failed" in the recovery menu.
Have wiped cache and data.
Note: This is actually the second N910F which had corrupted itself and stopped working.
Help! :angel:
Do you want to recover some data from it?
If Not than you can try factory reset from Recovery menu.
Other than that it might be memory corrupted or your battery.
Try to change the battery.
a602820922 said:
Do you want to recover some data from it?
If Not than you can try factory reset from Recovery menu.
Other than that it might be memory corrupted or your battery.
Try to change the battery.
Click to expand...
Click to collapse
No data to recover, have tried factory reset from recovery menu, sure will try another battery.
a602820922 said:
Do you want to recover some data from it?
If Not than you can try factory reset from Recovery menu.
Other than that it might be memory corrupted or your battery.
Try to change the battery.
Click to expand...
Click to collapse
New battery: Allowed the phone to boot past the first "Samsung Note 4" screen to : "Samsung" logo, but the phone made a loud beep/screech.
If you want to reflash the Stock ROM search for a version on https://updato.com
I just reflashed mine (g910f) even twice as I had an Infini-Boot, too. After cleaning Dalvik/Cache and formatting data, taking out the battery, after some time it suddenly displayed that it's going to setup apps and it works since then ...
So maybe just be patient.
TheEnda619 said:
My note 4, randomly crashed, running completely stock.
Began bootlooping and hasn't stopped.
Have downloaded firmwares from Samsung-Firmware . org, as SamMobile will literally not allow me to download anything for free??
No firmware has worked on the device, Have tried numerous PDA versions as I am unsure which the phone originally is.
The first firmware gave the error "dm-verity verification failed" in the recovery menu.
Have wiped cache and data.
Note: This is actually the second N910F which had corrupted itself and stopped working.
Help! :angel:
Click to expand...
Click to collapse
to get the latest stock rom for your device, free and fast
look what you have to do:
download this (windows ) application and install it on your windows pc.
This is the aplication that will allow you to search and download the latest stock rom for your phone.
It connect to Samsung servers and in very little time you will have a new stock rom on your pc.
choose samfirm 3.06
extract it on a folder on your PC and run samfirm.exe
in the opening menu type
SM-N910F(or T/V/W etc your phones model)
REGION..... xxx (your region code)
these 2 you can find in a sticker under your battery if you open the phone and take off the battery
tick '' BINARY NATURE''
(If you dont tick BINARY...'' you will get the whole stock rom in one file xxxx.tar.md5 to flash it in the oding using the AP tab)
CHECK UPDATES>DOWNLOAD
THIS WAY YOU WILL GET THE LATEST STOCK ROM FOR YOUR PHONE/REGION
Binary nature means the rom split in 4 files
1. BL- bootloader
2.AP - rom
3. CP - modem
4. CSC - Customer support code(region/country)
This is what a stock rom is consist of
this kind of rom is also called REPAIR ROM, because you can use it to repair your phone.
If you look in odin you will find exactly these 4 entries.
So you can put each in the appropriate box and flash them all and so have a stock rom.
push start
Wait until rom flashes and phone reboots.
Hopefully it will solve your problem and everything will go as we all wish to.
BUT, from what you are describing, i am afraid for 2 things:
1. Your battery is almost dead, thats the good scenario .
With 20 $ you will solve it.
So new battery, new rom> problem solved, or
2. You are starting to have the emmc failure on your phone.
Thats a tough one.
Lets hope its not the case.
Just in case
https://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
good luck my friend