Develop Bugs

[ROM][STOCK][FROYO] EC03 Froyo Update

Here is the update that everyone has been waiting for At the moment, I'm only providing the modem, and rooted, stock, deodexed version of the ROM. There will be a cleaned up version to go along with all of this in due time, but we're currently working out some problems with it. I would like to note that despite this being the Froyo update, it is not without its own set of problems, and odds are you may never see another update outside of this from anywhere. However, the benefits of getting Froyo will outweigh the problems with it for most people, so have at it.
You will need a few things to get this, first, the downloads list here will be needed (obviously). You'll also need to have CWM setup and know how to use Odin. Heimdall will also work for those of you not on Windows, but I'm not providing any instructions for flashing using Heimdall. Also note that you will want to wipe data or perform a factory reset before booting into Froyo to avoid any problems. While you may get away with not doing it, you could end up with several problems, so my recommendation is to wipe data. Also, you can flash the ROM first, or flash the modem first, which ever you want to do. There isn't really a required order for it, as long as you do both parts.
[size=+1]Instructions[/size]
Download everything you need.
Odin
Froyo Radio
ROM+Kernel
CWM Kernel
CWM update.zip
Put the ROM zip and CWM update.zip on your SD Card
Flash the Radio via Odin in the PDA box
Enter CWM and flash the ROM+Kernel
Wipe Data in CWM before restarting your phone
Restart and enjoy Froyo
[size=+1]Downloads[/size]
Modem
ROM+Kernel

FAQ
How can I donate to you for this?
You can either click the "Donate to me" button above my avatar, or go through this link. Don't feel obligated to donate though, as Verizon should have given this to you (the users) long ago.
Can I still receive updates after flashing this?
You cannot receive updates after flashing this unless you revert back to DL17, which is the latest official software released by Verizon and Samsung.
If I can receive updates on this, how can I restore back to DL17?
I've been sending this to several people already that have had problems with their phones. If you need to revert back to DL17 for any reason, download this. You will need 7-zip or similar to extract it. Once you have the .tar.md5 file, flash it in Odin via PDA like you did for flashing the modem to get Froyo.
Can I return my phone to Verizon for warranty repair/service with this on my phone?
No. If you need any sort of help with your phone from Verizon, you will need to have the stock DL17 ROM on your phone. Anything else and you have voided your warranty and Verizon and/or Samsung will not have to do anything to help you. See the above question for a package to restore your phone to the latest stock software.
Are there any bugs in this release?
Yes there are, just as there is with any software. I do not know what the bugs are though off hand though as I have not been using this update. I also cannot say whether any of the problems you may have will ever get fixed, seeing as you can't even get a straight answer on why the update has been taking so long.
Is xxx modification/theme compatible with this?
Odds are that it isn't. All of the current themes and modifications for DL17 will not work on this package. They will all need to be updated to be able to work. Given that this is a relatively new release, this could take some time, especially given that it is the summer and people are on vacation (I'm looking at you trailblazer ). We will work though to try and get all of the mods ported from DL17 to EC03 so that you don't have to give up anything to upgrade.
Will you release a "clean ROM" based on this?
Yes, and it is already in progress. I have sent it out to a couple people already to ask for feedback and any issues. Once they say it is ok, I'll create a new thread with the cleaned up version. There is currently no ETA on when it will be released though.
Are there any other kernels I can use with this besides the one that comes with it?
At the moment, there isn't. I'm trying to get a custom kernel to work, but it has some problems. At the very least, we can customize the stock kernel some, but I do not know if a full source built kernel will ever be available.
Can I flash this if I am on the voodoo kernel?
No, if you are running the voodoo lagfix kernel, you will want to disable voodoo prior to doing anything. If you don't, you'll be in for some fun times with Odin getting your phone back in a usable state.
Can I get something included in the FAQ?
Yes you can. Just create a post with the following template, and I'll try to keep the FAQ updated. If I don't see it or add it right away, don't worry, I'll try and update it. If it has been a week or two and I still haven't responded, just send me a message with a link to what you want included. Here is the format to use:
Code:
[PLAIN][b]Question goes here?[/b][/PLAIN]
Answer goes here.

I'm getting ready to download it

When I go to flash the radio, Odin says it's an invalid image type

circa881 said:
When I go to flash the radio, Odin says it's an invalid image type
Click to expand...
Click to collapse
It should work You aren't extracting or renaming it at all are you?

Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt

circa881 said:
Nope, not at all. I even downloaded it again just to make sure the first file wasn't corrupt
Click to expand...
Click to collapse
Your phone is in download mode when you're attempting to flash via Odin?

XD Now I feel like a ruh-tard. I forgot about that part

Wait, it's still saying invalid image type

I'm in shock... I'm on this forum every day and I missed this?! I'm going to install this and mess around with it. Ill post any bugs I find later this evening..
Kudos @imnuts for the effort!

Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?

jaizero said:
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
Does it really matter?

No... No it doesnt.. Its working perfectly by the way.. But Im sure you already knew that lol..

If jaizero got it to work, why couldn't I?
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God

jaizero said:
Took about 7 minutes from download to phone setup. There was a short hang at the Samsung screen (approx. 15 seconds) but other than that it looks like it should. All startup animations are in tact..
I just gotta ask, its killing me... Where did this come from?
Click to expand...
Click to collapse
It came from heaven!!!
Sent from my Mind

^ lolololol
Sent from my SCH-I400 using XDA Premium App

FROYO
i think i love you (no homo)

I successfully loaded the ROM.
It hang a bit longer than usual on the verizon logo but after that no issues.
Thanks imnuts and anyone else that worked to make this possible.

Kay, how are people getting this to work when I couldn't get the radio flashed
Sent from my SCH-I400 using XDA Premium App
---------------------------------
Jill plays tricks, Jack plays God

Ok I dl'd both files, I have Odin1.3 both blue n yellow CWM update.zip but what is CWM kernal?
P.S. I totally love you guys and many thanks to nuts for confirming my faith in opensource and saving my phone
Sent from my SCH-I400 using XDA Premium App

[Solved] Status 7 Error

I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.

Dantenios said:
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Click to expand...
Click to collapse
You will need to update to the latest bootloader (which is different from modem).
If you're on T-Mobile, you'll want UVDMD5: http://forum.xda-developers.com/showthread.php?t=2282603
If you're on WindMobile (or SGH-T999V), you'll want VLDLL1: http://forum.xda-developers.com/showthread.php?t=1949687 (you'll have to ODIN)

re: error 7 - odin flash
Dantenios said:
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Click to expand...
Click to collapse
This guide will get your phone back up and running properly, doing anything else will just prolong your problem.
Easy and sure way to fix error 7 and other issues or problems - Here is the step by step guide:
After doing this you will end up with a stock-pre-rooted T999 Tmobile Touchwiz 4.1.2 rom which works properly.
You will not loose any of your pictures, videos or music by doing this.
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!

to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.

re: jellybeans
Dantenios said:
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
Click to expand...
Click to collapse
I never said you should be running JB Touchwiz roms, all I was trying to explain is the best and easiest way to get
your phone back up and running whichever way you like it to run.
If you follow the step by step instructions and the phone is working normally then you can re-flash whichever rom
CM10.1 or any others without any issues unless their is something wrong with the rom you are trying to flash.
The main thing is that it's best to start fresh when someone is having issues like you are having with your phone.
Doing anything else besides what I suggested will only prolong all those issues you are having now.
People will be telling you that your cwm or twrp recovery is not the latest one and you need to update it,
other people will tell you that you must have had some error downloading the cm10.1 rom and they will
tell you to re-download it, then others will tell you to check the MD5 checksum of the download and all
kinds of other things which will just prolong the problems you are having.
None of those things I just wrote will help you to fix the error 7 and other issues you are having.
That's why I posted the step by step which works each and every time to fix errors such as yours and
give you or anyone else a clean and fresh start.
Good luck!

*please ignore*

re: you are right
GenericAsianGuy said:
You need to ODIN the latest TouchWiz JB in order to update all the inner-parts of your phone.
I did this yesterday:
ODIN to the latest pre-rooted firmware (DLL1 in my case (SGH-T999V), MD5 for SGH-T999)
Let it boot into TouchWiz
Install Android Terminal Emulator and the latest ClockworkModRecovery
Boot into Recovery
Factory Reset
Install the latest CM 10.1 Nightly
Reboot
Profit (and spend a few hours re-installing and re-configuring everything again).
Click to expand...
Click to collapse
U R so right! I could not have said it better!
---------- Post added 19th May 2013 at 12:00 AM ---------- Previous post was 18th May 2013 at 11:18 PM ----------
Dantenios said:
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
Click to expand...
Click to collapse
I forgot to mention, since you are kind of new to this you should not even think of or mention anything
about bootloaders if don't want to end up with a shiny brick.
This has happened hundreds of times in these XDA forums when people mess around with bootloaders.
Flashing bootloaders intentionally or by trial and error is the number one way to end up with a bricked phone.

Alright, I understand now, thank you. Just curious, this will probably trip the flash counter right? Or does following that method allow to reset the flash counter? Or is that just something i need to worry about if i'm going to send the phone in for repairs (which i hope I wouldn't need to)

re: flash counter
Dantenios said:
Alright, I understand now, thank you. Just curious, this will probably trip the flash counter right? Or does following that method allow to reset the flash counter? Or is that just something i need to worry about if i'm going to send the phone in for repairs (which i hope I wouldn't need to)
Click to expand...
Click to collapse
The odin flash to stock rooted will trip the flash counter, but then each time you flash any rom trips the flash counter too.
You can get the "Triangle away" app to reset the flash counter at the play store.
Actually there is no need to reset the flash counter at all unless you need to
exchange a defective phone which is still under warranty.
Good luck!

Apologies but one more thing, your post was a link to a pre-rooted JB for T999, My phone is the T999V, if you'd happen to have the pre-rooted version for that would be greatly appreciated.

Dantenios said:
Apologies but one more thing, your post was a link to a pre-rooted JB for T999, My phone is the T999V, if you'd happen to have the pre-rooted version for that would be greatly appreciated.
Click to expand...
Click to collapse
All of these roms are stock pre-rooted roms, I am not certain which one is for your
T999v phone. Perhaps the "V" stands for videotron so select that one.
Mobililicity_VLDLL1
Updated JB Firmware
Mobililicity_VLALH2
Updated ICS Firmware
Wind_VLDLL1
Updated JB Firmware
Wind_VLALH2
Updated ICS Firmware
Videotron_VLDLL1
Updated JB Firmware
Videotron_VLALH2
Updated ICS Firmwar

Misterjunky said:
Mobililicity_VLDLL1
Updated JB Firmware
Wind_VLDLL1
Updated JB Firmware
Videotron_VLDLL1
Updated JB Firmware
Click to expand...
Click to collapse
Great post Misterjunky!
One of these; it depends on what carrier you're with.

I just finished using Odin to the Mobilicity VDLL1 with the pre-rooted JB. Just waiting on my phone to boot up. I have the tab open to install CWM Touch via the terminal emulator. After that I can install the latest CM 10.1 update correct?

re Ok
Dantenios said:
I just finished using Odin to the Mobilicity VDLL1 with the pre-rooted JB. Just waiting on my phone to boot up. I have the tab open to install CWM Touch via the terminal emulator. After that I can install the latest CM 10.1 update correct?
Click to expand...
Click to collapse
Yes, once odin is done and you flash custom recovery the phone will be ready to be flashed any compatible cwm/twrp custom rom zipfile.
You would be much better off if you go to the playstore and download "Goomanager" which is a free app.
After its installed, open it and press the menu key and select "installopenrecoveryscript".
Doing that will flash the latest TWRP recovery.
When Goomanager is done flashing, reboot the phone into recovery mode and go from there.
TWRP has a built-in file manager and terminal, plus an option for ADB sideloading.
It has all the options which CWM has and more.
Give it a try, you can always flash the cwm back if you like.

Sure, though i'm having a new issue now haha My phone has been stuck on the Samsung loading screen ever since after Odin said pass. How long does this usually take, right now for me it's been almost half an hour...And i know i followed the instructions to the T

re: reboot
Dantenios said:
Sure, though i'm having a new issue now haha My phone has been stuck on the Samsung loading screen ever since after Odin said pass. How long does this usually take, right now for me it's been almost half an hour...And i know i followed the instructions to the T
Click to expand...
Click to collapse
reboot the phone into recovery and do a "Factory reset" then restart the phone.
Chances are excellent that it will boot normally if you flashed the correct rom.
Don't wipe anything in recovery.
Good luck!

Thanks a Bunch, It worked! Now to install the recovery, then i may try using Touchwiz JB for a bit, but to be honest, I still think i like CM 10.1 better haha this one feels..some what clunky to me.

Dantenios said:
Thanks a Bunch, It worked! Now to install the recovery, then i may try using Touchwiz JB for a bit, but to be honest, I still think i like CM 10.1 better haha this one feels..some what clunky to me.
Click to expand...
Click to collapse
It would probably be best to edit your title with SOLVED in italics or something so other users are aware and can revert to this thread for assistance rather than starting up a whole new one
Sent from my SGH-T999 using xda premium

Done. I just wanted to ask, I installed the latest CM 10.1 update, and wondering, when i facotry reset it, it didn't take me through the welcome procudure and under my Mobile network options, i didn't see any LTE options, just EvDO and Global and other GSM/WCDMA ones which even after selecting didn't change the one selected by default.

Dantenios said:
Done. I just wanted to ask, I installed the latest CM 10.1 update, and wondering, when i facotry reset it, it didn't take me through the welcome procudure and under my Mobile network options, i didn't see any LTE options, just EvDO and Global and other GSM/WCDMA ones which even after selecting didn't change the one selected by default.
Click to expand...
Click to collapse
If you don't see the Gmail app (and other Google apps) installed, you may need to flash the latest Gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip

Cannot boot after Flashing [Pics attached]

After Flashing PI3 (pass on odin), first comes "Samsung Galaxy S6'' logo then installing updates and then error screen.
It goes direct to recovery. Tried wipe cache and all. What to do?

I would try the following:
Once in recovery, go to "POWER OFF" select it.
Let it sit for about 2 mins. Reboot to download mode. Flash the update.
Let it reboot and do its stuff. If it still fails, then a hard reset is in store for you. If that still fails, well, hopefully it doesn't.

elesbb said:
I would try the following:
Once in recovery, go to "POWER OFF" select it.
Let it sit for about 2 mins. Reboot to download mode. Flash the update.
Let it reboot and do its stuff. If it still fails, then a hard reset is in store for you. If that still fails, well, hopefully it doesn't.
Click to expand...
Click to collapse
which update? already flashed the latest ROM from Sammobile

[email protected] said:
which update? already flashed the latest ROM from Sammobile
Click to expand...
Click to collapse
Make sure the MD5 matches, and re-flash again. Something didn't get installed properly this is why you need to flash it again, but from a fully powered down state.

Saafir said:
Sammobile firmwares are outdated and likely your problem. Go over to our General section and download the firmware from Koop1955s Guides & Links thread. Flash it and report back.
Click to expand...
Click to collapse
Koop gets his files from Sammobile. I don't know why you said they are outdated and the problem. They are usually the #1 recommended go to site for firmwares. Koop just reups them to a much faster host for the rest of us. (Which I thank him greatly for!)
The only thing wrong with the OPs file could be things like missing pieces, corrupt download, etc. Either way, getting a fresh file from koop's links is probably the best option due to the faster more reliable download servers. So thank you for sharing the link for the OP.

Saafir said:
Well apparently your Sammobile differs from yours, because there isn't any current software aside from PB6.. good day.
Click to expand...
Click to collapse
You don't need to get all hostile man. Look at the pic. It clearly states the latest version on Sammobile.com's website.
Here's the link, but download speed is an atrocity: http://www.sammobile.com/firmwares/database/SM-G920P/

@elesbb and @Saafir, can't we all just get along?
Actually, I do use Sammobile but I also use the Samsung-firmware.org site as well. Sometimes it is slightly ahead of Sammmobile, but not always. https://samsung-firmware.org/model/SM-G920P/
There are TWO problems with Sammobile. The obvious one is the really slow speeds. The second, and not obvious unless you check, is getting a false result that the download has completed. Happened to me the last time. I was about to post, but then I noticed that the PI3 was smaller than the previous version. Had to re-download and got it complete the second go-round.
The other reason that I post to AFH is that you always get an MD5 to check. I know that we experienced folk check those, but less experienced users don't always check. And Sammobile doesn't show the MD5, so...

Saafir said:
I make a lot of on the fly replies. It wasn't intended to be "hostile" at all. My apologies to elesbb
Click to expand...
Click to collapse
@Saafir, anyone that follows this forum knows that you are the first to help out when someone has a problem. That carries a lot of weight and we appreciate you.

I love my Note - Trying to get back to 5.1.1

I love my Note 4 so much that I tried for about 2 weeks to fix it's constant rebooting issue. Went to ATT & Samsung repair center and they couldn't get it to flash. However, it stills turns on, I just generally need to pull the battery for a few minutes to get it to boot.
With that said, I'm not incredibly knowledgeable in this area. I've downloaded ODIN and found lots of resources for the exact steps to follow, however, I'm not sure where I can locate a version of 5.1.1 for ATT. To me, this seems like my only fix for my phone. I've tried clearing cache and factory resets etc. My phone is unlocked. Am I missing anything that you can think of? Can someone link me to a reputable source for the appropriate files?
You seriously cannot imagine how happy I'd be if I can get this thing working again. Thank you!
PS, if you think there is a more stable version than 5.1.1, I'm open to that too.

Bump. Any help is greatly appreciated. Thanks!

Google is your friend...
http://rapidgator.net/file/2ab3e0dc...om/att-galaxy-note-4-sm-n910a-stock-firmware/

Punker1234 said:
I love my Note 4 so much that I tried for about 2 weeks to fix it's constant rebooting issue. Went to ATT & Samsung repair center and they couldn't get it to flash. However, it stills turns on, I just generally need to pull the battery for a few minutes to get it to boot.
With that said, I'm not incredibly knowledgeable in this area. I've downloaded ODIN and found lots of resources for the exact steps to follow, however, I'm not sure where I can locate a version of 5.1.1 for ATT. To me, this seems like my only fix for my phone. I've tried clearing cache and factory resets etc. My phone is unlocked. Am I missing anything that you can think of? Can someone link me to a reputable source for the appropriate files?
You seriously cannot imagine how happy I'd be if I can get this thing working again. Thank you!
PS, if you think there is a more stable version than 5.1.1, I'm open to that too.
Click to expand...
Click to collapse
What is your Baseband? Maybe you can't go back.

Heya guys.
Thank you for the link! I seriously googled and browsed forums for days looking for it. I even went to the Android website with a slew of different version but they did not have the ATT versions. Anyway, I'm going to give this a go but still pretty green to it. I was going to follow the instructions from this post - should work right? https://forum.xda-developers.com/note-4-att/general/expert-phone-trashed-t3573110
And Norbarb, I have no idea what my Baseband version is. I did a quick google to see if I can locate it somewhere but couldn't figure it out. How can I check?
I do appreciate your help.

Punker1234 said:
Heya guys.
Thank you for the link! I seriously googled and browsed forums for days looking for it. I even went to the Android website with a slew of different version but they did not have the ATT versions. Anyway, I'm going to give this a go but still pretty green to it. I was going to follow the instructions from this post - should work right? https://forum.xda-developers.com/note-4-att/general/expert-phone-trashed-t3573110
And Norbarb, I have no idea what my Baseband version is. I did a quick google to see if I can locate it somewhere but couldn't figure it out. How can I check?
I do appreciate your help.
Click to expand...
Click to collapse
Can you reboot to recovery?? There's some info there regarding your current setup

Ironically, now I can't even get the phone to turn on. I bought a battery charger for the Note battery to see if that is the issue. I can't get the battery to charge even when it's plugged in. That arrives Monday so I'll update shortly.

Quick update:
Baseband is N910AUCS2EPK3. I'm not sure if that means I can or can't roll back to Lollipop.

Popped in the charged battery from my new charger and it came right on. Had it on for a little bit just messing around with things. After rebooting it myself a few times, it now is reverting back to it not even turning on, even with a charged battery. I pull the battery 10-20 times, hold the power button without the battery to clearly out any remaining electricity and still no go. I have 2 batteries and neither work. So I'm going to let it sit and if I can get it to come on, install Wake Lock.
Does anyone know if I can revert back to 5.1? I'm not sure how my Baseband effects that. Thank you for all of your help! If I can't get this, I think I may go back to my S3 vs a Pixel.

Punker1234 said:
Quick update:
Baseband is N910AUCS2EPK3. I'm not sure if that means I can or can't roll back to Lollipop.
Click to expand...
Click to collapse
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.

ljjehl said:
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.
Click to expand...
Click to collapse
Holy crap, awesome man. Thank you. At this point, I can't even get the phone to turn on with 2 different batteries. Tried holding the power button down for awhile and letting it sit for hours and still nothing. Not sure what the deal is with this thing. I'll keep attempting.

Punker1234 said:
Holy crap, awesome man. Thank you. At this point, I can't even get the phone to turn on with 2 different batteries. Tried holding the power button down for awhile and letting it sit for hours and still nothing. Not sure what the deal is with this thing. I'll keep attempting.
Click to expand...
Click to collapse
Try holding power button, home button and volume up all at the same time while its powered off. If you can get to Recovery screen here, then you just may be getting somewhere. I would then wipe data/factory reset, then reboot again. If this doesn't work, you can then try holding power botton, home button and Volume down at the same time. This gets you in bootloader mode. Once you get there, only way out at this point is pulling battery (to start over) or get started on Odin flashing.
At least I have kept OTA from working, with this debloater from this link: https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294

ljjehl said:
Try holding power button, home button and volume up all at the same time while its powered off. If you can get to Recovery screen here, then you just may be getting somewhere. I would then wipe data/factory reset, then reboot again. If this doesn't work, you can then try holding power botton, home button and Volume down at the same time. This gets you in bootloader mode. Once you get there, only way out at this point is pulling battery (to start over) or get started on Odin flashing.
At least I have kept OTA from working, with this debloater from this link: https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Click to expand...
Click to collapse
Thanks. Yea i can't get into recovery or the download mode. I bought a battery charger just thinking my phone wasn't charging them. The first time it started up perfect. Now I can't get it to come up at all. As mentioned, I'll keep trying. Wondering if something else has gone wrong, or if it's software related still.

ljjehl said:
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.
Click to expand...
Click to collapse
Got the phone to turn back on. Quick question. In your post, you mention 4 ODIN files. I only have an MD5 file and a PT file. Is there something I'm missing? I downloaded the stock rom from the top of my post. Thank you!

Punker1234 said:
Got the phone to turn back on. Quick question. In your post, you mention 4 ODIN files. I only have an MD5 file and a PT file. Is there something I'm missing? I downloaded the stock rom from the top of my post. Thank you!
Click to expand...
Click to collapse
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
There should be a zip in here that you have to extract four files to a folder. You will use the Odin exe program to look for those files. Just follow my howto notes I wrote in the link I posted. This is to the Marshmallow stuff. Forget the MD5 and pit file unless you know what you are doing. Since I don't know where that came from, I won't even suggest those 2.

ljjehl said:
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
There should be a zip in here that you have to extract four files to a folder. You will use the Odin exe program to look for those files. Just follow my howto notes I wrote in the link I posted. This is to the Marshmallow stuff. Forget the MD5 and pit file unless you know what you are doing. Since I don't know where that came from, I won't even suggest those 2.
Click to expand...
Click to collapse
Ironically I'm looking to get rid of Marshmallow because I think 6.0.1 screwed up my phone. It was working great prior to that. So the LP files I have are the MD5 and pit, supplied in the 3rd post. Is there somewhere I should look for LP files? And to be clear, are there "regular" rom files for general use, and then ODIN specific files? ie, you could have a "regular" 5.1.1 file, and then ODIN specific 5.1.1?

Punker1234 said:
Ironically I'm looking to get rid of Marshmallow because I think 6.0.1 screwed up my phone. It was working great prior to that. So the LP files I have are the MD5 and pit, supplied in the 3rd post. Is there somewhere I should look for LP files? And to be clear, are there "regular" rom files for general use, and then ODIN specific files? ie, you could have a "regular" 5.1.1 file, and then ODIN specific 5.1.1?
Click to expand...
Click to collapse
Well, I have the 5.1.1 Odin files also, but will have to zip it and upload, unless someone else has a link faster

ljjehl said:
Well, I have the 5.1.1 Odin files also, but will have to zip it and upload, unless someone else has a link faster
Click to expand...
Click to collapse
Is there a way to use the files that I have? Not using ODIN? Or is that not recommended?

Punker1234 said:
Is there a way to use the files that I have? Not using ODIN? Or is that not recommended?
Click to expand...
Click to collapse
With the mess you have, I would think you want to Odin flash a whole new setup. You don't know what's wrong and a partition could be corrupted. If it's hardware, nothing you really could do about it anyways

ljjehl said:
With the mess you have, I would think you want to Odin flash a whole new setup. You don't know what's wrong and a partition could be corrupted. If it's hardware, nothing you really could do about it anyways
Click to expand...
Click to collapse
Got it. I looked around and cannot find the files for ATT. I see them for others I think, but ATT is a ghost. Would you mind uploading if you can? If not I understand. I appreciate all of your help! Crossing my fingers that my Note 4 is still alive and well.

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.