Hey guys I have not seen this in the Q&A section and I want to make sure I do it right.
I only recently rooted my Nexus 7, been running stock but decided I wanted to have Multi Windows like I have on my Note 4. I have not decided on a ROM as I was looking for the best one so I am still running Stock Rooted 5.0.2 I saw Omni ROM and I think that this would be the best ROM to attempt this as I tried the Xposed method and of course got the boot loop.
I see that currently on OmniROM.com that this device is still running on KK 4.4.4 according to the nightlies. I assume I would need to find a KK stock ROM and flash it on to my Nexus to downgrade back to KK in order to install this ROM, or will this install with TWRP even though I'm running Lollipop?
If so does someone have a quick link to the Stock KK files? I used Wug's Nexus Root Toolkit to root my device as I did not feel like going through the same hassel as when I rooted my Droid RAZR so I would just tell that to use those files instead.
I am always flashing ROMs on my Note 4 but I have never gone backwards and I think it was possible to install KK ROM once you upgrade to lolly but not use a lolly ROM if your still on KK.
Soulforged666 said:
Hey guys I have not seen this in the Q&A section and I want to make sure I do it right.
I only recently rooted my Nexus 7, been running stock but decided I wanted to have Multi Windows like I have on my Note 4. I have not decided on a ROM as I was looking for the best one so I am still running Stock Rooted 5.0.2 I saw Omni ROM and I think that this would be the best ROM to attempt this as I tried the Xposed method and of course got the boot loop.
I see that currently on OmniROM.com that this device is still running on KK 4.4.4 according to the nightlies. I assume I would need to find a KK stock ROM and flash it on to my Nexus to downgrade back to KK in order to install this ROM, or will this install with TWRP even though I'm running Lollipop?
If so does someone have a quick link to the Stock KK files? I used Wug's Nexus Root Toolkit to root my device as I did not feel like going through the same hassel as when I rooted my Droid RAZR so I would just tell that to use those files instead.
I am always flashing ROMs on my Note 4 but I have never gone backwards and I think it was possible to install KK ROM once you upgrade to lolly but not use a lolly ROM if your still on KK.
Click to expand...
Click to collapse
I don't think anyone has done a compatibility check to see what happens if you run a 4.4 build on a device with 5.x bootloaders. It might work, it might do weird things (usually with sensors/wifi)
Multiwindow never got merged, if you want it you'll have to build for yourself and cherrypick it. There were some remaining issues with the patch we never had time to fix, we got too busy with other stuff, and xplodwild wants to rewrite the whole thing after finding a better way to implement it.
Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.
Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
https://www.youtube.com/watch?v=ck6e8y4S3tQ
ithehappy said:
Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
Click to expand...
Click to collapse
Same with you, but I got this problem after I flash from CM13 and want back to eRobot / stock ROM
That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.
ithehappy said:
That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.
Click to expand...
Click to collapse
I already try it using the WanamLite Modem + Bootloader. Still didnt work
Hmm, no idea then. If you find any solution kindly don't forget to tag me.
AlStarsKyz said:
Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.
Click to expand...
Click to collapse
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
And when even flashing CM 13 the phone don't start ?
ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
Yes i used CM13 and function smoothly, but there couple bugs such Spen, and 4G didn't work in my country and when i try to flashing the stock rom, it's stuck on samsung logo.
*Simpati ra kenek 4Gne mas )
i got the same issue on my note 4 n910h is frustrating there is any solution to this or just wait until Samsung release a new update of 6.0 for the note 4
Try this 4 part factory firmware it's full wipe rom https://mega.nz/#!eJIUiLQD!r-HcKWRWd...VriCeWYdNpxeTo
Or http://d-h.st/EPj8
http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk
HmanA6399 said:
http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk
Click to expand...
Click to collapse
Gonna try that. Thanks m8 for the help )
Hey, guys as we all know The stock marshmallow for note 4 is out. Is it possible to flash it without boot looping to famous Samsung-logo. If there is a way I would really appreciate the help.
Hi guys,
Not sure if this is the right place to post this but unless I am missing something, I have yet to find a thread or instructions on how to do this.
I am on Pure Nexus, but I posted here because I'm guessing the answer applies to virtually any custom ROM. What are the steps involved in upgrading from a custom 6.0 ROM to the newly released Android 7.0? Is there a way to do this while keeping root?
Thanks,
speedemonV12 said:
Hi guys,
Not sure if this is the right place to post this but unless I am missing something, I have yet to find a thread or instructions on how to do this.
I am on Pure Nexus, but I posted here because I'm guessing the answer applies to virtually any custom ROM. What are the steps involved in upgrading from a custom 6.0 ROM to the newly released Android 7.0? Is there a way to do this while keeping root?
Thanks,
Click to expand...
Click to collapse
There's roms you can flash, other than that just wait for the images to release and there will be alot options
So if it's a custom ROM based on 7.0 I can go ahead and flash using that specific ROM instructions?
I thought the official 7.0 came out yesterday, that's why I was wondering if I could update to the official and keep root and how to do that.
speedemonV12 said:
So if it's a custom ROM based on 7.0 I can go ahead and flash using that specific ROM instructions?
I thought the official 7.0 came out yesterday, that's why I was wondering if I could update to the official and keep root and how to do that.
Click to expand...
Click to collapse
I'd Mae a backup send it to PC and try tupac4us rom or digitalhighs . They have vendors built in the zip .
I was on Benzo rom and this is exactly what I did; I restored back to stock rom only leaving bootloader unlocked. I joined the Android beta and the N ota was ready to install. I then flashed the latest twrp. I made sure to do a full nandroid and physically backed up anything important to my laptop before I restored to stock. I noticed until I flashed ditialhighs N rom my twrp would not "stick" but no big deal I just flashed it and went into recovery. It seems Android Pay is working with digitialhighs rom, you just toggle off root, use it, toggle back. Good luck
Which guide did you use for restoring to stock while keeping the bootloader unlocked?
i was on pure nexus 6.1 i used this guide to revert everything back to stock then i subscribed to the developer program and got 7.0 update in seconds, section 14 is pretty much all you need
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sorry in advance if this is a dumb question but I have an old OP5 sitting in a drawer that I'm not using anymore- it's already rooted and running a custom Android 6 ROM that I had flashed.
I was going to give it to a friend but I wanted to flash an Android 10 ROM on it for him before handing it over (he doesn't know how to do this stuff).
I wanted to know if I can wipe the phone, flash a newer version of TWRP and then either OOS 10 or a custom Q ROM, or if I have to flash it to OOS 6, then 7, 8, 9 before I can put an Android 10 ROM on it.
I vaguely remember going 2 versions up on this device before (possibly back in the lollipop era) and if I recall correctly I had to flash the next Android version before flashing to the version after that in order for the custom ROM to work, but it's been a long time. Thanks in advance for any wisdom you can offer.
teeWrex said:
Sorry in advance if this is a dumb question but I have an old OP5 sitting in a drawer that I'm not using anymore- it's already rooted and running a custom Android 6 ROM that I had flashed.
I was going to give it to a friend but I wanted to flash an Android 10 ROM on it for him before handing it over (he doesn't know how to do this stuff).
I wanted to know if I can wipe the phone, flash a newer version of TWRP and then either OOS 10 or a custom Q ROM, or if I have to flash it to OOS 6, then 7, 8, 9 before I can put an Android 10 ROM on it.
I vaguely remember going 2 versions up on this device before (possibly back in the lollipop era) and if I recall correctly I had to flash the next Android version before flashing to the version after that in order for the custom ROM to work, but it's been a long time. Thanks in advance for any wisdom you can offer.
Click to expand...
Click to collapse
if u want android 10 you can just flash the latest firmware which is on the crdroid sourceforge page and then u can install a android 10 custom rom or oos 10 be sure to wipe data partition
@Trey n Awesome, thank you!