everything was ok till 22 december build...it started from 27 december build
earlier every lollipop rom worked fine on my n7100.
i dirty flashed 27 december build on 22 december build..it started rebooting randomly.
i wiped everything and flashed again it also showed same error and the rom was rebooting as soon as the screen turns off
after that i have tried every lollipop rom out there even every build of cyanogenmod 12 but it is showing same problem and rom in unusable. I was also using agni kernel on that rom and titanium backup. The phone reboots as soon as the screen turns off and the cyanogenmod logo appears. I have also tried wiping internal storage 3 times but no success.
I seriously want to use 5.0.2. Came from dn4 which worked awesome. using TWRP 2.8.4.0 Earlier i also used multirom twrp when everything was working fine.
Thanks in Advance
ritikbanga said:
everything was ok till 22 december build...it started from 27 december build
earlier every lollipop rom worked fine on my n7100.
i dirty flashed 27 december build on 22 december build..it started rebooting randomly.
i wiped everything and flashed again it also showed same error and the rom was rebooting as soon as the screen turns off
after that i have tried every lollipop rom out there even every build of cyanogenmod 12 but it is showing same problem and rom in unusable. I was also using agni kernel on that rom and titanium backup. The phone reboots as soon as the screen turns off and the cyanogenmod logo appears. I have also tried wiping internal storage 3 times but no success.
I seriously want to use 5.0.2. Came from dn4 which worked awesome. using TWRP 2.8.4.0 Earlier i also used multirom twrp when everything was working fine.
Thanks in Advance
Click to expand...
Click to collapse
This is not true for me.I have tried almost all the Lollipop ROMs since their first release.Now I am with the Resurrection Remix 5.3.2 dated 27.01.2015.I have not experienced any random reboots till this date.Most of the time while flashing new ROMs I was doing full wipe and Factory Reset.Once I installed Agni Kernel.After that when I shifted to another ROM I lost my IEMI. Flashing stock ROM couldn't restore it.Hence I went to Samsung Service Centre.They said that the Mother Board has to be replaced which which will cost Rs.7000.00 (apprxly 75..00 USD).So I went to a private technician and he restored the IMIE at a cost of merely Rs.250.00(apprxly 4.50 USD).Thereafter also I shifted to many Lollipop ROMs without any issues.But I never installed Agni since then.I am sticking with the kernels came with those ROMs.
pnsdhrn said:
This is not true for me.I have tried almost all the Lollipop ROMs since their first release.Now I am with the Resurrection Remix 5.3.2 dated 27.01.2015.I have not experienced any random reboots till this date.Most of the time while flashing new ROMs I was doing full wipe and Factory Reset.Once I installed Agni Kernel.After that when I shifted to another ROM I lost my IEMI. Flashing stock ROM couldn't restore it.Hence I went to Samsung Service Centre.They said that the Mother Board has to be replaced which which will cost Rs.7000.00 (apprxly 75..00 USD).So I went to a private technician and he restored the IMIE at a cost of merely Rs.250.00(apprxly 4.50 USD).Thereafter also I shifted to many Lollipop ROMs without any issues.But I never installed Agni since then.I am sticking with the kernels came with those ROMs.
Click to expand...
Click to collapse
but i am getting these issues
Related
The last few nightlies have caused bootlooping, and I have reverted to my last backup of 10-15. Yesterday I worked out that after installing the 10-21 nightly (and bootlooping) I could restore just the /boot partition from 10-15 and it booted normally. Today I installed the 10-22 nightly and it bootlooped again (and worked after restoring /boot). So the nightlies appear to be modifying /boot as well as /system, and not in a good way for my Note 8 N5110. I'm using TWRP 2.7.1.0.
Any ideas how to fix this?
Greg
bump
I am having the same issue. I had the 20141008 rom to go back to so not a huge deal.
More detail
I went back to my last backup and then flashed the nightlies until I found the change. 10-17 works well and 10-18 boot loops. The changelog shows half a dozen changes to the Exynos 4412 kernel on that day, so one of them borked the Note 8.0.
I have tried everything I can think of to get these to work. I went back to TWRP 2.6.3.0, unplugged the battery, wiped cache and various partitions, all to no avail. I can't say definitively that it isn't something on this end but it is looking increasingly unlikely.
My brother also has a Note 8 and he has not had these problems. But he is using Ryukiri's custom draco kernel, not the one included in the nightlies, so that seems to confirm the source of the problem is the kernel, and specifically the changes made in the 10-18 nightlies..
Originally I thought this might be a general Omnirom issue but clearly at this point it is Note 8.0 specific. So this thread should probably be relocated to the Note 8.0 forum...
Fixed and will be available shortly
Thanks to Ryukiri for fixing the kernel problem.:highfive:
The patch has been merged and should show up in the 11-4 nightly. Watching intently...
Greg
I can confirm now that 11-04 nightly is booting properly.
Thanks again Ryukiri.
Greg
Hello guys,
It's been a while since the last time I visited the SGS3 section, over a year ago I remember updating the bootloader in order to upgrade/flash to 4.4.4 which went very smooth and was a success. I gave the phone to a sibling who has been very happy with it for the last year and a half. Lately, the phone has been very unstable with the 4.4.4 KitKat ROM, WiFi doesn't turn on, Bluetooth is unstable, Unstable apps/Force closes. I tried a wipe/factory restore and re-flashed the ROM but the problems persisted.
I did a little research and liked what CyanogenMod is doing and since they are actively supporting the phone I decided to flash CM12.1 and the provided Open Google-Apps, CM12.1 flashed successfully but Open Google-apps refused to install, CWM displayed (Section 6) error which upon research it is common with CWM and the solution is to flash TWRP. I booted with CM12.1 in order to install TWRP Manager through the APK and flash TWRP but it force-closed when it searched for the device model. WiFi was working but Bluetooth was still unstable.
I would like to know what would be the best way to proceed in this case, I would like to upgrade the recovery to TWRP and flash CM12.1 or any other stable Lollipop ROM.
Thanks,
Oscar
absolute all credit to @audit13.
http://forum.xda-developers.com/showthread.php?t=3313734
perhaps this will help.
"err on the side of kindness"
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc, does anyone know what the problem could be?
Have you flashed the latest firmware? If not, I think this is why due to you being on a very old version (6.0.1) and as you are not flashing official OxygenOS you are not getting the newest firmware.
Download and flash the latest firmware here:
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Pick the right one for the ROM you are flashing (For Freedom OS installing firmware Open Beta 14 - Firmware + Modem under 7.1.1 should be good.)
Note: After you have flashed the firmware the next time you reboot the phone it will appear to not turn on for a few seconds, this is normal while it updates, don't worry
Let me know if you have any questions
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.
The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.
HI,
I had been using the phone for the past 1 year. It was working fine. But, for past couple of months after the recent updates, everything went haywire.
I downloaded the last Android 10 ROM from sammobile and flashed it, it did not help too.
I am at a loss , can anyone please suggest anything.
Do I really need to flash the stack ROM , is that the only option I have ?