Yesterday I couldn't hold it any longer and unlocked my bootloader. Then, I rooted, flashed Xposed and run some root apps.
Every now and then, my Z4T freezes and fully reboots (Sony Xperia logo). In between, the screen turns blank and the LED flashes red 4 times. Does this have any special meaning on Xperia devices? Overheating? Or just a generic crash?
/edit: I have the feeling it is a System UI crash in my case, which then causes a total system reboot. I think so because when I try to do a Soft Reboot, which is a System UI reinitialization (or a zygote reinit?), it will also fully reboot. Tried that with the Xposed Installer and (Material) Power Menu.
/edit2: It's probably not a System UI crash, but if it is, it's definitely Xposed related. Also, soft rebooting is broken on the Z4 Tablet, it'll result in a crash and a full reboot. Right now, there is a scenario in which Xposed causes either random reboots or reboots right after booting into Android after the 'optimizing apps' stage (after wiping Cacvhe/Dalvik after flashing Xposed). Uninstalling Xposed fixes these issues. Research is ongoing, if you have any experiences yourself, please share your findings.
Hi,
I don't have the answer to this unfortunately, but I have had exactly the same issue with the blinking red light and it happened after I installed Xposed too, a few funny things have happened since I rooted and flashed Xposed....
I also get the red light if I use soft reboot but its fine with a proper full reboot. I would be interested too if anyone knows the answer to this.
D_STROY said:
Hi,
I don't have the answer to this unfortunately, but I have had exactly the same issue with the blinking red light and it happened after I installed Xposed too, a few funny things have happened since I rooted and flashed Xposed....
Click to expand...
Click to collapse
Is this with just Xposed and no active modules or apps that use root? Have you applied the Camera crash fix mentioned in the Xperia z4 tablet[root] and xposed thread?
I also get the red light if I use soft reboot but its fine with a proper full reboot. I would be interested too if anyone knows the answer to this.
Click to expand...
Click to collapse
Same here. So it looks like soft rebooting is definitely broken on the Z4T, so I think it could be the ROM or kernel. What are you running? I'm on latest stock ROM (CDA 1295-4711, Germany, Customized DE, 28.0.A.8.260 / R6A) and kernel is AndroPlus v10. Xposed is v79, SDK21, ARM64 (xposed-v79-sdk21-arm64.zip).
Right now my suspicion is on the app GMD Auto Hide Soft Keys root that casues a System UI crash...
Hey!
Had same issue, started about 3 weeks after unlocking, rooting and xposed out of nowhere ... reflashed Stock, rooted again and problem solved!
No more reboots even i set up my system ecxactly like before ...
Don´t know what was really causing the issue but reflashing helped me
Cheers
Mr. Schnabel said:
Hey!
Had same issue, started about 3 weeks after unlocking, rooting and xposed out of nowhere ... reflashed Stock, rooted again and problem solved!
No more reboots even i set up my system ecxactly like before ...
Don´t know what was really causing the issue but reflashing helped me
Cheers
Click to expand...
Click to collapse
Thanks for the feedback. This seems like a common fix so I'll try that (after I have completed my Titanium backups). I should use Flashtool, right?
jelbo said:
Yesterday I couldn't hold it any longer and unlocked my bootloader.
Click to expand...
Click to collapse
Now why did you have to go and do that jelbo that just means less people to try the root method when marshmellow is released!
Oh well...
jelbo said:
Thanks for the feedback. This seems like a common fix so I'll try that (after I have completed my Titanium backups). I should use Flashtool, right?
Click to expand...
Click to collapse
Yes, restored via Flashtool did the trick!
Downloaded the FW directly there and flashed it then rooted again with AndroPlus Kernel ....
Reboots startet after updating from V7 to V8 if i remember correctly ... when rooting then again i needet to start with V5 and updated then to V10 ... every higher Version than V5 gave me an error in ADB ....
Mr. Schnabel said:
Yes, restored via Flashtool did the trick!
Downloaded the FW directly there and flashed it then rooted again with AndroPlus Kernel ....
Reboots startet after updating from V7 to V8 if i remember correctly ... when rooting then again i needet to start with V5 and updated then to V10 ... every higher Version than V5 gave me an error in ADB ....
Click to expand...
Click to collapse
That could have worked back then maybe, but the .260 firmware apparently needs v10. I just flashed v5 and my tablet didn't boot anymore. That got fixed though, phew.
I re-flashed .260 with Flashtool, reflashed the kernel, SuperSU and Xposed. I somehow had my apps still there, so I hope that's OK for this fix.
Let's see if it's stable now...
scoobydu said:
Now why did you have to go and do that jelbo that just means less people to try the root method when marshmellow is released!
Oh well...
Click to expand...
Click to collapse
Haha, yeah... the software keys were making me mad. I could hide them with GMD Full Screen Immersive Mode, but when immersed, you can't type
/edit2: Oh noo.... first thing that happened when Android finished booting: the crash I described.
Sorry wasn't really clear i only flashed V5 to get into TWRP and then flashed V10 on latest FW. English is not my first Language but everything ok from what i read now?
Mr. Schnabel said:
Sorry wasn't really clear i only flashed V5 to get into TWRP and then flashed V10 on latest FW. English is not my first Language but everything ok from what i read now?
Click to expand...
Click to collapse
I was just a bit too hasty, no worries. English isn't my first language either.
Everything ok so far now, yeah. I re-flashed with wiping everything and this time just rooted, no Xposed. So far, so good.
jelbo said:
Is this with just Xposed and no active modules or apps that use root? Have you applied the Camera crash fix mentioned in the Xperia z4 tablet[root] and xposed thread?
Same here. So it looks like soft rebooting is definitely broken on the Z4T, so I think it could be the ROM or kernel. What are you running? I'm on latest stock ROM (.260) and kernel is AndroPlus v10. Xposed is v79, SDK21, ARM64.
Right now my suspicion is on the app GMD Auto Hide Soft Keys root that casues a System UI crash...
Click to expand...
Click to collapse
Hi Jelbo
Sorry I haven't replied sooner, haven't been on XDA for a few days! I wasn't aware of the camera fix, i'll check that out, thankyou. Aside from the camera not working, Audio settings and MusicFX have gone right up the wall, I had to freeze them because of all the FC messages popping up.....was driving me crazy in the end!
Yes I am also running the same ROM, Kernel and Xposed version that you have, and I also think that something with Xposed and the soft rebooting causes a System UI crash too, I don't know why I didn't mention it in my first reply to you as that was one of my suspicions, a soft reboot is a an unclean shutdown (I think?...) and the Z4 doesn't seem to like it!
I had some problems with Xposed modules too, I haven't got the GMD one installed but Gravitybox was the first one I installed straight away, I was really missing it without having root and aswell as numerous other modules I have installed I had the newest version of xStana running and everytime I went into the Recent apps either via softkey or BKB50 , I was getting a full system UI crash so I disabled gravitybox as I have navbar tweaks enabled....rebooted and still same issue, disabled xStana and all was fine again. So to my relief it wasn't Gravitybox and to fix the problem I installed the oldest version of Xstana and it has been working fine.
Also.....do you have or want viper4android FX installed? I just thought I'd ask because I cannot get it to work either Apk or ZiP install. I flashed the ZiP after no success with Apk and I was convinced I had bricked my beloved tablet after that, I couldn't get it to boot then it turned to bootloop and after nearly 2 days of trying alI I could think of I managed to rescue it by removing the ZiP via TWRP......I dont know if its SONY or Lollipop that causes problems but I have had things that won't play nicely it seems.....
EDIT: Sorry I just realised you asked if I had a problem with Xposed itself or wether it was with modules/apps that were active that were causing problems, I'm afraid I don't have the answer as I have had active modules as soon as I rooted and flashed Xposed.
My guess is that it is Xposed framework that is causing issues, I don't know if you have this too....but the system logs on my device have wall after wall of error code displayed in red and they nearly all mention Xposed, honestly I have never seen such a vast list that repeats over and again of errors, it made me think about uninstalling Xposed but I just can't live without it!!!
Mr. Schnabel said:
Hey!
Had same issue, started about 3 weeks after unlocking, rooting and xposed out of nowhere ... reflashed Stock, rooted again and problem solved!
No more reboots even i set up my system ecxactly like before ...
Don´t know what was really causing the issue but reflashing helped me
Cheers
Click to expand...
Click to collapse
But are you running Xposed again or not?
D_STROY said:
Hi Jelbo
Yes I am also running the same ROM, Kernel and Xposed version that you have, and I also think that something with Xposed and the soft rebooting causes a System UI crash too, I don't know why I didn't mention it in my first reply to you as that was one of my suspicions, a soft reboot is a an unclean shutdown (I think?...) and the Z4 doesn't seem to like it!
Click to expand...
Click to collapse
I don't think it's an 'unclean shutdown', as it reboots. I think a SystemUI crash has more or less the same effect as a soft (or hot) reboot. These should immediately show the boot animation, but on the Z4T they cause a full (or cold) reboot, beginning at the splash screens, showing the Sony and Android logo's.
Also.....do you have or want viper4android FX installed? I just thought I'd ask because I cannot get it to work either Apk or ZiP install. I flashed the ZiP after no success with Apk and I was convinced I had bricked my beloved tablet after that, I couldn't get it to boot then it turned to bootloop and after nearly 2 days of trying alI I could think of I managed to rescue it by removing the ZiP via TWRP......I dont know if its SONY or Lollipop that causes problems but I have had things that won't play nicely it seems.....
Click to expand...
Click to collapse
No, I don't use or intend to use that.
EDIT: Sorry I just realised you asked if I had a problem with Xposed itself or wether it was with modules/apps that were active that were causing problems, I'm afraid I don't have the answer as I have had active modules as soon as I rooted and flashed Xposed.
My guess is that it is Xposed framework that is causing issues, I don't know if you have this too....but the system logs on my device have wall after wall of error code displayed in red and they nearly all mention Xposed, honestly I have never seen such a vast list that repeats over and again of errors, it made me think about uninstalling Xposed but I just can't live without it!!!
Click to expand...
Click to collapse
I haven't installed Xposed yet on my fresh install. It's been running great so far with all kinds of root apps and tweaks. When I had the reboot problems I also had it with no Xposed modules active.
I'm very hesistant now to install Xposed, because of stories that the uninstall.zip didn't fix problems and that's the only rollback option since TWRP restore is broken.
jelbo said:
But are you running Xposed again or not?
Click to expand...
Click to collapse
Yes, like said running same setup as before the re-boots occurred. Root/Xposed/Same modules/ same apps, etc.
System was running w/o problems for about 3 weeks and out of nowhere came those re-boots. Didn´t update any app/module/etc. in this time only thing was the BK50 but i had it for about 10 days before it started acting weird so don´t know what was really causing the problems ....
Sometimes after seconds, sometimes after minutes, sometimes after hours ... out of nowhere black screen/Red light and reboot ...
Mr. Schnabel said:
Yes, like said running same setup as before the re-boots occurred. Root/Xposed/Same modules/ same apps, etc.
System was running w/o problems for about 3 weeks and out of nowhere came those re-boots. Didn´t update any app/module/etc. in this time only thing was the BK50 but i had it for about 10 days before it started acting weird so don´t know what was really causing the problems ....
Sometimes after seconds, sometimes after minutes, sometimes after hours ... out of nowhere black screen/Red light and reboot ...
Click to expand...
Click to collapse
I just flashed xposed-v79-sdk21-arm64.zip, after I was running great for a few days, rooted. Guess what? After the boot and when all the apps were 'optimized': black screen, red LED and a reboot. So, this issue is definitely caused by Xposed.. What I still don't understand is why it's working for @Mr. Schnabel. Guess something is different and the cause of my issue.
I just flashed xposed-uninstaller-20150831-arm64.zip, hopefully things will be stable again.
Anyone else running Xposed, but without issues?
/edit: seems like we're not alone in this. I'm currently searching older Xposed framework .zip's, these are somehow hard to find as the old versions are replaced with the new in the Xposed thread :S I want to try xposed-v78-sdk21-arm64.zip.
/edit2: Just tried it with xposed-v78-sdk21-arm64.zip (found on a flaky Chinese Baidu mirror) and this also resulted in a crash, very quickly after booting. I'll have to delve into how to get some logging on this so people can look into this.
/edit3: @dl12345 once compiled an unofficial v74 build that worked great on a Z3+, but a Sony ROM update killed compatibility. At least on the Z3+, according to @DHGE, who ran the unofficial v74 on his Z4 Tablet. I just read now last week he was running v78 on his Z4 Tablet, so I guess he is also running it without the rebooting issue on the latest .260 firmware...
@jelbo
typing this on my tablet:
all fine here with xposed v78, now on v79 - no random reboots
only Sony camera app is crashing, deodexing according to AndroPlus did not help. That could be a tablet issue.
DHGE said:
@jelbo
typing this on my tablet:
all fine here with xposed v78, now on v79 - no random reboots
only Sony camera app is crashing, deodexing according to AndroPlus did not help. That could be a tablet issue.
Click to expand...
Click to collapse
All right. Just to be clear, this is with:
firmware 28.0.A.8.260 (mine is CDA 1295-4711, Germany, Customized DE, R6A)
AndroPlus Kernel v10
AndroPlus' TWRP 2.8.7.0
xposed-v79-sdk21-arm64.zip
No other, special things like disabling SELinux?
I really wonder what causes the difference here. I completely re-flashed the stock firmware a few days ago, including the kernel, recovery and Xposed. First thing that happened was the crash. So it couldn't have been any other 3rd party apps or Android settings.
I then redid everything, but did not install Xposed and things run fine. As soon as I flash Xposed (have tried v78 and v79) I get the crash. I do wipe cache and Dalvik cache after I have flashed Xposed. When I uninstall Xposed, the problem is gone.
I did not do the deodex trick for the camera app this time, but that would not bother me anyway, I don't use the camera.
Do you have any idea? Life without Xposed is hard.
Here are some logs, one from a normal boot without Xposed, two with Xposed v79 flashed; an initial boot and a second boot, both of where the device crashed and rebooted.
I also filed a report on rovo89's Xposed GitHub.
From similar Sony Xposed issues I have the feeling that some of my odex files are corrupted (which ship on several Sony ROMs) and that people who are running Xposed on a Z4T just fine are running a slightly different build than me (e.g. a non German one), in which these files are OK.
jelbo said:
All right. Just to be clear, this is with:
firmware 28.0.A.8.260 (mine is CDA 1295-4711, Germany, Customized DE, R6A)
AndroPlus Kernel v10
AndroPlus' TWRP 2.8.7.0
xposed-v79-sdk21-arm64.zip
No other, special things like disabling SELinux?
Do you have any idea? Life without Xposed is hard.
Click to expand...
Click to collapse
I do not know the exact numbers of the german ROM but since I got it via XperiFirm we should have the same version.
SELinux is enforcing.
I have deactivated lots of bloatware like VideoEditor, Google apps, myxperia...
I have disabled all autostarts of apps via Xprivacy (or Titanium Backup?) that I deemed unnecessary/nosy.
DHGE said:
I do not know the exact numbers of the german ROM but since I got it via XperiFirm we should have the same version.
SELinux is enforcing.
I have deactivated lots of bloatware like VideoEditor, Google apps, myxperia...
I have disabled all autostarts of apps via Xprivacy (or Titanium Backup?) that I deemed unnecessary/nosy.
Click to expand...
Click to collapse
Thanks. More or less the same here. I disabled or froze a lot of system apps using Titanium Backup and My Android Tools Pro, based on this Xperia LP 5.x debloat script. I did miss a few, because they were not listed and I don't know what they do, so maybe one of those that is still running is the culprit here. Rather difficult to compare between you and me.
Here's the Xperifirm list as of now, by the way. Maybe I'll try the US variant.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jelbo said:
Thanks. More or less the same here. I disabled or froze a lot of system apps using Titanium Backup and My Android Tools Pro, based on this Xperia LP 5.x debloat script. I did miss a few, because they were not listed and I don't know what they do, so maybe one of those that is still running is the culprit here. Rather difficult to compare between you and me.
Here's the Xperifirm list as of now, by the way. Maybe I'll try the US variant.
Click to expand...
Click to collapse
Hi,
I just can confirm that soft reboot doesn't work. (Without Xposed installed)
Sony Xperia Z4 SGP771
Androplus Kernel V10
Twrp 2.8.7.0
SuperSu 2.46
28.0.A.8.260/R10A Customized FR
I tried xposed-v79-sdk21-arm64.zip (three modules loaded: greenify,3c toolbox pro,Ownorientation) two weeks ago and my only problem (I think) was the Sony camera app stop working, so reflash stock rom, androplus,twrp,SuperSu and restore UserData via twrp did the job.
I try to install xposed and the deodexed trick for the sony camera app next weekend if i'm not busy.
Related
phones been fine for 440 hours (uptime since last time this happened) - since i lost the virtual keys last time and had to use sonys software to reinstall everything.
now after a reboot this happened again. disabled all xposed mods and the menus returned but now with orbot and folder mount running i had endless reboots. only after uninstalling the other 2 apps did this stop.
anyone else had anything like this?
wish i had recovery - stupid win8 and locked bootloaders
sony update service with full wipe.
did that last time. 2 weeks later happened again. stopped when i made changes mentioned in OP
Looks like you've been using an incompatible Xposed module or possibly other mod(s). Install them one by one again and see what triggers the crash (if you feel like re-flashing your ROM again)
Btw, it's fully possible to unlock your bootloader using Win8. It's a little wonky, but it's possible (unless your bootloader is unlockable). Or you know, you can install Recovery for locked bootloaders, but you can't flash custom ROMs, but you can make NAND backups.
A little off topic: I installed uTorrent yesterday since i had to download a torrent, and after i was done with it and uninstalled it, my ZU crashed and rebooted. Once it booted up again it crashed again, and again and again. Luckily i had a NAND backup on my SD card, so that problem solved itself, but lesson learned; no uTorrent anymore.
"Fun" fact: This also happened with uTorrent on my Galaxy Note.
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
tommo123 said:
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
Click to expand...
Click to collapse
Recovery is not a problem once you're rooted. Go to this thread, download and run the file, press "Oui oui, mademoiselle" or something like that and voila, you got Recovery. Easy peasy. It'll take you five minutes. Just remember to make a NAND backup once it's up and running. It's a life saver, as you already know.
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
tommo123 said:
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
Click to expand...
Click to collapse
Yup! Good going mate! I see you made it without any issues
Hey all,
I tried searching for this issue, but couldn't find anything--apologies if it's been answered already. I just got my first smartphone and rooted it yesterday, so I'm new to this stuff (but in general am good w/ tech). It's a Moto X non-dev verizon, and running 4.4.
Xposed Framework (installed 2.4.1) won't stay up to date after a hard reboot (app_process is a red dash) and thus my modules don't work at bootup. There actually was an issue when I first installed Xposed: after installing and then updating and rebooting, it wouldn't say it was up to date until I did a soft reboot. Now after a hard reboot, I have to reupdate xposed and then soft reboot for modules to work. Apparently there are at least a few others with the same issue. Is this a known bug?
Any ideas? I've tried reinstalling Xposed, no go. SuperSU seems to work fine with my other apps too. Any help would be appreciated!
Thanks!
P.S. Gravitybox is hella crazy what the wizardry?
I am having the exact same problem. When I click reboot or soft boot I get a blank dialog box and then click ok but nothing ever happens and when I reboot manually from the power menu it gives me the red dashes like you said. It worked fine on my nexus 5 a while back but I'm trying it now on my galaxy tab 2 and getting this issue
ricesteamer said:
Hey all,
I tried searching for this issue, but couldn't find anything--apologies if it's been answered already. I just got my first smartphone and rooted it yesterday, so I'm new to this stuff (but in general am good w/ tech). It's a Moto X non-dev verizon, and running 4.4.
Xposed Framework (installed 2.4.1) won't stay up to date after a hard reboot (app_process is a red dash) and thus my modules don't work at bootup. There actually was an issue when I first installed Xposed: after installing and then updating and rebooting, it wouldn't say it was up to date until I did a soft reboot. Now after a hard reboot, I have to reupdate xposed and then soft reboot for modules to work. Apparently there are at least a few others with the same issue. Is this a known bug?
Any ideas? I've tried reinstalling Xposed, no go. SuperSU seems to work fine with my other apps too. Any help would be appreciated!
Thanks!
P.S. Gravitybox is hella crazy what the wizardry?
Click to expand...
Click to collapse
The newest version of Xposed (2.5) solved this, but not directly:
Without TWRP or CWM or anything, I tried to install/update the framework via recovery (flash zip automatically) -- this was a new option in the update. It didn't exactly work, but then I tried install/update normally (writing to /system) and it finally worked. No idea why, but I'm happy. I googlefu'd the crap out of this too, sigh.
As the topic title states..
Is is worth flashing and installing Xposed Framework on our loved Z4 Tablet(s) - or does it result in a soft brick / infinity bootloop?
Did read here somewhere that it was some trouble with getting Xposed to work properly on Z4 Tablet (?) so I rather ask you guys before taking the shot and biting the bullet..
Any suggestions / experiences om this matter, guys?
@all
Yes it's worth, actually random reboots almost went away with the latest androplus kernel. But permanent reboots are still here with after optimization apps(wipe dalvik cash) and xmod for coc no matter with xposed it or not. If you nevertheless catch a bootloop or brutal hang which are unlikely to happen, shut down your tablet(volume up and power button) boot in twrp(volume up when it boot with yellow led) and wipe cash/dalvick cash with twrp and should run fine again.
It's totally worth it as it really enhances Android. GravityBox works too, so that alone is great.
As alex009988 says, there are still random crash+reboot problems, but people seem to get these without Xposed installed as well. After flashing Xposed you'll need to wipe cache/dalvik, which causes Android to 'optimize' all of the apps when booting into Android for the 1st time after. When that's done, you'll most likely get a crash and reoboot, but after that it'll just let you enter Android.
Make sure to put the Xposed uninstall .zip file on the tablet too - in cas eof issues you can uninstall Xposed. As for Xposed itself, you'll need the official SDK21 ARM64 build.
Marshmallow for this device, keeps crashing as it is (com.android.phone, RIL). Getting the problem solved is easy, @puntoazul already written something like that, but I managed to get everything that has to be flashed in a single post.
Flash these files, in the next order, from top to bottom:
- A-GAPPS_6.0.1_09022016.zip - https://mega.nz/#!M99xiQbZ!fcclA9QDSXxxizsifu21MUbgMGsyRsNCCHPO4KrF5xQ (thanks to @puntoazul for packing it)
- APNFixer4CM13.zip - http://forum.xda-developers.com/attachment.php?attachmentid=3689957&d=1458482477 (thanks to @puntoazul for packing it)
- UNIVERSAL NFC DESTROYER - http://forum.xda-developers.com/attachment.php?attachmentid=3280610&d=1429942749 (thanks to @-CALIBAN666- for developing it), yeah, it's made for lollipop but works perfectly.
- Media.zip (codecs pack) http://forum.xda-developers.com/attachment.php?attachmentid=3680746&d=1457817927 (thanks to @EdwinMoq for packing it.)
When you're done, do a factory reset and reboot your device. Then, enjoy Marshmallow .
EDIT: Media.zip seems to be a mistyped step, I haven't found it and it wasn't needed to get a successful startup on my device.
EDIT: It seems like it's needed, anyways, I haven't found it, waiting for @EdwinMoq to answer.
EDIT: Added Media.zip, found at http://forum.xda-developers.com/opt...ogenmod-13-t3303671/post65803228#post65803228 ( @EdwinMoq 's post).
facuarmo said:
Marshmallow for this device, keeps crashing as it is (com.android.phone, RIL). Getting the problem solved is easy, @puntoazul already written something like that, but I managed to get everything that has to be flashed in a single post.
Flash these files, in the next order, from top to bottom:
- A-GAPPS_6.0.1_09022016.zip - https://mega.nz/#!M99xiQbZ!fcclA9QDSXxxizsifu21MUbgMGsyRsNCCHPO4KrF5xQ (thanks to @puntoazul for packing it)
- APNFixer4CM13.zip - http://forum.xda-developers.com/attachment.php?attachmentid=3689957&d=1458482477 (thanks to @puntoazul for packing it)
- UNIVERSAL NFC DESTROYER - http://forum.xda-developers.com/attachment.php?attachmentid=3280610&d=1429942749 (thanks to @-CALIBAN666- for developing it), yeah, it's made for lollipop but works perfectly.
- Media.zip (codecs pack) http://forum.xda-developers.com/attachment.php?attachmentid=3680746&d=1457817927 (thanks to @EdwinMoq for packing it.)
When you're done, do a factory reset and reboot your device. Then, enjoy Marshmallow .
EDIT: Media.zip seems to be a mistyped step, I haven't found it and it wasn't needed to get a successful startup on my device.
EDIT: It seems like it's needed, anyways, I haven't found it, waiting for @EdwinMoq to answer.
EDIT: Added Media.zip, found at http://forum.xda-developers.com/opt...ogenmod-13-t3303671/post65803228#post65803228 ( @EdwinMoq 's post).
Click to expand...
Click to collapse
Ive been experiencing the same problems you have, but i found my own alternate way. Since this phone isnt my daily driver, i used lucky patcher to remove the phone services app aka com.android.phone from the system.Everything is fixed, all stabilized and smooth. I still get crashing from phone and messaging storage,but no lag or stability issues. But ill try this anyway to try to completely remedy the crashing
As only two entries for Orange seem to be missing in the APN database: Does everyone need that fix because the APN list is totally corrupted by this, or only certain Orange customers?
Elite.101 said:
Ive been experiencing the same problems you have, but i found my own alternate way. Since this phone isnt my daily driver, i used lucky patcher to remove the phone services app aka com.android.phone from the system.Everything is fixed, all stabilized and smooth. I still get crashing from phone and messaging storage,but no lag or stability issues. But ill try this anyway to try to completely remedy the crashing
Click to expand...
Click to collapse
Okay, please let me know what happened when you're done.
lecorbusier said:
As only two entries for Orange seem to be missing in the APN database: Does everyone need that fix because the APN list is totally corrupted by this, or only certain Orange customers?
Click to expand...
Click to collapse
For a better stability, you must flash it. For example, running this ROM without this patch, the RIL keeps crashing, taking in mind that Movistar and Tuenti (a lesser know Argentina provider, a recently started provider), are not being detected.
I'll wait for the next build. Then probably use it as a Wireless AP, as there are huge problems resulting from the small data partition and Ram. I still hope that MMs z-buffer feature provides some solution. This whole mess started about half a year ago and getting worse, on the L9 and a similarly featured tablet with CM11, so it's not the rom's fault. The tablet has plenty of space on the data partition, however, but ram and SoC face similar problems.
My current wireless AP is an Iphone 4s with only 0,5GB Ram. And it's is still working reliably, no apps freezing and fcing, and I can access websites which will make Firefox on the L9 and said tablet quit every time.
All the affected apps seem to deal with HTML code and are supposed to use the system webview engine. Updating the Google webview engine is possible with CM12.1 and 13, but to no avail, only taking space on the data partition.
facuarmo said:
Okay, please let me know what happened when you're done.
Click to expand...
Click to collapse
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showpost.php?p=65892603&postcount=395
As i have previously explained in original thread all of these files in a single go. with order defined
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) If you have a p768 flash campatch
Also flashed NFC Destroyer so that on booting for the first time... i did'n encountered any error at all.. i have been using this ROM as my daily driver and never encountered any kernel panic or ant other error also i didn't faced any rotation problem. its working fine as it should be. Only thing i am concerned about is battery, it drains very fast, tweaking with kernel auditor didn't help me either. other then this i haven't faced any problem, everything is working fine, i'm able to install Xposed framework without any problem.. Great work......
I have also tried this with New TWRP Recovery.... worked like a charm
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Can you tell me your real phone model? There're some hard incompatibilities between the P760 and the P769.
Codeplex said:
Follow this http://forum.xda-developers.com/showpost.php?p=65892603&postcount=395
As i have previously explained in original thread all of these files in a single go. with order defined
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) If you have a p768 flash campatch
Also flashed NFC Destroyer so that on booting for the first time... i did'n encountered any error at all.. i have been using this ROM as my daily driver and never encountered any kernel panic or ant other error also i didn't faced any rotation problem. its working fine as it should be. Only thing i am concerned about is battery, it drains very fast, tweaking with kernel auditor didn't help me either. other then this i haven't faced any problem, everything is working fine, i'm able to install Xposed framework without any problem.. Great work......
I have also tried this with New TWRP Recovery.... worked like a charm
Click to expand...
Click to collapse
Well, ill try this.The way i tried this was in a different order, but pretty much i have the phone under control since i uninstalled com.android.phone aka Phone Services and disabled Phone and messaging storage.
but i guess ill try this.i need the exact correct order with NFC Destroyer in the list in order of flashing.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
facuarmo said:
Can you tell me your real phone model? There're some hard incompatibilities between the P760 and the P769.
Click to expand...
Click to collapse
I currently Have the LG-P769. T-Mobile variant
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Codeplex said:
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Click to expand...
Click to collapse
Alright. Ill try this right now.Ima do a backup first.
Codeplex said:
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Click to expand...
Click to collapse
im still having problems. i just finished setting up and now i have a kernel panic.......reverting now
Elite.101 said:
Well, ill try this.The way i tried this was in a different order, but pretty much i have the phone under control since i uninstalled com.android.phone aka Phone Services and disabled Phone and messaging storage.
but i guess ill try this.i need the exact correct order with NFC Destroyer in the list in order of flashing.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
I currently Have the LG-P769. T-Mobile variant
Click to expand...
Click to collapse
The kernel panics that you're experiencing, are also being faced by most of the people who has tried the P760 build in the P769, please check the ROM @EdwinMoq 's post and download the special build for this model, and try again. Then, please tell me how it goes.
facuarmo said:
The kernel panics that you're experiencing, are also being faced by most of the people who has tried the P760 build in the P769, please check the ROM @EdwinMoq 's post and download the special build for this model, and try again. Then, please tell me how it goes.
Click to expand...
Click to collapse
Well specifically, i used the p769 version. i tried apn fixer, nfc destroyer and media.zip, but the problem persisted. so i just reverted back to my nandroid backup in which i uninstalled com.android.phone aka phone services and disabled phone and messaging storage.I have it stable this way without kernel panics and using gapps mini since this isnt my daily driver. My galaxy core prime is SMG360T1.
Elite.101 said:
Well specifically, i used the p769 version. i tried apn fixer, nfc destroyer and media.zip, but the problem persisted. so i just reverted back to my nandroid backup in which i uninstalled com.android.phone aka phone services and disabled phone and messaging storage.I have it stable this way without kernel panics and using gapps mini since this isnt my daily driver. My galaxy core prime is SMG360T1.
Click to expand...
Click to collapse
Hmmm... Idk, sorry. That's what I've learned from here, not much atm haha.
facuarmo said:
Hmmm... Idk, sorry. That's what I've learned from here, not much atm haha.
Click to expand...
Click to collapse
True.one thing I want fixed is the headphones problem where sound goes to speaker
Elite.101 said:
True.one thing I want fixed is the headphones problem where sound goes to speaker
Click to expand...
Click to collapse
That's quite strange, seems like a bad kernel. For me, using the P760 (in the P778g, Argentina, LATAM) works fine, both speakers (front and rear) and headphones.
When the headphone amp starts to clip/overdrive, this is accompanied by an unplugging event for the headphones. Artas' CM11 and CM12.1 are affected, too, but I could get my P760 to work with decent and stable sound output. While in Rammar's PA sound volume was even lower than with the stock rom(too low for even bothering to take the headphones with me) , CM12.1 is loudest. In order to not accidentially trip clipping and unplugging events, which will also reset volume to safety level, requiring to turn it up and clip again etc etc, Ilimited max volume to 80% in the Headset Button Controller app,which allows to control volume via headset mic button.
Note: I am not affiliated to the Dev team of this ROM, just a Note 7 user who would like to share the ROM with everyone here. Hence, NO dev support will be provided.
Some elements of the UI/ROM options are in Chinese, but I will not be providing translations unless there is demand. Thank you for your understanding
A Chinese dev team has recently released an Oreo port for the Note 7, and hence I am sharing it here for everyone to enjoy.
The original Dev thread (in Chinese): Here
Once again, I am not affiliated to the Dev team, so don't direct any questions/bugs as I will not know how to solve them.
Most of the info listed below is translated from the original thread.
Aurora ROM for Note 7 Exynos 8890
Supported devices:
Note 7 N930F/FD
Unsupported devices:
Note 7 N930S/L/K
[*]ROM will fail to boot on these devices, as the kernel does not support these models yet.
ROM Information
Full Oreo 8.0 port based on the Note FE stock ROM
Stock UI, but with additional customization options
Multi-language support. A few elements may be in Chinese, but 90% of the UI will be in the chosen language.
Custom Aurora kernel for better battery life and stability
Pre-rooted, able to choose from SuperSU or Magisk on install
De-bloated
Full S-Pen support
Added Dolby Atmos audio effect
Advanced power menu - fast reboot, recovery, download mode, safe mode
Wallpapers and lock screen ported from the S9
No time limit/paywall, unlike the Soul ROM that has been floating around this forum
Device model changed to Samsung S8+ (SM-G9550)
Will not change or update the baseband
Things that are working:
Everything
except... (see below)
Things that are not working:
Iris scanner
Mobile data usage tracking (can be circumvented with 3rd party apps)
That's it
Bugs:
None known thus far
Screenshots:
Here
Installation guide:
1. Boot into TWRP recovery with home+volume up+power on while the device is off.
2. Do a full backup (optional, but always helpful in case something goes wrong)
3. Perform a full wipe (system, data, cache)
4. Flash the installer zip (download link below).
5. Follow the pictures in the album: How to install
6. The first boot may take 10-15 mins. Be patient.
7. Once the setup wizard pops up, change the language to English (or any language of your choice)
8. Reboot your device after configuring
9. Your Note 7 is ready for use
Special note: Do not update any system apps as the device model has been modified, and updating system apps may cause errors.
Download link:
http://www.mediafire.com/file/6sgn1b50lqsy2bz/Aurora_N930X_N935X_OREO_RG4_V1.0_2.zip/file
FAQ section (translated from the original dev thread)
Q: Google play services keeps stopping
A: Go to app permissions in settings and enable location access for Google play services.
Q: Unable to sync Google contacts
A: Go to app permissions -> Contacts, and enable all 3 settings for Google play services.
Note: The ROM comes with Google Play store installed but disabled by default. Refer to bomcoi1402's comment to see how to enable it.
Can you help me to install Google services? (Google play, Gmail, Maps, Google account manager, ...)
Thank somuch!
Update: I was installed. In Aurora app.
Hey guys, if you like using your device, DO NOT INSTALL this rom, it has a lot of chinese apps, and if you try to flash another rom your device would constantly be restarting itself.
I couldn't figure how to install google ?
After checking Aurora App setting WHAT?
Can you help me ?
I installed a gapps but Play services Stopped. @bomcoi1402
@IcyDevil_ can you translate FAQ section?
Edit: Thx for answers I will try again
10 cmt for upload picture
@ReTekno: do not install gApps. You can factory reset, then see pictures and do it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@KAL26: I was installed this rom from last week and everything okey now ^^~
KAL26 said:
Hey guys, if you like using your device, DO NOT INSTALL this rom, it has a lot of chinese apps, and if you try to flash another rom your device would constantly be restarting itself.
Click to expand...
Click to collapse
Are you sure we installed the same ROM? As far as I can see, the only Chinese app installed is the ROM settings, no others. Not quite sure about the flashing another ROM part, but have you done a full wipe before flashing? Dirty flashing may cause issues sometimes so it's not recommended to dirty flash.
ReTekno said:
I couldn't figure how to install google ?
After checking Aurora App setting WHAT?
Can you help me ?
I installed a gapps but Play services Stopped. @bomcoi1402
@IcyDevil_ can you translate FAQ section?
Click to expand...
Click to collapse
@ReTekno, have translated the FAQ section. Do take a look to see if it solves your issue.
Guys, how can I remove chinese text on the control panel ?
IcyDevil_ said:
Are you sure we installed the same ROM? As far as I can see, the only Chinese app installed is the ROM settings, no others. Not quite sure about the flashing another ROM part, but have you done a full wipe before flashing? Dirty flashing may cause issues sometimes so it's not recommended to dirty flash.
Click to expand...
Click to collapse
Yes i installed the same ROM, i did a full wipe and i still have random restarts. Thanks to this ROM i can't use my phone anymore. I'll see if i'll manage to get it working eventually.
You can try it.
Only one problem, this is don't push notification of Facebook, Messenger, Zalo.
I still don't know how to fix it.
ugur142015 said:
Guys, how can I remove chinese text on the control panel ?
Click to expand...
Click to collapse
I still don't know
KAL26 said:
Yes i installed the same ROM, i did a full wipe and i still have random restarts. Thanks to this ROM i can't use my phone anymore. I'll see if i'll manage to get it working eventually.
Click to expand...
Click to collapse
Same issue, but not with this rom (Note8 Port Full Note7/FE). Any solution!
Push notifications
[/COLOR]
bomcoi1402 said:
You can try it.
Only one problem, this is don't push notification of Facebook, Messenger, Zalo.
I still don't know how to fix it.
Click to expand...
Click to collapse
You can easily fix it by uninstalling the brevent app
Brevent prevents apps from running in background that is why when your screen is off you wont get any push notifications
vicioso3 said:
Same issue, but not with this rom (Note8 Port Full Note7/FE). Any solution!
Click to expand...
Click to collapse
Sadly i don't think there is a solution, I tried everything, factory reset, full wipe, re-root, nothing works, still getting random restarts, and the worse is happening whenever i try to update or install any apps, either from play store or from galaxy apps. Thanks to this crap, i now have an unusable brick of a note7.
KAL26 said:
Sadly i don't think there is a solution, I tried everything, factory reset, full wipe, re-root, nothing works, still getting random restarts, and the worse is happening whenever i try to update or install any apps, either from play store or from galaxy apps. Thanks to this crap, i now have an unusable brick of a note7.
Click to expand...
Click to collapse
And who asked you to do this? It looks a lot like a personal problem to me. I am running the other Chinese Oreo ROM for a long time with no problems. Tried this one too and it was good, but I just didn't want to fix all the Chinese again. I might try the Aurora kernel when I have the time.
I really suggest you study all the information available on this forum before you share nothing but frustrated rants. BTW, I can't see a way how you can brick this phone permanently. In the worst of all cases there is always Odin.
ulev said:
And who asked you to do this? It looks a lot like a personal problem to me. I am running the other Chinese Oreo ROM for a long time with no problems. Tried this one too and it was good, but I just didn't want to fix all the Chinese again. I might try the Aurora kernel when I have the time.
I really suggest you study all the information available on this forum before you share nothing but frustrated rants. BTW, I can't see a way how you can brick this phone permanently. In the worst of all cases there is always Odin.
Click to expand...
Click to collapse
What made you think i have a personal problem or that this simply is a frustrated rant? I simply told my experience in trying this ROM, and apparently i'm not the only one having issues with it. Due to all the chinese apps, and various other issues, i simply didn't like this ROM, and when i tried to flash another ROM, i got the problems i mentioned. I've been installing ROM's on my various phones for many years now, i'm not a noob when it comes to rooting, ROM's and other custom things you can do to and android device. I tried ODIN aswell, and still no changes, so i simply voiced my opinion. Next time try to be less frustrated yourself, and less judgy.
KAL26 said:
What made you think i have a personal problem or that this simply is a frustrated rant? I simply told my experience in trying this ROM, and apparently i'm not the only one having issues with it. Due to all the chinese apps, and various other issues, i simply didn't like this ROM, and when i tried to flash another ROM, i got the problems i mentioned. I've been installing ROM's on my various phones for many years now, i'm not a noob when it comes to rooting, ROM's and other custom things you can do to and android device. I tried ODIN aswell, and still no changes, so i simply voiced my opinion. Next time try to be less frustrated yourself, and less judgy.
Click to expand...
Click to collapse
Well, there is a long line of posts by you in this thread that are indicating that you should not have started using a device that has been withdrawn by the manufacturer.
BTW, I did not mean to say YOU have a problem (how would I know?). I simply wanted to say your problems should not be generalized as indicative of what can be done with this device.
I still don't see any reason why you can't flash back an older Android 7 version with Odin and have a flawless, Chinese free experience of this nice device until it dies. Again, the problems you are describing are related to your device or environment, not to the Note7 per se.
In fact, I would like to understand, how you initially overcame Samsung's blocking of the phone and how you proceeded since then. This would provide an indication what might have gone wrong. Your ranting does not.
And only so you understand, I am writing this on my Note7 with the Soul Vip11 Oreo ROM where I added my own mods to eliminate 99% of the Chinese crap and the pay wall. Once I 8did a TWRP backup and installed this ROM without any problem and played around with it for a while until I restored my old one,again no problem. There was no incentive for me to polish up this ROM and install all my apps again, would have been a total waste of time.
This should explain to you, that those Chinese ROMs might be a PITA, but they are also not intended for us Westerners. So if you can't handle them, simply don't go there.
ulev said:
Well, there is a long line of posts by you in this thread that are indicating that you should not have started using a device that has been withdrawn by the manufacturer.
BTW, I did not mean to say YOU have a problem (how would I know?). I simply wanted to say your problems should not be generalized as indicative of what can be done with this device.
I still don't see any reason why you can't flash back an older Android 7 version with Odin and have a flawless, Chinese free experience of this nice device until it dies. Again, the problems you are describing are related to your device or environment, not to the Note7 per se.
In fact, I would like to understand, how you initially overcame Samsung's blocking of the phone and how you proceeded since then. This would provide an indication what might have gone wrong. Your ranting does not.
And only so you understand, I am writing this on my Note7 with the Soul Vip11 Oreo ROM where I added my own mods to eliminate 99% of the Chinese crap and the pay wall. Once I 8did a TWRP backup and installed this ROM without any problem and played around with it for a while until I restored my old one,again no problem. There was no incentive for me to polish up this ROM and install all my apps again, would have been a total waste of time.
This should explain to you, that those Chinese ROMs might be a PITA, but they are also not intended for us Westerners. So if you can't handle them, simply don't go there.
Click to expand...
Click to collapse
Maybe you didn't understood what i wrote in my first post. What i said was that i installed this ROM, tried to use it, and due a lot of chinese apps, i couldn't get used to it, so i flashed the ROM i was using before, and that's when the problems began. Random restarts, device would freeze up. I did backup, full wipe, factory restore, re-did the entire root process, I even tried ODIN, without any luck. Before installing this ROM, my device worked flawlessly, It was rooted before installing this, with the Nougat Note FE ROM, no issues. So for me this ROM messed up my device in some way.
KAL26 said:
Maybe you didn't understood what i wrote in my first post. What i said was that i installed this ROM, tried to use it, and due a lot of chinese apps, i couldn't get used to it, so i flashed the ROM i was using before, and that's when the problems began. Random restarts, device would freeze up. I did backup, full wipe, factory restore, re-did the entire root process, I even tried ODIN, without any luck. Before installing this ROM, my device worked flawlessly, It was rooted before installing this, with the Nougat Note FE ROM, no issues. So for me this ROM messed up my device in some way.
Click to expand...
Click to collapse
All I can say: Do a TWRP backup first if you want to experiment. Has been said on XDA thousands of times. And READ the OP fully before you jump into it.
And if I had your problem, I am quite sure I would fix it silently myself. You may have to format (not wipe). Also, a remaining SAMSUNG function in the bootloader may try to keep you from going back to NOUGAT, so as a last option you might have to live with one of the Chinese OREO ROMs before you figure out what to do.
In any case, the real experts (besides the Chinese) have all moved on. Nobody around anymore who would help you. And I obviously don't like your style... :silly: