Related
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Mine reboot when it overheats during charging. There are several overheating threads u should check out.
Sent from my Nexus One
Just be honest
houmi1 said:
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Click to expand...
Click to collapse
From what I hear, if your honest and tell google that you unlocked your bootloader they will still repair your device, I don't know about replacing it if it can't be repaired. But before you go that route try troubleshooting. Make sure you have the correct radio, not all roms come with the correct radio. Non-compatible kernals can become a issue to, if you flashed a custom kernal. I get the bootloop problem if I flash a rom without wiping, which I never do, except when the instructions say no wipe required, and then I get the bootloop issue. So try a full wipe, data, dalvik & cache, ext, and then reflash your rom.
I had random reboots up the wazoo. My phone was unlocked/rooted/running FRF93. I downgraded to other versions of Froyo and even went back to 2.1/CM and it was still rebooting.
Turns out that HTC actually puts it through a reasonable testing procedure to determine if it was in fact the user that damaged the phone. So even if it is unlocked/rooted and the phone passes the test, you will get your repair free of charge just like me. I'm currently waiting for them to ship my phone back.
Although I have heard horror stories from HTC, so I really think it depends on the moon cycle...
Like a poster above said, BE HONEST. Let them know the truth that it's rooted/unlocked but currently running a standard ROM. If they give you the standard "if it's rooted, you're going to have to pay", tell them that you're heard of their testing procedure to determine if it's the user's fault. Go to a supervisor if you have to.
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
houmi1 said:
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
Click to expand...
Click to collapse
Any updates? I have a similar issue
Yeah I basically think it's heat related and unrelated to the firmware, RAM, etc.... I had the phone at a very cool place and it works perfectly, and when I started using it, as it got hot, it started rebooting, and I noticed the back of the phone was very hot.
So I think nxt was right #2 in this thread.
Houman
The above observation would seem to make sense. My phone would reboot while trying to watch youtube videos sometimes, but ALWAYS within a few minutes of using it on the mains...
I have since had it sent back to HTC to have the phone repaired. I had rooted my phone just to get 2.2 however as it was a genuine hardware issue they replaced the main board and now not only does the phone not reboot anymore, the issues I had with no 3G (only Edge) have disappeared too. Happy
BANE
Hi
So I got my phone back from htc, they basically fixed it and even locked the bootloader so all is well
Just FYI
Houman
I'm hoping someone can help me. I installed CM KANG 7.1.5 on my Milestone a couple of months ago and for the most part, everything was working great (at least better than the stock 2.2 on it). But over the last week or so, I've been having a problem with wifi on my phone. Basically, wifi is not working any more or at least it's inconsistent now.
Previous to this week, I had no issues. I had a number of wifi networks set up, and everytime I went to the wifi hotspot, the phone would automatically switch from using data to wifi.
However now, it appears the phone doesn't detect wifi networks any more. I've tried multiple hotspots and still nothing. I've tried using Wifi Analyzer and doesn't see anything either. I've rebooted the phone multiple times, taken the battery out, reseated the SIM card and still nothing. I use 3G Watchdog and Juice Defender and have removed both and still nothing. The strange thing is it's sporadic. ie. wifi will work one day and then the next day in exactly the same spot, the phone get no wifi at all.
Has anyone else experienced this issue? How did you fix it? I've thought about wiping the phone and starting over again but I'm hoping to avoid that, if possible.
Thanks for your help in advance.
Doing a complete nandroid backup, wiping everything, and installing a new ROM takes me a total of about 15 minutes. If the problem I was having isn't fixed by that, I just restore the backup.
I should also point out that 7.1.5 is outdated and the current version is 7.2.0; quite a bit of work was done on WiFi issues in the past few months, and you're probably missing out on fixes for these exact issues.
It can be a pain to set up a new ROM, but worst case scenario is that it doesn't fix anything and you can just restore the backup and be right back to where you were an hour ago.
Please keep us updated here.
Sorry, I'm somewhat new to this (this Milestone is the first phone I've ever rooted, installed CyanogenMod, etc) so I'm probably going to ask some very noob questions here. My apologies if these are very simple or dumb questions.
I've been hesistant to rebuild/upgrade my phone to fix this problem for a couple of reasons including -
My wifi still comes and goes randomly. I worry that maybe it's a flaky hardware issue more than software so I don't want to spend all this time rebuilding it again to find out it's a loose connection or something like that instead.
I assume all my apps, data, settings, etc will be wiped out if I rebuild or update my CyanogenMod unless I use something like Titanium Backup to back them up? Or is there some better/faster way for doing it or maybe CyanogenMod and Nandroid have some better/faster solution that I don't know about? It took me, it seemed like days, to fully restore all that stuff last time so I want to make sure it's worth doing.
Is there an ETA on a "production" aka non-RC version of 7.20? If it's coming soon, I'd rather wait. I'd hate to upgrade to the RC version and then 2 weeks later have to do it all over again.
Thanks for your help.
About ugrading to 7.2:
- do full nandroid backup first
- clean both caches
- apply 7.2 zip
- clean both caches again
- rebot
I use that method when moving from one version of the ROM to another and no serious issues (one or twice I have to clean caches one more time after first restart). In worst case you have nandroid backup so you can quickly move back.
I have done full wipe (including partial sd and complete ext partitions cleanup) just few times e.g. moving from CM6 to CM7.
Generally I apply full wipe only when moving from one ROM to another, in beetwen versions of the same ROM I just clean caches twice.
Hi Guys,
I have this phone for many years, but suddenly the random reboots started approx 2-3 months ago, running originally KitKat 4.4.4 at this time. Before that I was rooted the phone and I supposed it could be something with that. However, flashing back & factory resets didn't help at all, clearing dalvik caches as well. What I tried up to now:
1. Upgraded/Downgraded the bootloader -- no change
2. Tried different recovery modes -- CWM & TWRP(the current one)
3. Different ROMs -- no change, the sudden restarts persist.
(4. Updated the radio -- the signal got quite better)
Three days ago I've upgraded to Lollipop 5.1.1 (the Cyanogenmod 12.1), the same story continued after a while (different applications installed).
There's one thing for sure: flashing the factories always results into a very stable phone at the beginning, installing some more applications leads to the same state -- random and frequent restarts.
I've checked the hardware -- the power button looks ok, it's definitely not the main cause b/c it reboots without touching! The CPU temp & free memory look quite good too.
Now, the current situation is as follows:
- flashed ROM (official one): 2016-03-03 Poland (T-mobile) 4.4.4 I9305XXUFOL2 I9305TPLFOL2 (seems like the most stable till now)
- installed ATK (Advanced Task Killer) -- configured to kill all applications aggressively when the screen goes off.
For me it looks like the ATK helps much, although I don't know the reason. Also, memory checked, I've executed all kind of possible tests up to the phone -- all appears as OK. Also, I don't know if it's related to the issue but I moved all possible apps installed to the SD card. The internal memory has been formatted via TWRP before the last ROM installation... Does anyone have any idea what could be the reason for the sudden restarts? It restarts even in Safe Mode, without any obvious reason and not touching the phone at all. The CPU load at the times of restart is quite low, the temperature as well. I doubt if the RAM is corrupted or maybe the NAND has some bad blocks. Are there any useful utils for tests that could be executed?
PS: I attach some log file, which I gathered once I was running the Cyanogenmod 12.1 (Lollipop). As I stated above the situation is the same when running 4.4.4 and 5.1.1. Sometimes after such a restart, it sticks in a boot-loop (if I boot manually via the GUI in recovery or download mode it will not).
Current versions:
---------------------
Android: 4.4.4
Baseband: I9305XXUFOA1
Kernel: 3.0.31-4282983/[email protected] #1
Build: KTU84P.I9305XXUFOL2
SELinux: Enforcing
Recovery: TWRP
I beg for your help on this! Cheers!
Same problem here...
Hi there
I'm having this same annoying issue with my Samsung GT-I9305. It suddenly restarts without doing absolutely nothing but looking at the screen or scrolling a text or just sending a sms/whatsapp/whatever.... I started trying to restart the phone (nah) turning it off and back on (nah) changing the battery for another one that I have here with me (nah)... After that, I extracted the SD Card and leave the phone only with internal storage (again, nothing happened but restarting randomly). I tried not installing apps such as FB, even Pebble App or just stopped sycronizing my phone with my Pebble Time via Bluetooth, but with the same and well known result: still restarting suddenly. I have noticed that when Google Play detects that there are few apps with a newer version asking to be updated, the phone restarts too! I tried deactivating this option in Google Play, just letting me to decide when and how to upgrade my apps, but It seems that it still detects the app upgrading needs and keep doing it the same way.
About a year ago, I found the same problem with my phone, but in that time it was related to the power button, it seems that it was pressed all the time and the device felt into a rebooting cycle. I check some blogs and I solved the problem cleaning the button with this electronic cleaning spray. I almost drowned my Samsung but I let it dry for a few hours. It worked fine, until now.
My cellphone is still in Android 4.3 (I9305ZHUCNB1) I don't know why I can't upgrade it to a newer version, even when I see that the 4.4 is available for this model. Right now, I'm thinking about change the cellphone and just forget the whole problem. But I'm just exploring again to see if I can find a last solution that tackles this annoying issue.
Did you manage to solve this problem??
Thanks in advance!
Unfortunately not, I had to buy a new phone. I guess the processor or other element suddenly broke, there's no other explanation to me. Also, as you see no any reasonable support in the forum.. Anyway, wish you a good luck with this.
Not so good here too...
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
fjpp81 said:
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
Click to expand...
Click to collapse
Sorry for bothering this thread also... I got success by replacing the display!
HI,
I'm writing this in a new post not to be confused with out dated information!
My wish is, someone smarter than me write it! but it just has not happened..
The main issue is:
Note 4 tmo
1. Freezing.
2. Restarting randomly.
3. MMC failures.
4. Kernel Panic.
5. Sluggish.
6. Goes to sleep and does not awake.
7. Bla, Bla.
Remember, this is in my opinion!
If you can use it say thanks if not don't flame, but feel free to set the record straight!
Thoughts...
To many phones have gone wacky on or about the same time as the MM update.
In my humble opinion its software not hardware or is it!
I think its faulty/borderline firmware that may run on some but due to maybe another underlying issue pushes the phone over the edge!
Since the clean-up I have had no other issues, see below!
Troubleshooting, Best practices
Troubleshooting best practices
*Start out with good tools*
1. Good USB Cable
2. Fully Charged Battery
3. Good software tools such as Odin, Kies, etc.
4. Known workable drivers (windows, Mac)
5. Always do a back-up of your stuff.
6. Have good working copies from reliable sources such as firmware, roms, TWRP, etc.
7. Make sure your hardware is Genuine, there is Note 4 knockoffs & Micro-sd card knockoffs, Battery Knockoffs swirling around the internet!
8. Remember, Garbage In Garbage out! if your system is conflicting you can't rely on your back-ups, dirty flashing, etc tear it down and rebuild including internal SD
9. Factory reset, wipe, format, (this must happen to start fresh.
10. If your googling for research please don't choose all but say search in the last month etc. conflicting information exists.
11. Please match your kernel with the rom & firmware ask the developer of the rom for advice.
BAD Information
in our search for answers, we may come across info that was good at one time but no longer! so be careful.
examples:
1. You can revert back to KK from MM.
(not sure that's true, although Odin will let you downgrade to the AOG1 firmware of the N4T2, I'm not sure its stable.
But it won't then let you reflash the ANK4.
2. Just because its on the internet don't mean its true.
3. Just because the Samsung guy says its the Motherboard, its still suspect.. (I'll tell you my car transmission story later)same theory
3a. He pulls his pants down and craps just like we do!
4. You can't make chicken salad out of chicken $h!t, just because it has chicken in the title..
Dude my note 4 is totally F'd phones just stop working when they are old. I've had this note 4 since a week after it came in 14. Been a great phone but I switched to the s7 edge because of this. S7 edge screen cracked so I'm using this one as a backup and MAN it sucks ! My issues are mainly with battery. I've tried a new battery and don't help, it dies at 30% it charges slow, drains fast. Also a lot of glitches my back button don't work on YT? camera can't focused on an object more than 3Ft away. Thus phone is a mess. Can't wait to fix my s7 edge. Just needs to come up with an extra $320 stupid Assurant won't fix my s7 edge. Taking off JUMP. Till the switch insurance companies soon they will
Sent from my SM-N910T using Tapatalk
nano303 said:
Dude my note 4 is totally F'd phones just stop working when they are old. I've had this note 4 since a week after it came in 14. Been a great phone but I switched to the s7 edge because of this. S7 edge screen cracked so I'm using this one as a backup and MAN it sucks ! My issues are mainly with battery. I've tried a new battery and don't help, it dies at 30% it charges slow, drains fast. Also a lot of glitches my back button don't work on YT? camera can't focused on an object more than 3Ft away. Thus phone is a mess. Can't wait to fix my s7 edge. Just needs to come up with an extra $320 stupid Assurant won't fix my s7 edge. Taking off JUMP. Till the switch insurance companies soon they will
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yep I'm with you brother! (still writing the thread though!)
SO far So Good Here's What I DID
1. Download all necessary firmwares.
2. changed to a smaller tried and true micro-sd card (just in case)
3. Charged my battery.
4. formatted my sd card with SD-formatter on the PC
5 loaded all files on the sd card with a usb-micro-sd reader/writer
6.Moved PC files all in one location on the HD such as C:/note4/kernels
or C:/note4/roms or C:/note4/firmware.. (I think you get the picture)
7. in TWRP I wiped,factory reset, formatted data on internal SD, everything except the external sd. (a couple of times)
8. with ODIN I did flash the T2"s firmware listed as :N910T2UVU2A0G1 just to downgrade from MM.
9. Then let it boot with minimal input, after shutting it down back to DL mode.
10 with odin install DOK2 firmware, it is more stable.
11 then flashed TWRP but unclick the auto-boot. (Thanks to Bigbiff & TWRP team)
12 Unplug after TWRP flashes and pull the battery. (2 or 3 Seconds)
13 boot in recovery using home, Power and volume UP.
14 now flash rom of choice I used N5 Express ver. 3.4D (Thanks rmarinella )
15 with Freeza's kernel 3.10.40 BeastMode Thanks Freeza)
16 customize with your personal settings then backup ( backup before you do to much tweaking though)
Special thanks to all folks that put so much time into this phone! if I left someone out, let me know!
Here's some photos!
I know you say Quadrant bench marks are bull?
well they will detect stuttering, lag etc.
So you guys had a huge performance hit today? I thought my ram was going or something. Long pauses in responsiveness, 10-15 second lock screen turn on from time to time, random jitters. Forced me to wipe everything and upgrade to MM from 5.0.1. Right around my last tmo payment for the phone too. Suspicious. The upgrade seems to have made things a little better (still some small issues) but now I'm paranoid. Probably my last samsung phone...shame (this is primarily due to the lack of battery and expandable memory though).
If anyone had a lot of success with a custom ROM please repot back.
EDIT: phone rebooted after posting this. Will have to tinker more.
gdewald said:
So you guys had a huge performance hit today? I thought my ram was going or something. Long pauses in responsiveness, 10-15 second lock screen turn on from time to time, random jitters. Forced me to wipe everything and upgrade to MM from 5.0.1. Right around my last tmo payment for the phone too. Suspicious. The upgrade seems to have made things a little better (still some small issues) but now I'm paranoid. Probably my last samsung phone...shame (this is primarily due to the lack of battery and expandable memory though).
If anyone had a lot of success with a custom ROM please repot back.
EDIT: phone rebooted after posting this. Will have to tinker more.
Click to expand...
Click to collapse
Good luck, thanks for posting!
I got my Note 4 back in late 2014. I picked the Note 4 over the Nexus 6 and I regretted it after the first Lollipop update.
I truly believe (imo) Samusng gave us a borked Lollipop update because at the time the S6 had came out the gate with Lollipop and the newer version of TouchWiz.
There was a rom that was made from a Sprint S6 edge which the creator tried to port over as best he could to the Note 4 and it was very fast and snappy, The only issue was the radio would stop working and would randomly reset every so often. Everything did work including the Theme store and the edge apps. What makes the Note 4 so weird acting (imo) is the older version of TouchWiz still lingering on the Note 4 and Note Edge.
It got worse when the MM update came out. I was using a stock rom, unrooted and it was terrible. I finally got a Nexus6 last year and the phone is still snappy and fats, if not faster on Nougat. Samsung knew that people would still keep their Note 4's over the Note 5 due to the lack of missing features like a removable battery, sd card slot, and IR blaster.
I dont think their is much you can do unless you run a custom rom.
Welp since I still have issues with my Note4 and am completely new and not very knowledgeable about it... I had the same issues with my stock phone;(it even bricked on me once) I snooped around and now I've settled with installing that app "WakeLock" and let it always run (Partial wake lock setting 4);
* I know its not fixing the problem but I'm a noob *
its been almost a week now and it phone doesn't freeze, reboot, lag(majorly);
Before I had to remove battery at least 5 times a day and pray it would turn back on;
bvzxa3 said:
I got my Note 4 back in late 2014. I picked the Note 4 over the Nexus 6 and I regretted it after the first Lollipop update.
I truly believe (imo) Samusng gave us a borked Lollipop update because at the time the S6 had came out the gate with Lollipop and the newer version of TouchWiz.
There was a rom that was made from a Sprint S6 edge which the creator tried to port over as best he could to the Note 4 and it was very fast and snappy, The only issue was the radio would stop working and would randomly reset every so often. Everything did work including the Theme store and the edge apps. What makes the Note 4 so weird acting (imo) is the older version of TouchWiz still lingering on the Note 4 and Note Edge.
It got worse when the MM update came out. I was using a stock rom, unrooted and it was terrible. I finally got a Nexus6 last year and the phone is still snappy and fats, if not faster on Nougat. Samsung knew that people would still keep their Note 4's over the Note 5 due to the lack of missing features like a removable battery, sd card slot, and IR blaster.
I dont think their is much you can do unless you run a custom rom.
Click to expand...
Click to collapse
I think your on to something!
Thanks for your post.
Xirazer said:
Welp since I still have issues with my Note4 and am completely new and not very knowledgeable about it... I had the same issues with my stock phone;(it even bricked on me once) I snooped around and now I've settled with installing that app "WakeLock" and let it always run (Partial wake lock setting 4);
* I know its not fixing the problem but I'm a noob *
its been almost a week now and it phone doesn't freeze, reboot, lag(majorly);
Before I had to remove battery at least 5 times a day and pray it would turn back on;
Click to expand...
Click to collapse
I hope an expert chimes in... but I think wake lock is doing what a good working kernel is suppose to do! correct me if I'm on the wrong track.
Most of my issues seem to be kernel related. There are times when the phone will act up just because I plugged it in or will loop when trying to shutdown. I think part of it was having a bad TWRP flash that screwed with subsequent actions. Secondly, my phone seems to run fine until I install any GAPPS. The camera is always having issues and I would get random wake lock and boot loops.
Right now, I flashed DU 10.6 and then ran a backup before flashing GAPPS. Then, using that as a base, I'm going to try and find a happy GAPPS and DU 10.6 combination. I may have to try a minimal GAPPS approach and install things as needed on /data
cal3thousand said:
Most of my issues seem to be kernel related. There are times when the phone will act up just because I plugged it in or will loop when trying to shutdown. I think part of it was having a bad TWRP flash that screwed with subsequent actions. Secondly, my phone seems to run fine until I install any GAPPS. The camera is always having issues and I would get random wake lock and boot loops.
Right now, I flashed DU 10.6 and then ran a backup before flashing GAPPS. Then, using that as a base, I'm going to try and find a happy GAPPS and DU 10.6 combination. I may have to try a minimal GAPPS approach and install things as needed on /data
Click to expand...
Click to collapse
Thanks,
Keep us updated on you progress!
Good luck.
sloanster said:
Thanks,
Keep us updated on you progress!
Good luck.
Click to expand...
Click to collapse
Thanks for the luck wishes. I think they might have helped
So, thinking more about my issues, I realized that it was not only kernel problems, but random issues depending on how I flashed and what I flashed. Today, I have what I think is a CLEAN and working install. Previously, I would have issues with Wifi starting up and Camera focusing and SuperSU installation.
Here's what I did to get my clean install:
Always backed up a copy each step of the way so I could have checkpoints to go back to and build upon.
First, I downloaded the newest version of ODIN: 3.12.3
Then, I flashed a new copy of TWRP recovery via ODIN: twrp-3.0.2-0-trltetmo.img.tar
SHUT DOWN PHONE (Do not reboot)
SIT 2 MINUTES
boot into recovery using VOL UP + HOME + PWR
ADVANCED WIPE: check everything BUT Internal Storage and MicroSD and swipe to wipe.
Install ROM (no other files!) and wait.
Back out of menus until TWRP home menu and choose reboot, then in the submenu, Shutdown
SIT 2 MINUTES
boot regularly
SIT 15 MINUTES This part is hard to do, but just go do some reading and come back.
Then, SHUTDOWN and TURN BACK ON.
You should still be on the Welcome screen upon boot.
Make sure you can connect to Wifi and your SIM is being read. If not, start over from the advanced wipe and make sure to wait when needed.
If that all works, skip the gmail and name prompts and get to the home screen.
Shutdown wait a minute and boot to recovery
run a backup and name it PRE-GAPPS or something (DO NOT USE ENCRYPTION, it has not restore properly from encryption in my experience)
Then, flash your GAPPS file and SHUTDOWN and wait a minute. I used PICO GAPPS (Open Gapps; ARM | pico | 6.0) so I could install what I wanted later from Play Store.
Boot up normally, skip any logins etc and make sure camera, wifi and phone work. If yes, shutdown and boot into RECOVERY, backup and name WORKINGGAPPS or something.
Boot into system and start the Google Account logins etc.
At this point, I ran another backup Called WITHGOOGLE
And finally, I booted back into the system and started loading my other applications and adding some of my tweaks, then running another backup. LOL
It was a time consuming and patience testing practice, but I'm happy now that my phone is working as expected. I'll report back if it stays stable or not. At least I have back ups to revert to.
cal3thousand said:
Thanks for the luck wishes. I think they might have helped
So, thinking more about my issues, I realized that it was not only kernel problems, but random issues depending on how I flashed and what I flashed. Today, I have what I think is a CLEAN and working install. Previously, I would have issues with Wifi starting up and Camera focusing and SuperSU installation.
Here's what I did to get my clean install:
Always backed up a copy each step of the way so I could have checkpoints to go back to and build upon.
First, I downloaded the newest version of ODIN: 3.12.3
Then, I flashed a new copy of TWRP recovery via ODIN: twrp-3.0.2-0-trltetmo.img.tar
SHUT DOWN PHONE (Do not reboot)
SIT 2 MINUTES
boot into recovery using VOL UP + HOME + PWR
ADVANCED WIPE: check everything BUT Internal Storage and MicroSD and swipe to wipe.
Install ROM (no other files!) and wait.
Back out of menus until TWRP home menu and choose reboot, then in the submenu, Shutdown
SIT 2 MINUTES
boot regularly
SIT 15 MINUTES This part is hard to do, but just go do some reading and come back.
Then, SHUTDOWN and TURN BACK ON.
You should still be on the Welcome screen upon boot.
Make sure you can connect to Wifi and your SIM is being read. If not, start over from the advanced wipe and make sure to wait when needed.
If that all works, skip the gmail and name prompts and get to the home screen.
Shutdown wait a minute and boot to recovery
run a backup and name it PRE-GAPPS or something (DO NOT USE ENCRYPTION, it has not restore properly from encryption in my experience)
Then, flash your GAPPS file and SHUTDOWN and wait a minute. I used PICO GAPPS (Open Gapps; ARM | pico | 6.0) so I could install what I wanted later from Play Store.
Boot up normally, skip any logins etc and make sure camera, wifi and phone work. If yes, shutdown and boot into RECOVERY, backup and name WORKINGGAPPS or something.
Boot into system and start the Google Account logins etc.
At this point, I ran another backup Called WITHGOOGLE
And finally, I booted back into the system and started loading my other applications and adding some of my tweaks, then running another backup. LOL
It was a time consuming and patience testing practice, but I'm happy now that my phone is working as expected. I'll report back if it stays stable or not. At least I have back ups to revert to.
Click to expand...
Click to collapse
Yeah, I believe I would have move my important stuff off the internal and wiped it!
You can't be sure conflicting stuff does not linger..
Take the poll
page 1
Hi all,
I am completely running out of things to try and do now.
After installing Android 7 on my Note 5 I had the strangest issue that i in general have never seen on a phone. The screen is simply black (which isnt that strange) and the phone is fully functional. Bare with me, after reseting it multiple times so it would finally come on the screen goes crazy and turns goes into so many colours (if it turns on that is). Its either that or jumps all around the phone, quite literally it glitches out completely. Its like one of those virus cut scenes you see in movies, it goes different colours, glitches out, jumps around and completely misformats.
From the beginning i knew this was not a broken screen.
So far i have tried.
1. Factory reseting the phone. That gave me about 5 minutes of normal use until i locked the phone and it wouldnt unlock again.
2. Factrory reseting multiple times... again to no avail, it would work for short periods of time and glitch out again.
3. Reflashing stock Android 7 in Odin. - No avail.
4. Flashing Dr.Kretans Rom... worked for 1 day which made me so happy and think that the problem was solved but then the same problem persisted.
5. Installing Arters Kernel.. (arter97-kernel-n920cig-22.0) Nothing... literally did that today and still NOTHING
6. Re partitioning. Quickest process and no avail.
In more detail, if the phone does sucessfully boot, and bare in mind sometimes it takes more than 2 hours to get ANYTHING on the screen (including recovery which doesnt boot up either until the initial apperance of something on the screen)
I tried taking the phone to a phone shop before doing anything myself and since in England this phone was never released theyre refusing to touch it. I tried calling samsung and they dont want to do anything either cause its not a UK variant.
Could someone please tell me anything else i can try. I feel like im totally running out of options here.
My phone details are as follow
Galaxy Note 5
SM-920I Singapore Singtel Variant
Running on 6.01 (i downgraded from Kretan)
And the kernel is the one previously mentioned v.22.0
I would appreciate anyone's help or suggestions so much at this point. All these problems started since the 7.0 update a few weeks back :/
Oh its also running TWRP recovery (arter97-recovery-n920cig-22.0-twrp_3.0.2-0.tar)