Hello everyone here:
I have bought a Cinglar 8525 about 3 month ago. Because enthusiasm of flashing rom, I start to flash rom one week after the purchase.
I flashed the hard spl v7,and flashed new OS rom image.
During the flashing, nothing special happened.
After two months usage, one time a software stopped responding, I thought it might be network failure or something like that and simply reset the device,then the nightmare began.
The device boot into bootloader automaticlly without the pressing of OK and Power button.I tried to reset the device by push the reset pin but it does not work, the device always boot into bootloader, after a few step of tring, it turns out the device maybe dead and I pull off the battery to make the device totally shut off, then install the battery again, and leave the device black screen.
After some time, I reset the device again , it boot into the OS this time. After some configuration that need reset , I reset the device ,but again ,it boot into bootloader.
So my device is very unstable now, even "fragile". Boot, maybe into OS, maybe into bootloader.
Can someone explain this? Or help me solve it?
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
You're running wm6.1, aren't you? Try wm 6 as its more stable or if you wanna stick with 6.1 try PDAViets roms (19701 or 19900). They're english though....
Please note the "unstable" I mentioned is not something like halt frequently,application auto close up,etc.It's the bootloader stuff.
But I thought the problem might be irrevelant to the OS version, the "crash" occur first time when I use a ROM of wm6.0 and "crash" second time when I use a ROM of wm6.1
do some reading on wm6.1, it causes stuff like what you are describing....
After deep search in my brain, the "crash" might be occured during two version of ROM and both with wm6.1 .
Can you provide some link describing this problem of wm6.1 ? I just wondering if it is my device hardware failure or not.Or due to my some improper operation during ROM flashing process. Thank you.
Use the search function. There are a heap of threads... Some people recommend flashing a stock rom THEN flashing the wm6.1 of choice. This DOES seem to fix the problem.. Cheers...
yinx said:
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
Click to expand...
Click to collapse
Please note this, I have done it before, I 'll do some search work.
Is there some evidence or something that the 6.1 rom of 19701 kernel has solved this problem ? I really like the thread function in SMS message in 6.1 so I want to stick in wm6.1 .
I have honestly only had problems with th 19919/19202 versions of wm 6.1. Tried 19900 with no problem and REALLY liked the speed. 19213 is SLIGHTLY faster and again no problems. Try ne of these if you MUST have wm6.1. The stability seems to get better and better as the chefs progress up the versions. Cheers...
Untill now I can't get my phone out of bootloader, I've flashed many ROMs including manufacture shipped ROM, but the phone still remain in one screen.Wondering if it can work out. Frustrated....
Start from 9:00 this morning I kept flashing my phone with different version of ROM, try to get out the bootloader,but still not working.
After a reset of frustrating "not working", I put down the phone,and do some other job,when I came back,I have transfered another ROM to the microSD and ready to flash the ROM.Before flash I thought "may I reset the phone again? may be the bootloader will go away", then I reset the phone as normal, after a while , the splash screen appear! I enter the OS, thinking the bootloader problem has go away. But when I complete some setting and reset the phone again, the phone finally fall in bootloader again.
So what ......
check for bad blocks using MTTY.... On upgrading section.
Cheers...
This I also have tried out. But I see no bad block on it, and I even do a forcibly fix to the NAND and with no avail.
I have sent the phone to a service center, it is said they might going to change a chip on the phone.
Wish my phone good luck.
Related
Hey,
Right, so in my great wisdom I managed to drop my TyTN on its face on the kitchen floor one day and since then it just doesn't do GSM.
On boot, it says "No GSM" below the boot logo, and anything to do with GSM (opening the phone app) causes the device to run slow for a little while then return back to normal without launching the phone app or throwing any error message. Its stuck in permanent "flight mode" as it were.
Sending the phone back to the provider, they turned around and said "On inspection it was found that 3rd party software was loaded on the unit and damaged the unit. Unit is returned without repairs done to it."
I was using one of the ROMS from the forums here which worked fine for a few weeks up till the drop. (I do know which one but I'd prefer not to give anyone a bad name where its not called for, so prefer not to mention it directly).
I will say that it was a fairly new release in june.
Also currently have on boot.
IPL-1.04
SPL-1.40.Olipro
Have since tried re-installing version roms which have made no difference at all.
So:
1: is it possible that the updated OS and flashing the radio etc could have cause the problem described?
2: How do I return the phone to its original radio version and a generic (officially supported) WM5?
3: Is there anything I can do from my side to fix the problem?
Many thanks
-RobH
Have you tried flashing the original ROM that it came with... Then you can probably take it back to another warranty shop or to HTC for repair... You can also upgrade to Olipro 2.10, you can search for the files, I'm just to lazy to look for it now... If you can't find let me know, and I'll look for it...
Once you upgrade to Oli 2.10, it may make a difference.. Have you tried flashing the radio...? It could very well be a hardware problem that occurred during that sudden stop on the floor...
I'm not to helpful, sorry...
Rob,
Obviously the fall messed up your TyTN, and HTC now refuses to work on it (read save money) because you are running a non-standard firmware. Well, screw that!
Have a look here to start the downgrading process.
Then, go to Leaf's site and download the AKU3 firmware from the Members section.
Flash it to your TyTN.
Then take it back to a different repair centre (not too sure about your options in Grahamstown) and tell them you dropped it, and now it is not working anymore.
Right so trying to get the original (well an club-imate approved) rom installed so that I can try the repair center again...
Based on this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
Image is HERMIMG_CDL_1.31.305.2_SHIP.nbh
(Extracted frin JASJAM_wwe_1.31.305.2_1.31.305.104_1.21.31.10_ship.exe)
I get the following:
<Gray screen with blue txt>
HERMIMG.nbh -
IPL - OK
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
EXTROM - OK
GSM -
OS -
Update in Progress...
</End screen>
And thats where it sits.
Even when trying the recommended usb/HardSPL methods, its gets to about 14% and hangs. I presume due to the GSM module being damaged.
I've also tried .nbh's that only have the GSM stuff, and using the microSD method, it gets about 5% along the progress bar and then halts.
EDIT: I've managed to flash it with an original rom excluding the GSM stuff. Will see what happens at the repair center...
-Rob
Excellent, hope you get it sorted!
Hi Mates
I was using a Doopod 838 and last week i lost GSM on my phone so i tried to flash the phone and phone stuck on 20%. after the phone wont starts and goes to boot mode, and i am not able to flash the phone.
please some one help me to unlock the phone
thank you
nasmi
What SPL you got?
If its Hard SPL ver.7 then it may be recoverable - pleasew note the "No GSM" error is pretty much a permanent brick if a couple of things don't work.
1). Try to flash a stock rom (carrier rom) on and see if it gets through that way.
2). Try to find the native radio rom... Most people update this but generally its better off left alone as it is carrier specific - some radio roms cause bad connection issues and/or drain the battery WAY too fast...
If you can't do either of these 2 things you're looking at a brick, Mind you if you haven't flashed Hard SPL you're not gonna be a happy camper either.. LOTS of frustration and hair pulling...
Good Luck...
I just recently acquired a HTC Touch Dual and really like it but am having a few issues with it. First, I get tskschedule, repllog, and clocknot notification errors. I've noticed a few threads regarding this issue but haven't yet found a solution so any suggestions would be most appreciated. The second problem is that my battery indicator doesn't seem to be working properly, it stays at 90% and doesn't change regardless of how long I use it for. This caused the phone to die on me in the middle of a conversation. So if anyone has an idea on how to fix either of these two issues, that'd be great.
Hard-Reset or flash another ROM (for example Original HTC Shipped 6.1 or one of the custom ROMs which where offered here in your language).
I bought the device used and unlocked off of eBay, will hard-resetting it keep it unlocked? Also, I'm very much a noob to phones and don't have any clue about flashing roms, what are they exactly and how do I do it? Thanks for the quick reply.
Hard-reset = Original state of the installed ROM
For flashing there are lots of tutorials here (I don't know which is your native language, so I can't post links to some ROMs - I have nearly tested all of them ;-)). Best you try flashing first original HTC ROM. Very easy (you said it's already unlocked), just connect the phone to pc via USB and start the flashingtool. After flashing hard-reset to be sure that all settings and files were restored to original state. That's all.
Don't forget to backup contacts, emails and so on before hard-resetting/flashing! Files on storage-card will be ignored, you don't need to backup them!
im from the us, so my native language is english. do you have any suggestions or links for the better flashing tools? after flashing to my original rom, my phone will stay unlocked right? because it doesn't it'll create more problems for me then i am having right now. thanks again
My native lang is German, so don't worry about my English ;-)
Unlocking is easy, just use hardspl and uspl. I have unlocked my phone only once a time and never had problems after or while flashing (done 15 times or more!). Once I killed my phone with a bad Rom (endless boot-sequence), but you can go into bootloader by pressing "Power-Button + Camera-Button + Reset", so you're always able to flash another Rom and/or could unlock the phone again. Nevertheless I can give no guarantee.
First you could try to download from HTC website. You need the serial-no. which can be found after removing the battery. If you have a look at niki upgrading/flashing forum you'll find also links to the original ROMs.
You can also try the latest WWE/english ROMs offered in this forum at the first 1-2 pages. I tried Gullum's TF3D and Lilly's ROM, both are great and have Manilla included (if you don't like it, the old HTC Home plugin is included in HTC Rom), but I prefer german ROMs. The Niki Project Rom didn't work for me (bugs in Outlook and Office Mobile).
All Roms include the flashing tool, it's really easy to use.
thanks buddy, i'll give it a shot and let you know how it goes
do i have to use a sspl before a hardspl? i have a neon and havent yet found a sspl for it yet. how dangerous is it to use a hardspl? im very new at this so thats why i have so many questions. thanks again
For me everything worked without problems. So I can't say how "dangerous" it is. Most users don't have any problems. To be sure get latest ROM from HTC or your provider, so if any problems occur, you're able to flash the original ROM back via bootloader.
As far as I know you only need to hardspl, but I did sspl first and then hardspl.
I think we need to clear up a couple of things and kind of slow down before you brick your phone
Generally, there are 3 types of locking for these phones.
First, there is SIM locking that everyone is familiar with and locks your phone for use on only one network.
Secondly, we have CID locking - which locks the software\firmware on your phone to that supplied by a particular carrier (for example, if your phone is CID locked to AT&T, you can only flash a ROM from AT&T and not HTC or a custom ROM).
Lastly, and least to be concerned about, is Application locking. I've not heard of any of the touch duals being app locked so we can safely ignore this.
I'm guessing that you meant your phone is sim unlocked in which case, I'm 99.9% sure that none of the ROMs that you can flash will change that.
If yours still has the carrier ROM on it, it is most likely still CID locked so you need to get that off first.
Once that's done, you need to HARD SPL installed (the SPL is the bootloader bit, SSPL is just a "software" version of it that can run but doesn't install anything) If you put HARD SPL on, then it is almost impossible to brick and ruin your phone - but until that is on, don't try flashing custom ROMs or radios etc. as you're asking for trouble.
Also, until you have HARD SPL on, be careful about flashing anything - make sure you don't run apps while it's going and shutdown anything that could interfere. Take basic precautions and you should be fine.
But TBH, if you're new to these phones anyway, and the ROM is right for your carrier, I'd leave it as standard - I personally always find something wrong with the cooked ROMs - missing T9 dictionaries \ SMS not working \ MMS not working \ some other detail that was missed, and I always end up going back to either my stock ROM (T-Mob UK WM6) or the HTC Update (WM6.1) but I don't notice the difference if I'm honest.
People say that whatever ROM they have on is the fastest they've ever tried but in my experience (and I'm on my fifth or sixth generation of WM phone) the difference is marginal at best and certainly not worth the trade off of broken features and multiple reboots.
So, my advice is, by all means, have a mess with other ROMs but be careful, get HARD SPL and make sure you have a ROM to go back to.
Oh, and try a hard reset (or Clear Storage from control panel) after syncing everything up to try and fix your current problems
Cheers,
Smiffy.
i was thinking about trying a hard reset prior to flashing a rom. i cant download a rom from htc and am unable to find one from att (my carrier) so as of now, i dont have a rom to fall back on. i bought the phone used and unlocked, so will a hard reset keep it that way (basically, what will a hard reset do exactly)? i am referring to a sim-unlocked state. the centennial wireless splash screen still shows up so im guessing it is still cid locked? do i need to unlock the cid before hard-resetting it? thanks for the help
The hard reset basically wipes and user-related info and returns it to a factory-fresh state - if one ever starts playing up, this is what should be done before you flash a new ROM, and yes, it will still be SIM-unlocked afterwards. It will alos go through the setup routine again as if you just took it out of the box
There are other places to get the HTC rom from - it's actually quite a good one too as it will set up all the data\MMS settings for your carrier too.
If you're not worried about any warranty, then it's good as a fallback though search on here and see what results other people have with AT&T.
CID unlocking is fairly easy if I remember - been a while since I did it and I have a different model than you. Just make sure anything you use is listed as OK for a neon
HTH,
Smiffy.
so i did a hard reset, and there hasn't been a change in the battery issues. so maybe the battery is faulty? would flashing a different rom help or should i just get a new one? thanks again
If the ROM is at fault, then flashing a better ROM would help, yes. If the battery the faulty, then even a ROM that is much more energy efficient would help little, only delaying the inevitable.
how would i know if the the problem is from the rom or the battery? other than trying a new battery that is
aight, so i got the hardspl for the neon. will that cid unlock my phone cause i cant find a cid unlocker for the neon 300. what would happen if i didn't cid unlock my phone before flashing a new rom?
Nothing would happen. Either it refuses to flash on beforehand, or it'd stop at about 1% from the start not touching your existing rom.
Hardspl is indeed the way to cid unlock your phone, as far as I know.
Please Help!
new problem here, my new battery just arrived a couple of days ago. i inserted it in my phone then let it charge before turning it on. my previous problem was that with old battery, the amber light would start blinking but not remain steady and tell me that my battery was very low then eventually turn off. the new battery's amber light was solid and i left it plugged in for 10ish hours because the light never turned green. i finally turned it on, but eventually the same problem arose. i hard-spled it then flashed a new rom which helped for a little while. the light stayed steady and the battery status rose up until 100%, but the light stayed amber. then if there was any shift in pressure on the chord, the light would start blinking and the battery would immediately read 5%. now the new battery isn't any different from the old one. does anyone have a suggestion? it would be greatly appreciated.
Anybody? Help? At the very least would anyone have suggestions of good repair sites? Thanks in advance
Hi all...I recently bought the HTC HD2 and ever since day one I've been having problems...The place I bought it from gave me a network locked phone (to Virgin Media UK) by mistake first and I had to send it back to them to get it unlocked for me (I live in the Middle East).
One day later I got the answering call problem mentioned many times in these forums...Next day, after installing a few apps, I found out that my phone takes a looong time to boot. The initial logo comes up fine with those version numbers or something at the bottom left...After that the virgin media animations loads up and then its stuck...few minutes later I get a message saying the phone couldn't boot up and I have to reset it by pressing volume up key or any other key to cancel...I just left it as it is without pressing any keys and few minutes later it shows the windows logo and then everything starts up normally. This is the same thing that happens everytime I reboot now.
1. Is there something that's causing the device to get stuck between the virgin media animation and the windows logo? I would prefer to get this fixed without resetting the device.
2. However, if I had to reset the device will I be stuck with a network locked device again?
Here is my software versions if it helps in anyway:
Manila: 2.5.19211619.0
ROM : 1.66.351.1 (76641) WWE
Radio: 2.07.51.22_2
I had this problem when i flashed the evo ROM, but i think that was because i tried to flash without HSPL, anyway all i did was flash it with another ROM and it worked fine, the best i have found and am currently using is EnergyROM Ultra.
What i would suggest to you is to either try flashing it with a custom ROM *WILL VOID WARRANTY*, to do that there are plenty of tutorials on here but basically just put HSPL on your phone then flash new ROM and radio ROm too if you like or you can send it back and see if they will fix it for you which they should because it seems like you havent done anything to void the warranty.
Let me know how if this helps and what you decide to do.
Psychoticus said:
I had this problem when i flashed the evo ROM, but i think that was because i tried to flash without HSPL, anyway all i did was flash it with another ROM and it worked fine, the best i have found and am currently using is EnergyROM Ultra.
What i would suggest to you is to either try flashing it with a custom ROM *WILL VOID WARRANTY*, to do that there are plenty of tutorials on here but basically just put HSPL on your phone then flash new ROM and radio ROm too if you like or you can send it back and see if they will fix it for you which they should because it seems like you havent done anything to void the warranty.
Let me know how if this helps and what you decide to do.
Click to expand...
Click to collapse
Thanks for the reply.
I got tired of waiting ages for the phone to bootup and decided to take a risk and reset it. Luckily it wasn't network locked after the reset.
I believe the app that caused this to happen was swype. Even though swype worked perfectly, it was after installing it and restarting that made my bootup take forever. Uninstalling it didn't help too. After reset, I no longer face any of the problems I faced earlier..It hasn't got stuck when answering a call (yet...) and I've installed everything I installed earlier except for swype.
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