Database Develop

[Q] Xposed on I537? Working, anyone try?

I am a bit nervous to take the plunge and try out Xposed on my Active. Just rooted it yesterday, installed the Google edition Rom. Now I am wondering if Xposed will work on stock or the Google Edition. I will give it a go if no one has tried yet.

AkFatherof4nCounting said:
I am a bit nervous to take the plunge and try out Xposed on my Active. Just rooted it yesterday, installed the Google edition Rom. Now I am wondering if Xposed will work on stock or the Google Edition. I will give it a go if no one has tried yet.
Click to expand...
Click to collapse
Xposed works fine, I haven't run into any problems. Since you're using SafeStrap anyways there's no harm in trying things for yourself. Even if something does go wrong you can always wipe your slot and start over, that's pretty much the whole reason for SafeStrap.

Devo7v said:
Xposed works fine, I haven't run into any problems. Since you're using SafeStrap anyways there's no harm in trying things for yourself. Even if something does go wrong you can always wipe your slot and start over, that's pretty much the whole reason for SafeStrap.
Click to expand...
Click to collapse
Good to know. A possible stupid question here, would it be best to load my back up of my stock onto one of the ROM Slots? To try out the Xposed. I am coming from HTC One X, so roms and such are done a bit different, I am not quite used to the ROM slot.

AkFatherof4nCounting said:
Good to know. A possible stupid question here, would it be best to load my back up of my stock onto one of the ROM Slots? To try out the Xposed. I am coming from HTC One X, so roms and such are done a bit different, I am not quite used to the ROM slot.
Click to expand...
Click to collapse
I'm not exactly sure what you're trying to do. In your first post you mentioned that you have the GPE ROM installed (I assume you have it in slot 1) and you want to install Xposed to it. There should be no problems doing this since ROMs are independent of each other and do not share any data.
I think what you really need to know is how SafeStrap works. Basically, SafeStrap creates new ROM "slots" while preserving your stock ROM "slot". These slots are completely independent of each other and only share a kernel. So any changes you make to one ROM will not impact the other. Now it is possible to flash a new ROM to your stock "slot", but this is not how SafeStrap is intended to work. Ideally you install a ROM to a new slot and use that ROM as your daily driver. The stock ROM is supposed to be your fallback in case you mess anything up with your new ROM. You are more than welcome to modify your stock ROM or even install a new ROM to your stock slot, but if you do this and you mess something up with your stock slot you could risk bricking your phone. That is why it is recommended that you don't mess with your stock ROM.
As for your original question, there is no need to install your stock ROM to a new ROM slot since it is already there, all you are doing is taking up twice as much space on your phone.

Devo7v said:
I'm not exactly sure what you're trying to do. In your first post you mentioned that you have the GPE ROM installed (I assume you have it in slot 1) and you want to install Xposed to it. There should be no problems doing this since ROMs are independent of each other and do not share any data.
I think what you really need to know is how SafeStrap works. Basically, SafeStrap creates new ROM "slots" while preserving your stock ROM "slot". These slots are completely independent of each other and only share a kernel. So any changes you make to one ROM will not impact the other. Now it is possible to flash a new ROM to your stock "slot", but this is not how SafeStrap is intended to work. Ideally you install a ROM to a new slot and use that ROM as your daily driver. The stock ROM is supposed to be your fallback in case you mess anything up with your new ROM. You are more than welcome to modify your stock ROM or even install a new ROM to your stock slot, but if you do this and you mess something up with your stock slot you could risk bricking your phone. That is why it is recommended that you don't mess with your stock ROM.
As for your original question, there is no need to install your stock ROM to a new ROM slot since it is already there, all you are doing is taking up twice as much space on your phone.
Click to expand...
Click to collapse
I understand I was a bit unclear. I do have the Google edition installed, but I am encountering massive reboots. I was going to uninstall it and install a backup version of the stock in to the ROM Slot containing the Google edition. I understand I do not want to mess with my stock Slot, that is why I wanted to install my Stock Rom into the Rom Slot I made. Which, sounds like it is the safest bet.

AkFatherof4nCounting said:
I understand I was a bit unclear. I do have the Google edition installed, but I am encountering massive reboots. I was going to uninstall it and install a backup version of the stock in to the ROM Slot containing the Google edition. I understand I do not want to mess with my stock Slot, that is why I wanted to install my Stock Rom into the Rom Slot I made. Which, sounds like it is the safest bet.
Click to expand...
Click to collapse
I would recommend deleting Slot 1, recreate it and install the GPE ROM again. A lot of people have been using it without issue including myself. The only known problem with the GPE ROM is computers do not detect the phone as a usb mass storage device when using the ROM.
If you are having issues with reboots I suggest deleting the slot and starting over from scratch. Also make sure your slot is big enough for the ROM and anything you're going to install. If the slot is too small you could run into the issues you've mentioned.
As to installing your stock ROM to a slot, why not just try another ROM? There are plenty of regular S4 ROMs that work on our phone. You are not limited to the ROMs that are found in the development section of this forum. There are at least 5 other ROMs I have tried and I'm sure there are many more that work as well.
I guess I'm just missing the point of why you want to install your stock ROM to another slot if you already have it? I'm sure there are ROMs already existing that can do what you are trying to modify your stock ROM to do. I recommend trying out Hyperdrive for tons of features. I personally use the GPE ROM found in this forum. Check out this thread for more information on ROMs that work with the S4 Active and SafeStrap.

@Devo7v, thanks, will reinstall and give it a shot. Thank you for your time.

[Q] Moving from CM11 back to Stock or Otherwise

Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.

Nicholo said:
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Click to expand...
Click to collapse
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.

simple_fear85 said:
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
Click to expand...
Click to collapse
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.

If you want to stick to CM11, you can upgrade your baseband to 24A and use jackpotclavin's build, it works well but it hasn't been updated past 4.4.2 I believe.

Nicholo said:
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.[/QUOTE
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
All aosp roms now that are 4.4.4 are running the 24a bootstack or kitkat.
Click to expand...
Click to collapse

no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
Click to expand...
Click to collapse
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.

Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
You use autorec for twrp?
Sent from my LG-VS980 using XDA Free mobile app

Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If so, flash the 2.7.x.x zip within your current recovery, then reboot recovery. If you don't have a custom recovery, then use autorec or freedom tool to install one.
Sent from my VS980 4G using XDA Premium 4 mobile app

[Q] I cant install CyanogenMod on my LG G2. Any more ways to install it?

I am unable to install Cyanogenmod. I have TWRP that was installed with AutoRec. I tried flashing the Stable 10.2 CM version,and when I flashed it said "Failed", which put me into a security error boot loop. Then I tried a nightly, and it said "Success" and when I tried to start it up, it put me into another boot loop. I have the stock Kernel, and I am rooted. Is something like goo manager or rom manager better to use for this? Or what is the safest way to install a custom ROM

Zach_Deem said:
I am unable to install Cyanogenmod. I have TWRP that was installed with AutoRec. I tried flashing the Stable 10.2 CM version,and when I flashed it said "Failed", which put me into a security error boot loop. Then I tried a nightly, and it said "Success" and when I tried to start it up, it put me into another boot loop. I have the stock Kernel, and I am rooted. Is something like goo manager or rom manager better to use for this? Or what is the safest way to install a custom ROM
Click to expand...
Click to collapse
JackpotClavin's version is the only one that works on the VS980. http://forum.xda-developers.com/showthread.php?t=2702958
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app

What he said, the official nighties only work with the JB baseband.

So is there any other way to do this? I saw that is is extremely risky, and it will permanently brick my phone. Is there any other thing im able to do to flash this?

Zach_Deem said:
So is there any other way to do this? I saw that is is extremely risky, and it will permanently brick my phone. Is there any other thing im able to do to flash this?
Click to expand...
Click to collapse
If you want CM11 with the KK baseband(24A), use the version z3pp3lin pointed you to, otherwise most other AOSP based roms have already been upgraded to work with the KK baseband, use one of those. Just double check the notes on the rom to make sure it's KK/24A based.

Do I have to do all of those steps? You said there is a like for cyanogenmod for 24a. I don't see one though

Zach_Deem said:
Do I have to do all of those steps? You said there is a like for cyanogenmod for 24a. I don't see one though
Click to expand...
Click to collapse
All those steps are required to manually install a recovery on KK, that was pre-autorec, if you've already installed TWRP, you can skip to step 11.

mjones73 said:
All those steps are required to manually install a recovery on KK, that was pre-autorec, if you've already installed TWRP, you can skip to step 11.
Click to expand...
Click to collapse
So I can only use his roms?

Zach_Deem said:
So I can only use his roms?
Click to expand...
Click to collapse
You have the 24A KK baseband on your phone, you can only use roms that work with that baseband. If you specifically want CM11, you need to use the rom linked, otherwise any other 24A KK based rom will work. Check the notes for any rom you want to install to see what baseband it works with.

mjones73 said:
You have the 24A KK baseband on your phone, you can only use roms that work with that baseband. If you specifically want CM11, you need to use the rom linked, otherwise any other 24A KK based rom will work. Check the notes for any rom you want to install to see what baseband it works with.
Click to expand...
Click to collapse
So If I want cm, I have to use his links correct? I just want to be sure so I don't get another bootloop

Why not just use a AOSP or CM based ROM that works with the 24A baseband... CM is good, but hardly the "best" ROM out there, if there is such a thing... Try AICP 6.0, it is extremely stable and the VS980 version is excellent and very feature packed.

Zach_Deem said:
So If I want cm, I have to use his links correct? I just want to be sure so I don't get another bootloop
Click to expand...
Click to collapse
For about the 4th time, yes.

mjones73 said:
For about the 4th time, yes.
Click to expand...
Click to collapse
Im about to flash the cm version and we will see how this goes

I downloaded the rom onto my phone but I'm scared for some reason. Is it guaranteed to not brick if I'm on the right version?

Zach_Deem said:
I downloaded the rom onto my phone but I'm scared for some reason. Is it guaranteed to not brick if I'm on the right version?
Click to expand...
Click to collapse
Not too freak you out more, but no, there is no guarantee. That's why every ROM has the disclaimer in the OP. By flashing you're taking responsibility that you understand the risks involved. If you flash cm and damage your phone somehow, it's on you. So it's either stay with rooted stock where you know nothing will happen, or flashing and taking the risk. Your choice...

njstein said:
Not too freak you out more, but no, there is no guarantee. That's why every ROM has the disclaimer in the OP. By flashing you're taking responsibility that you understand the risks involved. If you flash cm and damage your phone somehow, it's on you. So it's either stay with rooted stock where you know nothing will happen, or flashing and taking the risk. Your choice...
Click to expand...
Click to collapse
Alright, but is there any way to know if a rom is successfully flashed other than it saying successful or restarting?

Zach_Deem said:
Alright, but is there any way to know if a rom is successfully flashed other than it saying successful or restarting?
Click to expand...
Click to collapse
No.

All ROM installs a failure except in the beginning

I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks

David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens

David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
We have two versions of safestrap and each one works with a different OS.
1.Safestrap 3.71: that works ONLY with jellybean roms. Use it (If your phone says "4.3 MI9, MJ5, or NB4" in your "about phone" in settings) to flash any jellybean rom. Read the title of any rom you're attempting to flash. If it says "4.4.2 KK or Kitkat or NC2" then stay away.
2. Safestrap 3.72/3.75 ([emoji118] this is recommended) that works ONLY with Kitkat roms. Use it (If your phone says "4.4.2 NC2" in your "about phone" in settings) to flash any Kitkat/NC2 rom. Read the title of any rom you're attempting to flash. If it says "4.3 jellybean or JB" then stay away.

K-alz said:
We have two versions of safestrap and each one works with a different OS.
1.Safestrap 3.71: that works ONLY with jellybean roms. Use it (If your phone says "4.3 MI9, MJ5, or NB4" in your "about phone" in settings) to flash any jellybean rom. Read the title of any rom you're attempting to flash. If it says "4.4.2 KK or Kitkat or NC2" then stay away.
2. Safestrap 3.72/3.75 ([emoji118] this is recommended) that works ONLY with Kitkat roms. Use it (If your phone says "4.4.2 NC2" in your "about phone" in settings) to flash any Kitkat/NC2 rom. Read the title of any rom you're attempting to flash. If it says "4.3 jellybean or JB" then stay away.
Click to expand...
Click to collapse
basicaly what he said.. and since you said you did dynamic kat and alliance.. sounds like you are on the nc2 with Kitkat..
So, best bet is going to be make sure you have ss 3.75 and only flash the kitkat roms.. Dynamic kat, Alliance, Tweaked, Firekat, and you should be fine.. just dont try and flash any that are JB
From my Fired-up Note Pro 12.2!

Thank you. A combo of Android version AND baseband at the end?
Are the version numbers I'm looking for, a combination of the Android version (4.4.2) and the end of the Baseband number (NC2)
Basically I tried everything and your suggestions should very very suspiciously like everything I've done But.. I will give it one more shot.
Any possibility of SafeStrap 3.72 would work as opposed to 3.75 not working?
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
Version 4.42. I'll give everything a shot here although, I've tried all of this but maybe I've missed something. Thank you for responding.
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse

bodycode said:
Are the version numbers I'm looking for, a combination of the Android version (4.4.2) and the end of the Baseband number (NC2)
Basically I tried everything and your suggestions should very very suspiciously like everything I've done But.. I will give it one more shot.
Any possibility of SafeStrap 3.72 would work as opposed to 3.75 not working?
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
Version 4.42. I'll give everything a shot here although, I've tried all of this but maybe I've missed something. Thank you for responding.
Click to expand...
Click to collapse
yeah if you are seeing 4.4.2 and nc2 you are on KK.. just make sure you are on 3.75 and all should be ok with flashing..
if for some reason it is borked,, go down to carls thread for odin files and how to odin back to stock nc2 and then start over and you should be fine
From my Fired-up Note Pro 12.2!

NO good. 3.75/stock slot/Alliance ROM fails.
Same ****. Black screen.
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse

NO good. 3.75 fails!
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse

AFter creating another slot and wipe, system mounting errors.
System mount errors all over the place after creating another slot, and installing Alliance. What's going on here? Something's really screwed up.
e: unable to mount '/system'
e: unable to mount '/systemorig'
over and over again
Can't check permissions after FActory reset. Please boot rom and try again after you reboot into recovery.
David Sanborn said:
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
Click to expand...
Click to collapse

David Sanborn said:
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
Click to expand...
Click to collapse
I would simply restore back to mj5 and start over. I did this last night simply to reset my phone cause I flash way to much lol. I would give that a try though. Thread is in the general section

How to restore to Mj5?
How do I downgrade to Mj5 from KK4.2?
Thanks
warfenix said:
I would simply restore back to mj5 and start over. I did this last night simply to reset my phone cause I flash way to much lol. I would give that a try though. Thread is in the general section
Click to expand...
Click to collapse

David Sanborn said:
How do I downgrade to Mj5 from KK4.2?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559715

I know what your problem is brother. This same crap happened to me. To a T! For some reason when u wipe system in safesteap, it wipes everything out. EVERYTHING. except data. I learned the hard way,like u. So when u flash roms, don't wipe system, only factory reset. I wipe it 3× every time. Then install your Rom. You will b fine. I haven't had one problem ever since I stopped wiping system. And no random reboots or anything, Roms now flash, and boot as they should. Hope this helps.

David Sanborn said:
How do I downgrade to Mj5 from KK4.2?
Thanks
Click to expand...
Click to collapse
Dude. If you're on NC2 then don't ever do the MJ5. It'll give the same problem. Just Odin the first four files from this thread http://forum.xda-developers.com/showthread.php?t=2838117 then root with towelroot/install busybox (make sure to install it from within the app as well) then install ss 3.72 or 3.75 then start flashing Kitkat roms.

K-alz said:
Dude. If you're on NC2 then don't ever do the MJ5. It'll give the same problem. Just Odin the first four files from this thread http://forum.xda-developers.com/showthread.php?t=2838117 then root with towelroot/install busybox (make sure to install it from within the app as well) then install ss 3.72 or 3.75 then start flashing Kitkat roms.
Click to expand...
Click to collapse
True but I think his problem is wiping system when he installs roms. If he's still not able to boot up right then ya he needs to use Odin and those files to get up and running again.
I just wish it was like the note 2. With unlocked bootloader and real twrp recovery.

zounduser said:
True but I think his problem is wiping system when he installs roms. If he's still not able to boot up right then ya he needs to use Odin and those files to get up and running again.
I just wish it was like the note 2. With unlocked bootloader and real twrp recovery.
Click to expand...
Click to collapse
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz

K-alz said:
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
Click to expand...
Click to collapse
Oh I agree. I've had to do it. I'm saying going forward so it doesn't happen again.

4 files in odin flash, done that 15 times.
I've flashed Odin stock COUNTLESS times! When I go back to flash kitkat ROMS, same **** all over again. Unbelievable. I'm at my wits end. My phone DOES boot with the Odin files. But when flashing anything else with safestrap, black screen again.
K-alz said:
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
Click to expand...
Click to collapse

David Sanborn said:
I've flashed Odin stock COUNTLESS times! When I go back to flash kitkat ROMS, same **** all over again. Unbelievable. I'm at my wits end. My phone DOES boot with the Odin files. But when flashing anything else with safestrap, black screen again.
Click to expand...
Click to collapse
You used the files in the thread I gave you a couple of posts back and it didn't work? Man I hope you still have your warranty. Just flash back to stock and take your phone to the AT&T warranty center and make up and issue with your phone and tell them that you can't deal with your phone anymore and get you a new phone. They believe about anything. If that didn't work then head to bestbuy if there is one by you and ask them to reflash the system for you (that's of course after you flash back to stock).

Not a block screen on Odin and no trips.
Did I mention Odin works fine? Knox is not tripped. All is well right after Odin upload to phone in Download mode. It's only when I flash anything that blackscreen curses me again. heh heh.
K-alz said:
You used the files in the thread I gave you a couple of posts back and it didn't work? Man I hope you still have your warranty. Just flash back to stock and take your phone to the AT&T warranty center and make up and issue with your phone and tell them that you can't deal with your phone anymore and get you a new phone. They believe about anything. If that didn't work then head to bestbuy if there is one by you and ask them to reflash the system for you (that's of course after you flash back to stock).
Click to expand...
Click to collapse

[Q] My phone is stuck in a bootloader loop

I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed

Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app

Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.

Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)

absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile

Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.

Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4

I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.

ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.