Related
so i recently dove into rooting my s4 after first spending a lot of time reading this great board, thought i had a handle on it, thought things were going very well, but i've hit a snag, which came while attempting my first restore - i'm hopeful someone will give me a little help,
a little background:
1. before rooting i backed up my phone with titanium, also backed it up by copying all of its contents to my pc.
2. i followed the excellent "[SGH-M919] CF-Auto-Root" instructions and it worked without a hitch, it was a quick and easy process, no surprises.
3. confirmed that i was rooted using "root checker", all systems were go.
4. once the root was done i made another backup using titanium and sms backup. i also made a full system backup using online nandroid pro and, to be extra safe, i also backed up efs using efs backup tool.
5. i then moved some folders and files to my external card and once again backed up my phone as before, including to my pc.
6. feeling confident that i could now restore my system to its rooted stock state if things went south, i decided to flash my first rom with cwm, i went with cm11 m7 4.4.3 - i saved the cm11 and gapps zips to my external card using rom tool box pro, rebooted into cwm recovery, selected the two files, and flashed. i also did a data and cache wipe before doing so.
6. needless to say i was thrilled when cm11 loaded perfectly, it worked great, and it was just what i was hoping for.
7. having been bitten by the apparent ease of flashing roms, i decided to restore my system to it's pre cm11 state, to it's rooted stock rom state, and try another rom, rather than just flash another rom from cm11 - i wanted to make sure that returning to my rooted stock rom state would be a simple matter.
and that's where i've run into problems.
1. as i mentioned i made two system backups of my stock rom before flashing cm11, one right after i rooted my phone, and one after moving some folders and files to the external card.
2. after doing a wipe, i chose to restore the second backup, the one i made after moving files and folders, and it didn't quite work out - everything appeared to restore perfectly, but my device was immediately inundated with pop up warnings about stopped apps, i also got a persistent warning that the system had stopped responding as well, prompting me to choose between "wait" or "stop it". not only was the restored backup mired in popup screens, but it was impossibly slow, impossibly "laggy".
3. so i decided to restore the other stock backup, the one i made before i moved folders and files, and the results were the same, pop screens for apps not working, system warnings, severe lags, etc., identical to the first backup.
then i panicked.
1. i decided to flash my phone with the "[SGH-M919] CF-Auto-Root" file again, again with odin, hoping that it would put me where i started - i didn't stop to think that my phone was already rooted, that the file was was for unrooted phones.
2. not only did the reflash not work (my phone just booted as normal, as if the flash didn't get a chance to finish), but cwm recovery in boot mode was gone, replaced by what appears to be the andorid stock recovery screen, a screen with an animated dying/collapsing robot, - the screen was titled: "android system recovery <3e> and asked for an "update" from the external storage or cache.
3. not knowing what "update" it was looking for, i selected a backed system files (the first rooted stock rom backup i made, the second rooted stock backup i made, and even the cm11 file) - none worked.
4. i then downloaded a clean stock rom from cwm's website, converted it from zip to tar, and tried to flash it using odin with my device in upload mode, it didn't work either.
so how badly did i mess up my phone? any help would be greatly appreciated.
aeneas1 said:
so i recently dove into rooting my s4 after first spending a lot of time reading this great board, thought i had a handle on it, thought things were going very well, but i've hit a snag, which came while attempting my first restore - i'm hopeful someone will give me a little help,
a little background:
1. before rooting i backed up my phone with titanium, also backed it up by copying all of its contents to my pc.
2. i followed the excellent "[SGH-M919] CF-Auto-Root" instructions and it worked without a hitch, it was a quick and easy process, no surprises.
3. confirmed that i was rooted using "root checker", all systems were go.
4. once the root was done i made another backup using titanium and sms backup. i also made a full system backup using online nandroid pro and, to be extra safe, i also backed up efs using efs backup tool.
5. i then moved some folders and files to my external card and once again backed up my phone as before, including to my pc.
6. feeling confident that i could now restore my system to its rooted stock state if things went south, i decided to flash my first rom with cwm, i went with cm11 m7 4.4.3 - i saved the cm11 and gapps zips to my external card using rom tool box pro, rebooted into cwm recovery, selected the two files, and flashed. i also did a data and cache wipe before doing so.
6. needless to say i was thrilled when cm11 loaded perfectly, it worked great, and it was just what i was hoping for.
7. having been bitten by the apparent ease of flashing roms, i decided to restore my system to it's pre cm11 state, to it's rooted stock rom state, and try another rom, rather than just flash another rom from cm11 - i wanted to make sure that returning to my rooted stock rom state would be a simple matter.
and that's where i've run into problems.
1. as i mentioned i made two system backups of my stock rom before flashing cm11, one right after i rooted my phone, and one after moving some folders and files to the external card.
2. after doing a wipe, i chose to restore the second backup, the one i made after moving files and folders, and it didn't quite work out - everything appeared to restore perfectly, but my device was immediately inundated with pop up warnings about stopped apps, i also got a persistent warning that the system had stopped responding as well, prompting me to choose between "wait" or "stop it". not only was the restored backup mired in popup screens, but it was impossibly slow, impossibly "laggy".
3. so i decided to restore the other stock backup, the one i made before i moved folders and files, and the results were the same, pop screens for apps not working, system warnings, severe lags, etc., identical to the first backup.
then i panicked.
1. i decided to flash my phone with the "[SGH-M919] CF-Auto-Root" file again, again with odin, hoping that it would put me where i started - i didn't stop to think that my phone was already rooted, that the file was was for unrooted phones.
2. not only did the reflash not work (my phone just booted as normal, as if the flash didn't get a chance to finish), but cwm recovery in boot mode was gone, replaced by what appears to be the andorid stock recovery screen, a screen with an animated dying/collapsing robot, - the screen was titled: "android system recovery <3e> and asked for an "update" from the external storage or cache.
3. not knowing what "update" it was looking for, i selected a backed system files (the first rooted stock rom backup i made, the second rooted stock backup i made, and even the cm11 file) - none worked.
4. i then downloaded a clean stock rom from cwm's website, converted it from zip to tar, and tried to flash it using odin with my device in upload mode, it didn't work either.
so how badly did i mess up my phone? any help would be greatly appreciated.
Click to expand...
Click to collapse
If it boots at all you didn't kill it.
Not sure what rom you got from the CWM site. They do recoveries, not roms. The ROM manager app does allow you to download roms, but you can't just convert those from zip to tar. That doesn't make them flashable in Odin.
Here's what you do. Get the stock ROM from either here on XDA (use the search feature to find it) or from Sammobile.com.
Flash that in Odin.
Then you can start over.
---OR---
If you want to try to fix what you've got now, download CWM or TWRP RECOVERY (nor ROM) and flash that in Odin. Boot to recovery, wipe data and system, and flash any other rom you want. That will start you over with a fresh rom of your choice.
Skipjacks said:
f it boots at all you didn't kill it.
Click to expand...
Click to collapse
hallelujah!
Skipjacks said:
Not sure what rom you got from the CWM site. They do recoveries, not roms.
Click to expand...
Click to collapse
my apologies, i meant that i downloaded recovery files from the cwm website, not a rom files - i got them from https://www.clockworkmod.com/rommanager - i downloaded both (touch & non-touch) s4 t-mobile versions (6.0.4.7). i'm assumed those were recovery files?
Skipjack" said:
The ROM manager app does allow you to download roms, but you can't just convert those from zip to tar. That doesn't make them flashable in Odin.
Click to expand...
Click to collapse
again, my apologies - i meant that i downloaded *.img files, not zips, and converted them to tars for odin use. i used a batch file to convert them from img to tar, found at xda, here: http://forum.xda-developers.com/showthread.php?t=2281287 - it seemed to do the job, odin ran and reported success. wrong files? wrong conversion?
Skipjack said:
Here's what you do. Get the stock ROM from either here on XDA (use the search feature to find it) or from Sammobile.com.
Flash that in Odin.
Then you can start over.
---OR---
If you want to try to fix what you've got now, download CWM or TWRP RECOVERY (nor ROM) and flash that in Odin. Boot to recovery, wipe data and system, and flash any other rom you want. That will start you over with a fresh rom of your choice.
Click to expand...
Click to collapse
given a choice, i'd like to do what's bolded in red - but that's what i thought i was doing by flashing the cwm file i downloaded from the cwm website - but after the flash attempt it wouldn't boot into cwm, it would just boot into (i'm assuming") the stock rom i restored, which was a mess. i also unchecked auto-boot to see if that helped - but when i manually booted it didn't boot into cwm, it booted into the stock recovery, with the animated android.
i'll try downloading cwm from the sources you provided, and see if that does the trick. btw, why do you think i was able to flash the cm11 rom with (seemingly) perfect success, but wasn't able to restore either one of the full system (android) backups i made after i rooted my phone?
anyway Skipjack, thanks a ton for your assistance and i'll report back after i give your sources a try. fwiw, it sure is a great charge when a newbie like me sees a custom rom load for the first time, displaying a new ui as it boots, fun stuff.
Just download the ready yo flash tar files. Cwm has them. Twrp has them.
success Skipjack thanks to your generous time and assistance!
i ended up downloading the latest odin zip i could find and philz_touch_6.08.9-jfltetmo.tar.md5... my first try didn't take, with auto-reboot checked, my phone simply rebooted into the same problematic rom i had restored. i then tried it with auto-boot unchecked and manually booted when odin reported pass/success, and it worked. what struck me as odd was how long it took to flash, to report pass/success, around 3-5 minutes if i had to guess, a big difference compared to when i first used odin to root my phone with the["SGH-M919] CF-Auto-Root *.tar.md5 file - i'm guessing that's why it didn't work with auto-boot checked, just took too long?
anyway once i booted into philz_touch recovery i executed the wipe data/factory reset > clean to install a new rom command and then flashed the cm11 m7 (snapshot) rom, which i had flashed once before, right before i attempted to restore the stock rom it had replaced. and as was the case the first time around, it installed without a hitch and is running smooth and fast.
however now when i boot the phone, as soon as the cyanogen logo appears, very tiny text appears in the upper left hand corner which reads (i had to use a magnifying glass!) - it doesn't seem to effect the performance of he device but i'd like to get to the bottom of it, i've already searched and it appears to be a rather common issue.
kernel is not seandroid enforcing
set warranty bit: kernel
btw, i forgot to mention, when i purchased my sgh-m99 it already had 4.3 installed - when i flashed my first rom (cm11 m7) it included kitkat 4.4.2... could this be what caused my problems? did trying to go back to (restore) a 4.3 rom after flashing a 4.4.2 rom screw things up? can this even be done successfully?
and finally, at the risk of bugging the heck out of you, what roms do you prefer for your s4, assuming you have an s4? do you like aosp roms or touchwiz? does one type have a better reputation of being more stable? the primary reason i wanted to rot my phone was to get rid of a bunch of t-mobile / samsung bloatware, which i thought i could do by installing a lean custom rom. any suggestions, which are your favorites? thanks again Skipkack.
ouhned after
re the two lines of text i now get in the upper left hand corner of the screen whenever i boot, the kernel message:
kernel is not seandroid enforcing
set warranty bit: kernel
well after a lot of searching and reading, including coming across dozens of "fixes" and "solutions" that didn't seem to work for many folks, these two responses seemed to make some sense, what do you think?
eclpsues said:
I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.
Click to expand...
Click to collapse
Joku1981 said:
You are right.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2594483
aeneas1 said:
re the two lines of text i now get in the upper left hand corner of the screen whenever i boot, the kernel message:
kernel is not seandroid enforcing
set warranty bit: kernel
well after a lot of searching and reading, including coming across dozens of "fixes" and "solutions" that didn't seem to work for many folks, these two responses seemed to make some sense, what do you think?
http://forum.xda-developers.com/showthread.php?t=2594483
Click to expand...
Click to collapse
The tiny text on the boot screen is basically telling you that Knox has been tripped. You are right. It does not affect the performance of the phone.
Skipjacks said:
The tiny text on the boot screen is basically telling you that Knox has been tripped. You are right. It does not affect the performance of the phone.
Click to expand...
Click to collapse
thanks skipjack... btw i'm really liking the cm11 m7 rom but, via the learning curve process, i've discovered it does not support wifi calling, something that apparently all aosp rom lack, guess i'll have to go with a touchwiz rom even tho the selection seems to be few and far between. also, is it possible to revert back to 4.3 once 4.4.2 has been flashed? seems like there's a lot of mixed opinions on this, altho in terms of those opinions it's hard for me tell who the pros are that should believed, and who the other guys are that really don't know. thanks again.
aeneas1 said:
thanks skipjack... btw i'm really liking the cm11 m7 rom but, via the learning curve process, i've discovered it does not support wifi calling, something that apparently all aosp rom lack, guess i'll have to go with a touchwiz rom even tho the selection seems to be few and far between. also, is it possible to revert back to 4.3 once 4.4.2 has been flashed? seems like there's a lot of mixed opinions on this, altho in terms of those opinions it's hard for me tell who the pros are that should believed, and who the other guys are that really don't know. thanks again.
Click to expand...
Click to collapse
Once you are rooted you can flash any custom ROM 4.3, 4.4, 4.2, etc. and then go back to stock 4.3. And only TW ROMs allow wifi calling
Sent from my SGH-M919 using XDA Premium 4 mobile app
Kriptik210 said:
Once you are rooted you can flash any custom ROM 4.3, 4.4, 4.2, etc. and then go back to stock 4.3. And only TW ROMs allow wifi calling.
Click to expand...
Click to collapse
very interesting... i guess i misunderstood the posts i read on the subject, maybe they were discussing whether or not you could revert to 4.3 from 4.4.2 on non-rooted phones, which i'm guessing isn't possible. anyway, as i mentioned previously, i fist rooted my 4.3 phone, did a full system backup (using online nandroid), flashed a 4.4.2 rom which worked perfectly, then tried to restore my 4.3 backup only to encounter a bunch of problems, thought going from 4.4.2 back to 4.3 may have caused the problems but i guess not?
so if i'm using a 4.4.2 custom rom and want to restore a 4.3 backup i should be able to boot into recovery and restore from there? or would i need to do a 4.3 flash first, before restoring a 4.3 backup?
aeneas1 said:
very interesting... i guess i misunderstood the posts i read on the subject, maybe they were discussing whether or not you could revert to 4.3 from 4.4.2 on non-rooted phones, which i'm guessing isn't possible. anyway, as i mentioned previously, i fist rooted my 4.3 phone, did a full system backup (using online nandroid), flashed a 4.4.2 rom which worked perfectly, then tried to restore my 4.3 backup only to encounter a bunch of problems, thought going from 4.4.2 back to 4.3 may have caused the problems but i guess not?
Click to expand...
Click to collapse
Did you wipe before you restored? And do not misunderstand this, you cannot downgrade firmwares once you go 4.3 and up, but you can downgrade the system, which is what you did with your backup
serio22 said:
Did you wipe before you restored? And do not misunderstand this, you cannot downgrade firmwares once you go 4.3 and up, but you can downgrade the system, which is what you did with your backup
Click to expand...
Click to collapse
thanks very much for the clarification, i was under the impression that firmware and system were somewhat synonymous in this context, i.e. if you upgraded firmware you were in effect upgrading the system, but i see that's not the case, again thanks. and yes i did do a full wipe before trying to restore the backup, was i not supposed to?
aeneas1 said:
thanks very much for the clarification, i was under the impression that firmware and system were somewhat synonymous in this context, i.e. if you upgraded firmware you were in effect upgrading the system, but i see that's not the case, again thanks. and yes i did do a full wipe before trying to restore the backup, was i not supposed to?
Click to expand...
Click to collapse
Updating firmware does update the system. Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware. Firmware consists of bootloader, recovery, modem, and system, what you cannot downgrade is the bootloader, the flash will fail every time because it will try to downgrade it. And you should not experience any issues restoring your back up. What were this problems?
btw serio22, do you have a favorite tw rom?
Yea serio22, what is your favorite TW ROM?
Sent from my SGH-M919 using XDA Premium 4 mobile app
serio22 said:
Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware.
Click to expand...
Click to collapse
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
btw, fwiw, - now that i'm up and running thanks to skipjacks help, i decided to try restoring my 4.3 backup again. when i tried this in the past it would restore to the same state as it was before but it was virtually unusable because of severe lags and multiple app not working popups that made navigating almost impossible. well now when i try to restore it fails and i get the following message:
checking md summs...
md5 mismatch
serio22 said:
Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware.
Click to expand...
Click to collapse
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
btw, fwiw, - now that i'm up and running thanks to skipjacks help, i decided to try restoring my 4.3 backup again. as i mentioned, when i tried this in the past it would restore to the same state as it was before but it was virtually unusable because of severe lags and multiple "app not working" popups that made navigating almost impossible. but now when i try to restore the 4.3 backup it fails and i get the following message:
checking md summs...
md5 mismatch
update:
well it looks like the *.md5 file was pointing to my internal drive rather than external which is where i had moved the 4.3 backup (and apparently the *.md5 file didn't update or account for the move), anyway i copied the backup to my internal drive and, viola, no more md5 mismatch errors. more importantly, it restored the 4.3 backup perfectly, in the exact same state as before, without all of lagging and pop up issues i was having before, so i'm one happy camper! not sure what i did the first time around, but all is good now, for he time being, sure wish i knew what i mucked up to cause the problems in the first place, i really have no idea, other than being a newbie at this. also, fwiw, the tiny text in the upper left hand corner that appears during boot (kernal message) no longer appears now that i have restored the 4.3 system backup... fwiw2, i'm liking the philz_touch_recovery but it sure has taken some getting used to, the commands are so close together and the thing is so sensitive, very easy to accidentally select the wrong option, and some of the wrong options aren't too friendly if it wasn't what you had intended to select.
aeneas1 said:
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
Click to expand...
Click to collapse
Read my previous post more closely below. Good to see you up and running though! And no I don't have a favorite tw Rom
serio22 said:
Updating firmware does update the system. Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware. Firmware consists of bootloader, recovery, modem, and system, what you cannot downgrade is the bootloader, the flash will fail every time because it will try to downgrade it.
Click to expand...
Click to collapse
out of nowhere, my 3rd party apps aren't able to access the internal storage. Yahoo mail can't download attachments. Firefox can't download anything. Titanium Backup can't make backups. Etc.
I've tried:
Factory reset
Reinstalling SuperSU
Fixing Permissions through TWRP recovery
Fixing individual app permissions through an app.
Formatting internal storage
The only thing that fixed this it seems was to format the internal storage, factory reset and then flash stock 4.4.2.
Then everything was fine for about 2 weeks then suddenly my 4g went away. I had to factory reset because PRL/Profile and even reactivation wouldn't get it to stick.
So after a day of 4g again, once more I'm running into the same storage issue as above. WTF is going on?
I run into that issue when going from TW to a different rom and then try going back to TW. It's been irritating and stupid. I never had this problem prior to taking the Ota to the latest TW.
I've noticed when SuperSU says it's disabled Knox, I'll check the installed apps in app manager. Samsung Knox is right there. A) should it not be there and SuperSU goofed? B) if it is, does that make a difference?
Also on this other thread, there's a SELinux permissive kernal. http://forum.xda-developers.com/showthread.php?t=2747586#post54371724
Would that do anything? I'm nervous about flashing kernals just because that's where I hear people brick the most (because they downgrade) and that's where I'm the least familiar.
brokenmouse said:
I've noticed when SuperSU says it's disabled Knox, I'll check the installed apps in app manager. Samsung Knox is right there. A) should it not be there and SuperSU goofed? B) if it is, does that make a difference?
Also on this other thread, there's a SELinux permissive kernal. http://forum.xda-developers.com/showthread.php?t=2747586#post54371724
Would that do anything? I'm nervous about flashing kernals just because that's where I hear people brick the most (because they downgrade) and that's where I'm the least familiar.
Click to expand...
Click to collapse
they brick mostly because they flash the wrong kernel and so use this one http://forum.xda-developers.com/showthread.php?t=1800576 if on AOSP use the version for that if on TW use that version. After you flash the kernel flash the NDC Modem some have said this gave them better signal on the ND8 stock 4.4.2
PS. SuperSU disables Knox it just doesn't delete Knox Apps....there's a flashable zip that can delete those and one to that will also remove most Google/Samsung apps as well
6th_Hokage said:
they brick mostly because they flash the wrong kernel and so use this one http://forum.xda-developers.com/showthread.php?t=1800576 if on AOSP use the version for that if on TW use that version. After you flash the kernel flash the NDC Modem some have said this gave them better signal on the ND8 stock 4.4.2
PS. SuperSU disables Knox it just doesn't delete Knox Apps....there's a flashable zip that can delete those and one to that will also remove most Google/Samsung apps as well
Click to expand...
Click to collapse
Thanks. I'll give that one a shot later today. I just can't figure out what's triggering the internal storage access from working to suddenly not working.
This is what i've done time and time again:
I format the internal storage and factory wipe through TWRP
I ODIN this: http://forum.xda-developers.com/showthread.php?t=2738533
ODIN TWRP recovery
I flash the autoroot (found somewhere)
I flash the hotspot mod (odex)
I install Titanium Backup and try to restore my texts
I'm not doing anything crazy. No crazy apps. It's driving me nuts.
brokenmouse said:
Thanks. I'll give that one a shot later today. I just can't figure out what's triggering the internal storage access from working to suddenly not working.
This is what i've done time and time again:
I format the internal storage and factory wipe through TWRP
I ODIN this: http://forum.xda-developers.com/showthread.php?t=2738533
ODIN TWRP recovery
I flash the autoroot (found somewhere)
I flash the hotspot mod (odex)
I install Titanium Backup and try to restore my texts
I'm not doing anything crazy. No crazy apps. It's driving me nuts.
Click to expand...
Click to collapse
try also Philz Touch recovery....it works 100% of the time on stock ND8 and can root it so you wont need the auto root thing
hey guys... i have 2 att s3's... the one is running CM11 M12, and the other is fully stock...
my wife found out the hard way today that her GPS does not work (CM11/M12 snapshot on NE4 baseband). i have been reading all this about going back to stock for the dial pad menu options and doing the nvram fix and etc etc.... my question is, since i have a stock s3 with the latest NJ1 bootloader and baseband... can't i make a complete backup of that and restore it to her s3 running CM11/M12, get the menu options, do the fix, and restore back to CM11/M12? or will that change the baseband and bootloader back to NE4??
wow... nothin from no one?
A nandroid won't touch bootloader or modem. I don't think an nj1 stock nandroid will boot on ne4 firmware unless you flash a custom kernel too. I would not try it.
It would be easier to just flash an ne4 based touchwiz ROM on her phone. You need a stock dialer to run the ussd code to get into the maintenance menu and do the nvrebuild thing it sounds like you've read up on.
You can find a rooted stock ne4 ROM in the forums here. Talking monkeys and s3rx are both tw and ne4 based so they should work fine too. Just read up and flash carefully.
jason2678 said:
A nandroid won't touch bootloader or modem. I don't think an nj1 stock nandroid will boot on ne4 firmware unless you flash a custom kernel too. I would not try it.
It would be easier to just flash an ne4 based touchwiz ROM on her phone. You need a stock dialer to run the ussd code to get into the maintenance menu and do the nvrebuild thing it sounds like you've read up on.
You can find a rooted stock ne4 ROM in the forums here. Talking monkeys and s3rx are both tw and ne4 based so they should work fine too. Just read up and flash carefully.
Click to expand...
Click to collapse
well, that's kinda half what i am saying... if i restore to the backup i made of the original, i can get the ota update and go from there...
DigiManTX said:
well, that's kinda half what i am saying... if i restore to the backup i made of the original, i can get the ota update and go from there...
Click to expand...
Click to collapse
Restoring an NJ1 nandroid on NE4 firmware might work, it might not, I'm not really sure. I've never tried it and no one has posted any horror stories on here about it that I've seen. If it does actually boot, I think there's a good chance wifi or data (and maybe some other things) won't work right with an NJ1 stock rom on NE4 firmware without flashing a custom kernel too, not that you care too much about that if you're just using it for the GPS fix. It is probably too Frankenphone for an OTA to work, and since it is an up to date NJ1 rom it might not even trigger an OTA. If you try this, make sure you have a nandroid of your CM11, or a CM rom zip readily available for a bail out plan in case this just bootloops. I wouldn't recommend this. I'm just not sure it will work. I doubt it will hard brick, but why tempt fate? AT&T S3's have been really finicky about firmware since Knox was forced on them from MJB onward.
To fix GPS all you really need is a stock dialer. Step 3 in this thread has recovery flashable, near stock AT&T NE4 roms. If flashed properly, I am sure this will work.
You have a higher probability of success if you do this. Make a nandroid backup of CM11 on her phone. Clean flash one of the NE4 roms from the thread above. A full format of the internal storage is recommended when switching from AOSP to TW (sometimes the TW rom just won't boot if you don't), but if you do a full format make sure your CM11 nandroid and the stock rom you're going to flash are stored on an external microSD or you've verified that you can adb push or copy files over usb using mtp when in custom recovery. Otherwise you'll be left with a totally blank phone and no rom to install or backups available. A little microSD preloaded with the files is the most reliable way to go.
Once you're up and running in the stock rom, skip all the setup stuff as best you can and get to a dialer. Open your stock dialer and enter *#197328640#
That should open a menu. Now navigate Mainmenu -> UMTS -> Common -> NVREBUILD -> NVREBUILD
Don't exit or hit home after telling it to rebuild the NVRAM. Let it sit for 30+ seconds, then long press power and pick restart.
Once your phone boots back up open up Google maps and see if location locks, it should now. At this point you can boot into your custom recovery, restore the CM11 backup you made, and enjoy your custom ROM with working location service. It might not be necessary, but I always do all the wipes for a clean flash and format the internal storage again before restoring the nandroid. This takes about an extra 30 seconds and keeps any TW files from getting left over in your AOSP setup.
I've had to do this twice to fix GPS on my phone and it works.
jason2678 said:
Restoring an NJ1 nandroid on NE4 firmware might work, it might not, I'm not really sure. I've never tried it and no one has posted any horror stories on here about it that I've seen. If it does actually boot, I think there's a good chance wifi or data (and maybe some other things) won't work right with an NJ1 stock rom on NE4 firmware without flashing a custom kernel too, not that you care too much about that if you're just using it for the GPS fix. It is probably too Frankenphone for an OTA to work, and since it is an up to date NJ1 rom it might not even trigger an OTA. If you try this, make sure you have a nandroid of your CM11, or a CM rom zip readily available for a bail out plan in case this just bootloops. I wouldn't recommend this. I'm just not sure it will work. I doubt it will hard brick, but why tempt fate? AT&T S3's have been really finicky about firmware since Knox was forced on them from MJB onward.
To fix GPS all you really need is a stock dialer. Step 3 in this thread has recovery flashable, near stock AT&T NE4 roms. If flashed properly, I am sure this will work.
You have a higher probability of success if you do this. Make a nandroid backup of CM11 on her phone. Clean flash one of the NE4 roms from the thread above. A full format of the internal storage is recommended when switching from AOSP to TW (sometimes the TW rom just won't boot if you don't), but if you do a full format make sure your CM11 nandroid and the stock rom you're going to flash are stored on an external microSD or you've verified that you can adb push or copy files over usb using mtp when in custom recovery. Otherwise you'll be left with a totally blank phone and no rom to install or backups available. A little microSD preloaded with the files is the most reliable way to go.
Once you're up and running in the stock rom, skip all the setup stuff as best you can and get to a dialer. Open your stock dialer and enter *#197328640#
That should open a menu. Now navigate Mainmenu -> UMTS -> Common -> NVREBUILD -> NVREBUILD
Don't exit or hit home after telling it to rebuild the NVRAM. Let it sit for 30+ seconds, then long press power and pick restart.
Once your phone boots back up open up Google maps and see if location locks, it should now. At this point you can boot into your custom recovery, restore the CM11 backup you made, and enjoy your custom ROM with working location service. It might not be necessary, but I always do all the wipes for a clean flash and format the internal storage again before restoring the nandroid. This takes about an extra 30 seconds and keeps any TW files from getting left over in your AOSP setup.
I've had to do this twice to fix GPS on my phone and it works.
Click to expand...
Click to collapse
ok... awesome... makes sense at what ur saying. thank you. so you didn't bother with updating the band and just left it on ne4? and yes, i would plan on making a full backup of her cm11 and throw it on the ext SD as well...
DigiManTX said:
ok... awesome... makes sense at what ur saying. thank you. so you didn't bother with updating the band and just left it on ne4? and yes, i would plan on making a full backup of her cm11 and throw it on the ext SD as well...
Click to expand...
Click to collapse
There should be no need to update your bootloader and modem from NE4 to NJ1. I think NE4 is still working just fine even on the latest lollipop alphas available for this phone.
If you feel the need, there is a recovery flashable bootloader/modem update to NJ1 here. I flashed this to get my phone up to NJ1. You can trust anything enewman posts.
On the newer AT&T firmware be sure to always have a matching bootloader/modem (seems to go for MJB, NE4, and NJ1 - everything post Knox). That's why it makes sense to package them together, like has been done in that zip. Always read carefully and upgrade incrementally if you choose to. I don't know if it is some sort of security "feature" thinking something nefarious is going on if bootloader and modem don't match or what, but some hard bricks have been reported if you try to run AT&T S3's without matched bootloader/modem on these firmware revisions.
jason2678 said:
There should be no need to update your bootloader and modem from NE4 to NJ1. I think NE4 is still working just fine even on the latest lollipop alphas available for this phone.
If you feel the need, there is a recovery flashable bootloader/modem update to NJ1 here. I flashed this to get my phone up to NJ1. You can trust anything enewman posts.
On the newer AT&T firmware be sure to always have a matching bootloader/modem (seems to go for MJB, NE4, and NJ1 - everything post Knox). That's why it makes sense to package them together, like has been done in that zip. Always read carefully and upgrade incrementally if you choose to. I don't know if it is some sort of security "feature" thinking something nefarious is going on if bootloader and modem don't match or what, but some hard bricks have been reported if you try to run AT&T S3's without matched bootloader/modem on the these firmware revisions.
Click to expand...
Click to collapse
right on... thank you again! if ne4 is good, then so be it... i just rather not have a shoe thrown at me over this GPS not working thing... lol
DigiManTX said:
right on... thank you again! if ne4 is good, then so be it... i just rather not have a shoe thrown at me over this GPS not working thing... lol
Click to expand...
Click to collapse
Happy wife, happy life
NE4 and NJ1
I've posted questions about the boot-loader "update" over in the other forum and from what I have read , updating from NE4 to NJ1 is basically to return to stock unrooted, some people have reported that the signal drops and GPS was better when going to NJ1, but I've been told that If you are not experiencing issues then there's no need to update.
you have GOT to be kidding me... i finally had the opportunity to do this and it's failing on the restore of the backup i made right beforehand... made a complete backup of everything i had to choose. over 2 gigs... flash the stock rooted, did the nvram rebuild, got the gps lock... all was golden... now trying to restore the cm11 backup and it fails... she is going to kill me now... it was nice knowing you guys...
***edit... and now even going back to cm11 or slimkat, i still don't have gps again... grrrrrr...
DigiManTX said:
you have GOT to be kidding me... i finally had the opportunity to do this and it's failing on the restore of the backup i made right beforehand... made a complete backup of everything i had to choose. over 2 gigs... flash the stock rooted, did the nvram rebuild, got the gps lock... all was golden... now trying to restore the cm11 backup and it fails... she is going to kill me now... it was nice knowing you guys...
***edit... and now even going back to cm11 or slimkat, i still don't have gps again... grrrrrr...
Click to expand...
Click to collapse
That stinks. Did you enable compression on the backup? Did you format internal SD before trying to restore the backup? I don't think the format thing is an absolute must, but it is good practice. If you don't do it you will find some touchwiz files that survive the restore in your AOSP based system. Make sure your backup is stored on an external SD before you do an internal format!
If you can't get the backup to restore after formatting internal storage or you just don't want to try formatting internal storage, here are a couple other things you can try to salvage it.
Titanium Backup has an extract from nandroid backup feature. This could be a Pro feature, I'm not sure. Going pro supports some great developers and unlocks some of the best features, like being able to make a flashable zip of your backups. I find it to be worth the money. This has a chance of being able to get you your apps and app data back, if the backup isn't somehow corrupted beyond being useful.
If it is user data like pictures and such you're worried about, you should be able to copy the nandroid backup to a PC, then extract data.ext4.win archive and explore the files. If the built-in Windows zip utility won't handle it, try 7zip. If the data archive is split (you find a data.ext4.win000, data.ext4.win001, etc) you have to concatenate the files into a usable tar. Combining split archives is fairly simple if you're running Linux, but I'm not sure how to manage it if your PC is running Windows. At the size you mentioned I don't think you'll encounter a split data archive, but I'm not certain. This also assumes that the nandroid isn't corrupted beyond the point of being useful.
As for the GPS thing, if you flash enough roms it happens. I've had to do it twice. Once was after just a few flashes. The second time was after probably dozens. After the second time I keep a nandroid backup of a stock rom on my external SD just so I can quickly revert to stock, rebuild nvram, the revert back to Slimkat.
jason2678 said:
That stinks. Did you enable compression on the backup? Did you format internal SD before trying to restore the backup? I don't think the format thing is an absolute must, but it is good practice. If you don't do it you will find some touchwiz files that survive the restore in your AOSP based system. Make sure your backup is stored on an external SD before you do an internal format!
If you can't get the backup to restore after formatting internal storage or you just don't want to try formatting internal storage, here are a couple other things you can try to salvage it.
Titanium Backup has an extract from nandroid backup feature. This could be a Pro feature, I'm not sure. Going pro supports some great developers and unlocks some of the best features, like being able to make a flashable zip of your backups. I find it to be worth the money. This has a chance of being able to get you your apps and app data back, if the backup isn't somehow corrupted beyond being useful.
If it is user data like pictures and such you're worried about, you should be able to copy the nandroid backup to a PC, then extract data.ext4.win archive and explore the files. If the built-in Windows zip utility won't handle it, try 7zip. If the data archive is split (you find a data.ext4.win000, data.ext4.win001, etc) you have to concatenate the files into a usable tar. Combining split archives is fairly simple if you're running Linux, but I'm not sure how to manage it if your PC is running Windows. At the size you mentioned I don't think you'll encounter a split data archive, but I'm not certain. This also assumes that the nandroid isn't corrupted beyond the point of being useful.
As for the GPS thing, if you flash enough roms it happens. I've had to do it twice. Once was after just a few flashes. The second time was after probably dozens. After the second time I keep a nandroid backup of a stock rom on my external SD just so I can quickly revert to stock, rebuild nvram, the revert back to Slimkat.
Click to expand...
Click to collapse
i just gave up on restoring the backup... somehow some way it magically got deleted off my sd card anyways... i just got to my wits end after that... she didn't kill me and kinda had that "whatever" face...
as far as the GPS working goes... idk what i am doing wrong here. i used the stock rooted rom that i downloaded from the option 3 link. not sure of the differences between the odex and the de-odexed, but i just went with the 1st... in TWRP, i did advance wipe (checked dalvik, system, data, internal, and cache... left micro sd and usb-otg alone), then went back and chose format data, then another advanced wipe with aforementioned options chosen... then rebooted straight into recovery. flashed the stock rooted rom, rebooted again and stock rom came up... went thru all the bs prompts and bypassed what i could. got to the dialer, did the nvram rebuild, waited a min, rebooted, tried maps and also download gps status app... got fixes, saw sats, etc... rebooted and flashed to cm11, pico gapps (since restore didn't work) and started fresh... got maps and gps status app downloaded... no GPS lock, no sats listing in gps status app... tried flashing to slimkat, same deal... and this is where i be now... about to make a smoothie in my vitamix out of these 2 s3's... OH! and this is on both of them... the one running ne4 AND nj1... same procedures done on both...
ok, i just did the same procedure but this time just went with slimkat from fresh and GPS is good... must be a "me" problem or a CM problem... idk... but at least i can work with slimkat... i kinda dig this rom
So. Entirely new to the all of this. I've managed to get OctOS running on my SPH-L710T, I'm running TWRP custom recovery, and that's all very nice. The problem I'm having is that I'm only getting basic cellular and 3G service. I'm completely unable to connect to any sort of LTE. My google-fu has gotten me as far as:
-I need to flash a different modem because oh boy tri-band
-That modem might be ND8 or NDC, and I can get ahold of those with a quick search.
-I Can easily brick my phone if I don't do this right.
I'm uncertain of what to do with this. I don't know which recovery I should use to odin in the modem. Do I flash the modem first, then reinstall OctOs? Are there other things I need to do? Are either of these even the right modem?
Any and all help would be super appreciated. And remember, I'm a total n00b with this stuff so... be gentle?
Nope the t has nf4, oh1 modems
hilla_killa said:
Nope the t has nf4, oh1 modems
Click to expand...
Click to collapse
Okay, so is there a way to flash in nf4/oh1 firmware without going back to full on stock? Feel like it kinda defeats the entire point of the project otherwise.
But again, I'm new to all this.
There is a stock rom for the DataDoneRight? If so I may give it a try, VM support asked me to do a PRL update and I can't so now I have no service at all.
Warning: There is NO working StockROM for the Data Done Right Virgin Mobile Triband using the OH1 baseband. If you flash any rom with any other modem, your doomed.
I luckily made a backup of my Tri-Band OH1 Modem for this rare phone. Here it is for anyone else that needs it:
http://d-h.st/O2Yo
Flashing Oct-L + This modem I managed to get rid of the "No Sim Card" error that occured when flashing other roms.
(Note: This will only get your 3G service back due to OcOS limitations, they do not have 4G LTE working on VMDDR)
However, I still can't get back to stock to execute data provisioning. Without it my phone can't make calls or get data. No PRL, No HiddenMenu.apk... so keep in mind if you sell that phone, or the number changes you are bricked just like me.
Epic Battle and Recovery of My Triband Phone (Required if changing phone numbers)
INCREDIBLE! :victory: The only words I have to describe my 3 week battle to recover my Virgin Mobile Data Done Right Tri-Band phone (THE CRAPPY ONE FROM WALMART). OK, if you need a PRL update and have to update "Profile" to get a new number - once again there are NO stock roms. Here's what worked for me... this is not for the faint of heart:
1) Have the d2refreshspr TWRP recovery from Oct-OS thread installed. You can flash it with heimdall.
Pro-Tip: You CANNOT flash a non-triband L710 rom from Hiemdall or Odin, so that's why we need recovery. People will say your phone has bad memory and junk, they're wrong. It fails with errors " ERROR: Failed to confirm end of file transfer sequence!" and "sw rev check fail fused 2 binary 1" respectively.
2) Wipe --> Advanced Wipe --> Check Dalvik Cache, System, Data, and Cache. Flash NDC modem for L710 Sprint. (This will completely break the SIM/modem! But allows you to boot 4.4.2 TouchWiz roms) For good measure, Reboot the recovery. (Do NOT attempt to install SuperSU if asked by TWRP, at this point as it seems to cause bootloops)
3) Flash TouchWiz based ROM: Conquest: Singularity 10 (beta 9) Full, choose Virgin Mobile as the carrier during install, and then flash the 10 (b10) Update. (Do NOT attempt to install SuperSU if asked by TWRP, at this point as it seems to cause bootloops)
4) Boot the phone it will take awhile, but it should come up. If it does, half of the battle is done.
5) Go through setup, connect to Wifi, and wait for everything to finish installing in the background.
6) Power off phone, your baseband is completely shot. Boot back into TWRP recovery.
7) Flash OH1 Modem, and then flash Universal_vmu_ApnFix-v.R2.zip
.
8) Reboot. If it boots, it's a miracle. Acknowledge all errors, there will be quite a few about failing apps that don't work with your OH1 modem.
9) Make sure Wifi is on and working, there will be no data to force an OTA otherwise since our modem is still not provisioned.
10) Go to Settings --> System Update --> Update PRL. If it works awesome! Do the same for "Update Profile".
Phone will reboot.
Done! Your L710TVPU0AOH1 should now have fixed baseband and data + phone number. Good Luck!!!
From here I plan to go back to OctOS and try a few other ROMS out. No one but @moonknightus 's amazing Conquest: Singularity could have saved this phone. All props go to the man and his team of rom helpers. :good:
Can I have a copy of the OH1 modem? The server where it is hosted is offline and I need it now as I hosed my Virgin Mobile Galaxy S3 Triband, installed another ROM without backing up my modem, I did a full nandroid through TWRP, but forgot to backup the modem through Partitions Backup and Restore.........
EDIT: Nevermind, I managed to resolve the issue alternatively. I downloaded the following Stock Image:
ALL_SPT_L710TVPU0ANF4_L710TSPT0ANF4_1683363_REV00_user_low_ship.tar.md5
Extracted the MODEM.bin file, then compressed it to MODEM.tar and through ODIN I flashed this file, the modem got flashed successfully, I flashed the Virgin Mobile APN fix, and voila! Modem works now.
I am stating this for others who managed to hose their Triband modem with non triband roms, there is another solution.
Sorry to beat a dead horse, I come from the nexus forums and haven't used a samsung device in a while. My friend has the Note 4 with MM on it. Is flashing TWRP as simple as just flashing it via odin with his phone as is? Does he need to complete any process first, before being able to flash TWRP via odin?
Thanks all!
Sprint Note 4 already updated to PD1? If latest update is desired, update it first.
FYI: An ounce of prevention is worth a pound of cure!
The bootloader is already unlocked but the reactivation lock may have been locked by user. Goto to Settings/Security/Reactivation lock and disable it. You can also verify this while in download mode, the phone's display show reactivation lock disabled before your proceed.
Enable developer options by tapping build number in About device in Settings 7 times. Go into developer tab and enable USB debugging.
Using latest Odin and latest TWRP is recommended. You should only flash only the specified custom recovery for your device or the touch screen will not be accurate.
TWRP can be found in the original development thread.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Use AP slot and make sure the Samsung driver is installed; get that from Samsung support for Note 4. Make sure KIES and SmartSwitch is closed or uninstalled (may not work on rooted phone; manually backup files you wish to keep just in case). Run Odin as administrator; not required for Windows 10.
To flash, press the Odin exe, uncheck the auto reboot option, load the file using the AP slot, power down phone, hold the keys [volume down, menu and power] together until booted in download initial screen, connect the USB, volume up, verify your COM is connected and start. When you see the success, 0 failed, disconnect USB and pull battery, wait at least 30 seconds and replace battery and boot directly into recovery to ensure it sticks. Otherwise, you're back on stock recovery.
If swapping device owner, it's recommended to remove the Google account before factory resetting the device. Consider it as a good practice for all Settings menu selected factory resets. If you trip the factory reset protection circuit, you need to sign in with original Google account & password.
You can use Odin to downgrade to Android Lollipop 5.1 (most recent OK1 build recommended if going back to Lollipop) but you cannot use Odin to downgrade to Android 5.0 Lollipop or KitKat. The bootloader prevents lower security bootloaders from being installed.
Custom ROMs may remove ItsOn but may not remove it from root folder. Unless /carrier/ItsOn folder is deleted, you may suffer continual reboots if factory resetting device at some point. After following and verifying all the above, you may consider factory resetting, including wiping data, internal memory and Android folder in extSdCard to make a clean break with normal un-rooted conditions and Lollipop fragments on phone to prevent random reboots.
Sent from my SM-N910P using Tapatalk
samep said:
Sprint Note 4 already updated to PD1? If latest update is desired, update it first.
FYI: An ounce of prevention is worth a pound of cure!
The bootloader is already unlocked but the reactivation lock may have been locked by user. Goto to Settings/Security/Reactivation lock and disable it. You can also verify this while in download mode, the phone's display show reactivation lock disabled before your proceed.
Enable developer options by tapping build number in About device in Settings 7 times. Go into developer tab and enable USB debugging.
Using latest Odin and latest TWRP is recommended. You should only flash only the specified custom recovery for your device or the touch screen will not be accurate.
TWRP can be found in the original development thread.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Use AP slot and make sure the Samsung driver is installed; get that from Samsung support for Note 4. Make sure KIES and SmartSwitch is closed or uninstalled (may not work on rooted phone; manually backup files you wish to keep just in case). Run Odin as administrator; not required for Windows 10.
To flash, press the Odin exe, uncheck the auto reboot option, load the file using the AP slot, power down phone, hold the keys [volume down, menu and power] together until booted in download initial screen, connect the USB, volume up, verify your COM is connected and start. When you see the success, 0 failed, disconnect USB and pull battery, wait at least 30 seconds and replace battery and boot directly into recovery to ensure it sticks. Otherwise, you're back on stock recovery.
If swapping device owner, it's recommended to remove the Google account before factory resetting the device. Consider it as a good practice for all Settings menu selected factory resets. If you trip the factory reset protection circuit, you need to sign in with original Google account & password.
You can use Odin to downgrade to Android Lollipop 5.1 (most recent OK1 build recommended if going back to Lollipop) but you cannot use Odin to downgrade to Android 5.0 Lollipop or KitKat. The bootloader prevents lower security bootloaders from being installed.
Custom ROMs may remove ItsOn but may not remove it from root folder. Unless /carrier/ItsOn folder is deleted, you may suffer continual reboots if factory resetting device at some point. After following and verifying all the above, you may consider factory resetting, including wiping data, internal memory and Android folder in extSdCard to make a clean break with normal un-rooted conditions and Lollipop fragments on phone to prevent random reboots.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks bud. This was really great!
hate to be a stickler, but im a frickin nub.... after doing this how do i get root access?? pls help im new i just paid 10$ FOR A NOTE 4 , mint condition hahah but for real someone help..
CorporalCactus said:
hate to be a stickler, but im a frickin nub.... after doing this how do i get root access?? pls help im new i just paid 10$ FOR A NOTE 4 , mint condition hahah but for real someone help..
Click to expand...
Click to collapse
To get root after getting on desired update, whether it be current update, downgrading (be careful with downgrading; most likely you're only able to downgrade as low as Android 5.1 but that depends on your current bootloader) or upgrading, you flash TWRP and then you would do one of two things:
1) flash a pre-rooted ROM. Custom ROMs in our forum do this.
2) flash custom kernel and complete root with SuperSU zip. Both are flashed in recovery but both should be flashed before booting. Kernel first, then flash SuperSU zip and boot. You would also need to manually remove ItsOn and Knox.
Given the complexity of it, I'd suggest the custom stock ROM for you. The ROM should match your bootloader. I'd recommend stock, aka touchwiz ROMs. They're mostly stock and have less bugs and workarounds than others like CM.
We still don't have highly customized Marshmallow stockish ROMs but I don't think it will be long before we see them. By the time they're here, maybe you're ready.
Read the OP of the custom ROM. If you don't understand or need clarification, this thread is a good place to ask the question. Install this app to check your bootloader (baseband is relevant too):
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hint: make sure you're on the the recommended bootloader and baseband first. If you have trouble with TWRP flash sticking, you may not be unchecking auto reboot and pulling battery after successful flash and booting directly into recovery to make it stick properly. You have to wait at least 30 seconds after battery pull and boot directly into recovery.
Sent from my SM-N910P using Tapatalk
samep said:
To get root after getting on desired update, whether it be current update, downgrading (be careful with downgrading; most likely you're only able to downgrade as low as Android 5.1 but that depends on your current bootloader) or upgrading, you flash TWRP and then you would do one of two things:
1) flash a pre-rooted ROM. Custom ROMs in our forum do this.
2) flash custom kernel and complete root with SuperSU zip. Both are flashed in recovery but both should be flashed before booting. Kernel first, then flash SuperSU zip and boot. You would also need to manually remove ItsOn and Knox.
Given the complexity of it, I'd suggest the custom stock ROM for you. The ROM should match your bootloader. I'd recommend stock, aka touchwiz ROMs. They're mostly stock and have less bugs and workarounds than others like CM.
We still don't have highly customized Marshmallow stockish ROMs but I don't think it will be long before we see them. By the time they're here, maybe you're ready.
Read the OP of the custom ROM. If you don't understand or need clarification, this thread is a good place to ask the question. Install this app to check your bootloader (baseband is relevant too):
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hint: make sure you're on the the recommended bootloader and baseband first. If you have trouble with TWRP flash sticking, you may not be unchecking auto reboot and pulling battery after successful flash and booting directly into recovery to make it stick properly. You have to wait at least 30 seconds after battery pull and boot directly into recovery.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
damn thanks for this info! youre the man! you know ur stuff thats awesome. im confused regarding the kernel.. i just winged it tbh, i installed TWRP via odin. got it to stick, then flashed SUPERSU and got root. I made a full backup via twrp then i flashed a custom CM rom and it works awesome. i didnt do anything regarding kernels. My question now is, what is the easiest way to swap between roms?? Such as stock Rom to this New CM rom i have. Would i just create backups and restore when i want to switch??
CorporalCactus said:
damn thanks for this info! youre the man! you know ur stuff thats awesome. im confused regarding the kernel.. i just winged it tbh, i installed TWRP via odin. got it to stick, then flashed SUPERSU and got root. I made a full backup via twrp then i flashed a custom CM rom and it works awesome. i didnt do anything regarding kernels. My question now is, what is the easiest way to swap between roms?? Such as stock Rom to this New CM rom i have. Would i just create backups and restore when i want to switch??
Click to expand...
Click to collapse
You could make backups and factory reset before restoring. If you have issues restoring stock backups, wipe internal memory also.
You have to take care to read and adhere to changing trends with CM; they may not be compatible with Marshmallow baseband and bootloader yet but may even require a different kernel to run with Marshmallow bootloader and baseband. I'm not current on the latest and lack experience. Search the specific ROM threads for CM known issues, workarounds and trends.
As far as the kernel question, I did omit the fact you could flash SuperSU to patch the stock kernel; you didn't do any wrong there. I've abandoned use of stock kernel since Android 5.1 required an exploit to root. We didn't always have the boot image patch that SuperSU now includes. For some reason, users are randomly losing root with systemless root. If that happens, just flash SuperSU again; same version or higher should be OK.
Sent from my SM-N910P using Tapatalk
samep said:
You could make backups and factory reset before restoring. If you have issues restoring stock backups, wipe internal memory also.
You have to take care to read and adhere to changing trends with CM; they may not be compatible with Marshmallow baseband and bootloader yet but may even require a different kernel to run with Marshmallow bootloader and baseband. I'm not current on the latest and lack experience. Search the specific ROM threads for CM known issues, workarounds and trends.
As far as the kernel question, I did omit the fact you could flash SuperSU to patch the stock kernel; you didn't do any wrong there. I've abandoned use of stock kernel since Android 5.1 required an exploit to root. We didn't always have the boot image patch that SuperSU now includes. For some reason, users are randomly losing root with systemless root. If that happens, just flash SuperSU again; same version or higher should be OK.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
CorporalCactus said:
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
Click to expand...
Click to collapse
Did you factory reset and wipe internal memory when restoring the backup?
Put your micro sdcard in a card reader and transfer it. If you're trying to transfer while in recovery, that currently doesn't work.
If you're trying to copy your TWRP backup to micro sdcard, the path should be: TWRP/BACKUPS/(your device s/n recognized by TWRP)/(TWRP Backup folder)
Without proper path, TWRP may not see the backup as official. When saving TWRP backups, the TWRP folder as a whole with desired backups should be saved.
If you can't restore the backup, you can flash a ROM that matches bootloader. Like I said before, factory reset and wipe internal memory and flash the ROM.
Sent from my SM-N910P using Tapatalk
CorporalCactus said:
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
Click to expand...
Click to collapse
At this point I would just recommend flashing a new ROM man.
Sent from my SM-N910P using Tapatalk