Develop Bugs

[Q] Factory reset in CM12 now stuck in recovery boot loop

So I'm just getting into the whole ROM thing and I'm pretty sure I've messed up here. I encountered a problem after installing CyanogenMod 12 Unofficial (trltespr NIGHTLY) where I could receive text messages but not send them. I could still load pages and apps over lte and call people but I couldnt send messages. I gave up with the idea of finding a solution after browsing forums and decided to preform a factory reset through settings. The phone was rooted but not after I installed the rom. after rebooting it went into recovery mode and began to loop showing the Team Win screen then going black only to do it again. I removed the battery and booted the phone into download mode and it is now sitting here connected to my computer with Odin up ready for whatever it is that I need to do to fix it. I have absolutely no idea what to do. Help is very much appreciated.

diehlkj said:
I removed the battery and booted the phone into download mode and it is now sitting here connected to my computer with Odin up ready for whatever it is that I need to do to fix it. I have absolutely no idea what to do. Help is very much appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867
Go there and download the BOB7.tar and flash that.

xxSTARBUCKSxx said:
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867
Go there and download the BOB7.tar and flash that.
Click to expand...
Click to collapse
I went and followed the instructions and odin said it failed due to auth. Any other ideas?

diehlkj said:
I went and followed the instructions and odin said it failed due to auth. Any other ideas?
Click to expand...
Click to collapse
A couple but i dont think i can throw my laptop that far.
Youre an OE1 victim and Good Luck in your endeavors until a .tar comes out.
Search The Q&A threads pertaining to OE1 and see if you can manage to come out with a successful gathering of info and get back your phone.

xxSTARBUCKSxx said:
A couple but i dont think i can throw my laptop that far.
Youre an OE1 victim and Good Luck in your endeavors until a .tar comes out.
Search The Q&A threads pertaining to OE1 and see if you can manage to come out with a successful gathering of info and get back your phone.
Click to expand...
Click to collapse
Is there any way I can remove or reinstall/repair TWRP so i can properly wipe the system or just get another rom working?

Solved
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP

diehlkj said:
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP
Click to expand...
Click to collapse
Then you can flash notarize rom per that threads first post... Until an updated tar that will work in Odin.
http://forum.xda-developers.com/showthread.php?p=60506568

diehlkj said:
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP
Click to expand...
Click to collapse
Yep, the trend seems to be pointing to CF Auto Root after trying to flash stock tar over OE1 build. Although I'm thinking the stock recovery is from way back unless CF updates his build.
About the text sending issue, did you apply the fix found in link below? Check under the spoiler.
http://forum.xda-developers.com/showthread.php?p=57613217
If you want to get back to TW, Noterized is a good OP option. (As mentioned above)
Sent from my SM-N910P using Tapatalk

*Help* I unrooted on a rom and now I can't root my phone.

Device: LG G3
Rom: [AOSP EXTENDED V3.0] [LG G3 - D855] [OFFICIAL] [NOUGAT R9] [by MARCHETTO96]
Hey again,
So i'm running this rom right and I was reinstalling my apps onto my phone and one app I need to log into but it noticed it was running root (Snapchat). So I followed someones advice on here on XDA to fully unroot the device and I did that I fully unrooted the app from the phone and then here comes the worst part that I realized this will kick me out of recovery and i wont be able to get back in because I need to get on to recovery to re install superSU back on. So im stranded on nougat 7.1 and dont have access to root at all except for root access on developer settings but that doesn't nothing at all I re installed the app on play store but its telling me the phone is unrooted of course.
Anyone can help me out here. It would be greatly appreciated .
P.S I did get snapchat working after that method kinda did work/backfire at the same time.

Do you have nandroid backup? If yes, flash that. It will be all well.
Other hard method is to downgrade to KitKat and then root and then TWRP. ?

I do not have a back up for this ROM but I have other back ups on my phone that still works. I can't do it as well cause I neeed root to l get it to work.

HunterTubeHD said:
I do not have a back up for this ROM but I have other back ups on my phone that still works. I can't do it as well cause I neeed root to l get it to work.
Click to expand...
Click to collapse
Backups don't need root. They need TWRP to be flashed.

Jahanzaibawan said:
Backups don't need root. They need TWRP to be flashed.
Click to expand...
Click to collapse
Yeah thats the only thing I can't get access to TWRP. When I fully unrooted It would not let me in my recovery at all just bootloops until i take the battery out then it reboots to the system fine.

Just going to ask a hopefully obvious question that I know doesn't help but I'm intrigued... Why didn't you just unroot using the supersu app?

pffcouk said:
Just going to ask a hopefully obvious question that I know doesn't help but I'm intrigued... Why didn't you just unroot using the supersu app?
Click to expand...
Click to collapse
I did do that....now my main problem is I don't have root anymore and I can't get access to my recovery and plus I'm running an Nougat rom so I need to find a way to re-root my phone again to get it all back.

The supersu app doesn't delete the recovery on your phone so something had to have gone wrong. Either way the best bet for you I would imagine anyway would be to follow a guide to install recovery - it's been that long since I had to do it I can't be of much help but I'm willing to look into the easiest options for you if you want. There will be a way, pretty much guaranteed

pffcouk said:
The supersu app doesn't delete the recovery on your phone so something had to have gone wrong. Either way the best bet for you I would imagine anyway would be to follow a guide to install recovery - it's been that long since I had to do it I can't be of much help but I'm willing to look into the easiest options for you if you want. There will be a way, pretty much guaranteed
Click to expand...
Click to collapse
I know that my recovery is still there but It wont allow me on there for some reason. But im thinking that If I factory reset the phone it would PROBABLY fix the problem but theres one risk that it could probably happen and im guessing that it will go straight into a bootloop. If you want to help me It would be great

I'll research for you mate!

Did you modify your ro.product.model in build.prop file and when supersu app asks if you want to flash stock recovery you pressed yes?
For example if you have enabled google assistant by changing your ro.product.model to pixel or pixel xl and after that unrooted and pressed yes to restore stock recovery (to get OTA to work), supersu flashes pixel recovery and thats why you can't get to recovey again.
There are ways to get your phone back to factory clean and start over.

Okay I have spent a whole day figuring out this problem but i finally managed to fix it.
So I went onto download mode
opened up LG Flash Tool 2014
Flashed an LG KDZ File managed to work after the 2nd time
10 or 15 mins later it finally worked
LG started to boot up and started loading in the apps
THEN
I rooted the phone again using this forum: https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268
Then I finally got back onto the glorious TWRP rom.
I re-installed the ASOP rom again.

I'd Like to thank Juhkimo, Jahanzaibawan and pffcouk for helping me out. You guys got my phone back to what it was before so thanks a ton

HunterTubeHD said:
I'd Like to thank Juhkimo, Jahanzaibawan and pffcouk for helping me out. You guys got my phone back to what it was before so thanks a ton
Click to expand...
Click to collapse
Really good to hear that :highfive:

Updated Magisk Manager - NOW BRICKED?!

Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:

dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504

timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt

The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.

dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk

dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.

kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.

Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:

dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img

This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img

timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?

WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?

@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy

timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!

@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT

Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?

@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up

Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.

adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs

N910P - Please Help - Tried to root and failed No Bootloader found?

I'm really hoping someone can bail me out here before I...
I have made a mess of my new (to me) Note 4. I bought it as an Unlocked GSM. It arrived booting with a Sprint screen. I have Safelink BYOP service. When I switched from my Note2 to Note4, yesterday, an ATnT sim card was used to activate it with Tracfone. Everything seemed to work EXCEPT for MMS - I could not send nor receive pictures. I read -what I thought was- clear instructions here on the forum, I started downloading and attempting to root my phone, hoping that would solve the problem, since tech support had no answers.
I followed the instructions in this post - https://forum.xda-developers.com/note-4-sprint/help/rooting-sprint-note-4-pj1-t3495306 . Now the phone will only boot to download mode, or I can use the up volume button to get to the program to install, restore, etc. I have tried several times - with a couple of different .tar files. This last attempt - I tried to restore it - that also failed. My old eyes can not really see the tiny text but I did see in Odin3 that 1) No MDS found 2) Systemless mode Boot img support required 3) Boot Image Patcher Failed. When I attempt to install the SuperSU, from the thread, it gives me similar errors 1) NO MDS file found 2) (under Boot Image patcher it says FAILURE / Abort after extracting Ramdisk.
If anyone could help me out, I would be most grateful.

JadenEllis said:
I'm really hoping someone can bail me out here before I...
Click to expand...
Click to collapse
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!

Once you get phone back on stock. I'll show how to root!

Thank You
Thank you so much for the reply. I have downloaded the files you put in my post. I will attempt to do these things now, but I have a question. I stayed up fighting with the phone all night. I probably did some things I shouldn't have? I realized that I was getting stupid and quit, but I did (maybe) put some other stuff on the phone that night. Should I use the Clean or wipe function in TWRP before I do anything else???
Yes, I can boot to downloader or to TWRP. The phone (on its own) is now stuck trying to load with the Note 4 splash screen - but I can boot to either with the vol +/- buttons.

SamFirm did not work. It said Unable to fetch... please check data or enter manually.
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

First - THANK YOU all for the assistance.
Yesterday, none of the suggestions were working, but I kept at it. I was finally able to install the most current Stock tar that I could find. This phone had updated to the most current version available for the phone - it had Marshmallow 6.01. NOW, the red and yellow tamper errors appear to be gone from the Note4 splash screen - BUT, it boots to Sprint Activation so it won't fully load to OS. I read a post about removing the Sprint Hands Free Activation, but it gives two ways of doing so. 1 requires having a rooted phone (I am assuming it is not rooted now?) and the other uses ADN Connect, and I am not sure what that is.
I'm not really sure what to do from here? Any assistance appreciated. Can I start from step 1 of the original post to install SuperSU now?
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

Well, the sun is about to come up - again - but I think I got it! This has been a learning experience to say the least. I wasn't really planning a crash course in Android, but thank you to all who responded. And to :Samep too!

I think I get it
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.

JadenEllis said:
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
Click to expand...
Click to collapse
Sorry bud. I'm so busy. Haven't been online since i message you. Glad you got it.

Rookie messed up..
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.

meBn360 said:
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
Click to expand...
Click to collapse
Sorry I don't get on here much lately. Just seen your post.
Without knowing exactly what you did. I'd say you lost your unlock. If you had an unlocked sprint phone. And tried nougat. I believe i remember that upgrading to nougat was messing up people's EFS partition. And that's where the unlock happens. Did you make a backup?
I always tell everyone, the most important thing you can do is have a full working backup of every partition.
Hope that sheds some light

Samsung j2 Prime (sm-g532m) - how do I get LineageOS on this device?

I'm not completely brand new to flashing with custom roms, but I sometimes go 2-3 years running stock, so when I do come back I have forgotten everything and it feels like starting over.
So far I have achieved the following:
1 - backed up device
2 - reset device back to stock
3 - flashed stock image using Heimdall
Unfortunately after all that I am not sure if I have made any progress. It just took my phone back to factory settings.. My storage is full, my SDCard is empty and I can't push a file to the sdcard because I don't know how to reference the right path.
I tried flashing a TWRP recovery.img file to the recovery partition, and it indicated success. But when I boot into recovery it looks exactly like it did before. I get no TWRP gui interface. The TWRP app has no official build for this device, so is unusable. I also tried installing Magisk but got errors and just uninstalled it.
Frankly I don't know what to do yet. I'm not sure the device is officially 'rooted' or not. I'm not sure what to do next. Do I flash an Enigma Android 6 image? Do I have to do that before I can update to Android 9?

dixonge said:
I'm not completely brand new to flashing with custom roms,.........
Click to expand...
Click to collapse
I don't have this device but, your best bet is to take a look at the following TWRP thread that's specific to your device and variants. Don't be afraid to ask for some member guidance as well.
https://forum.xda-developers.com/showthread.php?t=3616589
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.

Ibuprophen said:
I don't have this device but, your best bet is to take a look at the following TWRP thread that's specific to your device and variants. Don't be afraid to ask for some member guidance as well.
https://forum.xda-developers.com/showthread.php?t=3616589
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.
Click to expand...
Click to collapse
Yes, that's where I got my twrp recovery.img file from. I'll go back through those steps and ask in the thread if I have further issues. Thanks.

Typically there is a reboot into system after flashing twrp. Some stock ROM replace twrp with stock recovery in that case.
Known workarounds:
Flash twrp to boot partition also
Remove battery after flashing twrp
Use windows Odin and unchecked reboot
Do some key tricks to force recovery during reboot.
Once twrp booted, it normally does tricks to not get overwritten.

Asgard holds your answer
dixonge said:
I'm not completely brand new to flashing with custom roms, but I sometimes go 2-3 years running stock, so when I do come back I have forgotten everything and it feels like starting over.
So far I have achieved the following:
1 - backed up device
2 - reset device back to stock
3 - flashed stock image using Heimdall
Unfortunately after all that I am not sure if I have made any progress. It just took my phone back to factory settings.. My storage is full, my SDCard is empty and I can't push a file to the sdcard because I don't know how to reference the right path.
I tried flashing a TWRP recovery.img file to the recovery partition, and it indicated success. But when I boot into recovery it looks exactly like it did before. I get no TWRP gui interface. The TWRP app has no official build for this device, so is unusable. I also tried installing Magisk but got errors and just uninstalled it.
Frankly I don't know what to do yet. I'm not sure the device is officially 'rooted' or not. I'm not sure what to do next. Do I flash an Enigma Android 6 image? Do I have to do that before I can update to Android 9?
Click to expand...
Click to collapse
OK, bad jokes about Nordic deities aside. Try using ODIN rather than Heimdall to flash TWRP. In ODIN, make sure the automatic reboot on exit feature is turned OFF. After exiting ODIN, MANUALLY reboot the thing into recovery mode using whatever multiple button combination is required, and you "should" find it starting up TWRP for you. ASSUMING that is so, then power off the device and re-start it. it "should" now be working correctly, meaning with whatever ROM you have in place and TWRP as the recovery. And if THAT worked, you can flash SU using TWRP if you are not already rooted and you are good to go. Good Luck.

I now have managed to finally get TWRP flashed. It worked this time. Could not begin to tell you what I did differently...
I managed to flash the custom ROM and am now dealing with two remaining issues - a password I am being asked for that I never set, and getting the right version of opengapps flashed.

nezlek said:
OK, bad jokes about Nordic deities aside. Try using ODIN rather than Heimdall to flash TWRP. In ODIN, make sure the automatic reboot on exit feature is turned OFF. After exiting ODIN, MANUALLY reboot the thing into recovery mode using whatever multiple button combination is required, and you "should" find it starting up TWRP for you. ASSUMING that is so, then power off the device and re-start it. it "should" now be working correctly, meaning with whatever ROM you have in place and TWRP as the recovery. And if THAT worked, you can flash SU using TWRP if you are not already rooted and you are good to go. Good Luck.
Click to expand...
Click to collapse
FYI - the only version of Odin I could find for Linux is a glitchy Java version. All the tutorials say to put things in the 'AP Slot' - and I can clearly see that in screenshots. But my version didn't have an AP slot. The graphics were misaligned and I finally gave up. I did manage to flash a ROM using ADB sideload. So there's that.

ODIN for Linux ....
dixonge said:
FYI - the only version of Odin I could find for Linux is a glitchy Java version. All the tutorials say to put things in the 'AP Slot' - and I can clearly see that in screenshots. But my version didn't have an AP slot. The graphics were misaligned and I finally gave up. I did manage to flash a ROM using ADB sideload. So there's that.
Click to expand...
Click to collapse
Yeah, Odin can be more than a little bit "glitchy" on Linux boxes. Surprised you found one that worked at all, to be totally candid. I suggest to folks that they just beg, borrow, or steal 15 minutes on a Windows box and do it the easy way. Yes, I know "windows" is a very long "four letter word" in many circles, but sometimes you just bite the bullet and take the path of least resistance. The IMPORTANT question is: is your problem solved ??

nezlek said:
Yeah, Odin can be more than a little bit "glitchy" on Linux boxes. Surprised you found one that worked at all, to be totally candid. I suggest to folks that they just beg, borrow, or steal 15 minutes on a Windows box and do it the easy way. Yes, I know "windows" is a very long "four letter word" in many circles, but sometimes you just bite the bullet and take the path of least resistance. The IMPORTANT question is: is your problem solved ??
Click to expand...
Click to collapse
Good question. Do I have LineageOS on my device? Yes.
Is it a usable version? Uh, no. My device is now reporting to be a Galaxy J7 and the WiFi is useless. This was from an Enigma ROM. So at least I have managed to figure out how to flash the device and TWRP recovery is working. Now to find a better ROM.
I guess the question I have now is this: *IS THERE* an actual, working Android 9 PIE ROM for the J2 Prime (Grand Prime+) model?

dixonge said:
Good question. Do I have LineageOS on my device? Yes.
Is it a usable version? Uh, no. My device is now reporting to be a Galaxy J7 and the WiFi is useless. This was from an Enigma ROM. So at least I have managed to figure out how to flash the device and TWRP recovery is working. Now to find a better ROM.
I guess the question I have now is this: *IS THERE* an actual, working Android 9 PIE ROM for the J2 Prime (Grand Prime+) model?
Click to expand...
Click to collapse
Hui. Quick search in XDA shows: there is probably no aosp based ROM for your device. So you flashed a ROM for a different device? You should learn a bit about model names and codenames. And be glad to not have bricked your phone.

kurtn said:
Hui. Quick search in XDA shows: there is probably no aosp based ROM for your device. So you flashed a ROM for a different device? You should learn a bit about model names and codenames. And be glad to not have bricked your phone.
Click to expand...
Click to collapse
Well, it's from here on XDA, and it was advertised as being ported for my model specifically. Just surprised to see the other model info in 'About' - I agree that Pie seems to be non-existent for this phone. What about Oreo? So far every single article I find on the 'net is just click-bait.

Sometimes it is better to stay on stock ROM. With twrp you can install magisk or xposed or nanodroid.