Related
I would like to install CM7 from http://forum.cyanogenmod.com/topic/...f0000dangerous-test-releasecolor/#entry148754
But to restore back to Froyo, it says to use ODIN to do a restore with the re-partition option. I thought I read that the re-part option would brick a SGH-I896.
Is this correct? or am I just imagining it.
In other words, does the repartition option work properly on Rogers SGH-I896?
Thanks for any answers you guys give.
You want to run an experimental beta ROM for an i897 phone on your i896? Trying to find the fastest way to brick your phone?
Miami_Son said:
You want to run an experimental beta ROM for an i897 phone on your i896? Trying to find the fastest way to brick your phone?
Click to expand...
Click to collapse
I do not believe it will brick the phone. The board is an I897 with slight revisions. I was just wondering about the method used to go back to froyo. I am not a complete noob and am not worried about bricking to install the rom. Just going back.
But I do appreciate your input.
DO NOT USE PIT / RE- PARTITION ( the p in PIT is for partition )
i did that and on reboot had an error
E: cant mount dev/dbdata...
was STUCK. only option was to do ONE CLICK ODIN, even after flashing EVERY AVAILABLE rogers stock image, on the net and my own, I CANNOT GET RID OF ATT bootscreen without the cheap hack of replaceing the ATT image with the origninal (still named ATT boot).
the CM7 is still not ready, you will just be going back to what you have now,
WAIT for it to be ready.
Everything I've read on CM7 up to this point is that it is not yet ready for use other than for developers trying to fix its remaining bugs. A number of threads opened up on it over the past week have been almost immediately closed because of the potential to mislead people to try it and end up with bricked phones.
I flashed there and back with no problem. I did not use the re-partition option to install.
Well answered
Trusselo said:
DO NOT USE PIT / RE- PARTITION ( the p in PIT is for partition )
i did that and on reboot had an error
E: cant mount dev/dbdata...
was STUCK. only option was to do ONE CLICK ODIN, even after flashing EVERY AVAILABLE rogers stock image, on the net and my own, I CANNOT GET RID OF ATT bootscreen without the cheap hack of replaceing the ATT image with the origninal (still named ATT boot).
the CM7 is still not ready, you will just be going back to what you have now,
WAIT for it to be ready.
Click to expand...
Click to collapse
Thats what I was afraid of, I didn't want to be stuck with att junk on the phone.
Guess i'll wait a little more, sad to say I can only play with gingerbready on by HTC Dream . for now anyways.
Thanks for the answer
Cm7 is largely stable with some bugs. If you do not read the known issues some funky stuff will happen. Speaking from experience ; ) it is everything the hype says it is. Running since the morning. My one concern is battery but I need to let it cycle a couple of times.
Sent from my Captivate using XDA Premium App
Been running CM7 since late January, and did some of the early dev work on porting it to the Captivate. I have an i896. Trust me, it won't brick it.
To op, there will never be a non-one click revert. CM7 changes the setup of the mtd blocks (basically the nand where the rom is installed), meaning you MUST repartition to go back to a Samsung rom. However, none of the Rogers images contain all of the rom, meaning if you repartition, you will be missing parts of the rom, and will just bootloop/be stuck in recovery.
Tl;dr: If you flash it, and want to revert, you must use one-click, and that won't change, even when it's at "stable".
TheEscapist said:
Been running CM7 since late January, and did some of the early dev work on porting it to the Captivate. I have an i896. Trust me, it won't brick it.
To op, there will never be a non-one click revert. CM7 changes the setup of the mtd blocks (basically the nand where the rom is installed), meaning you MUST repartition to go back to a Samsung rom. However, none of the Rogers images contain all of the rom, meaning if you repartition, you will be missing parts of the rom, and will just bootloop/be stuck in recovery.
Tl;dr: If you flash it, and want to revert, you must use one-click, and that won't change, even when it's at "stable".
Click to expand...
Click to collapse
Best advice, straight from the source. And OP, as was said before, make sure you know what the known issues are. The CM7 thread has a lot of complaints about issues that were already noted and known. If you can live with those, jump in!
I've tried searching for the solutions to this, but some of them are difficult to search and I'm struggling to get relevant results. So I apologize if any of this has been covered elsewhere.
Anyhow, I just installed the ParanoidAndroid ROM last night, and it all went very smoothly, and I was pleased. But, there seem to be a couple issues that either I need to iron out, or that the devs need to. And I'm fully willing to believe it's an issue on my end and not theirs, so, here we go:
1) In CWM, the top half of the screen or so has the rainbow glitch going on and there's a de-centered kind of effect happening that makes it very difficult to use.
2) I'm unable to get my external SD card to mount. I've seen plenty of threads about this similar issue, and I've tried tweaking the build.prop entry regarding this, but nothing I'm doing is helping.
3) The flash only works once per boot, even with included flashlight app. I haven't tested the flash's functionality in the camera yet. But in the flashlight app, the flash will turn on, and when I turn it off, it won't come back on until after a reboot.
4) I now have two installations of the stock Gallery app (com.android.gallery3d and com.google.android.gallery3d). I'm sure I can just uninstall one, but is there one that would be wiser to uninstall?
Otherwise, everything else seems to be working just fine. Thank you all very much in advance.
I've since discovered and fixed a new problem. My phone was apparently not sending or receiving any MMS messages, over WiFi or otherwise. But the APNs described in this post fixed that entirely:
http://forum.xda-developers.com/showthread.php?p=23806717#post23806717
As problem #4 from above goes, I deleted the com.android.gallery3d app and kept the com.google.android.gallery3d app as there were internet and syncing features that were omitted or nonfunctional from the former one.
Just so you know, if you read through the paranoid thread in the dev section or any of the ics ROM threads actually, all of your questions r covered. I cangive you answered/jumping off points for your questions.
1. The rainbow distortion comes from having Froyo bootloaders instead of GB. To fix this you will need to use Odin or Heimdall to flash the GB bootloaders. Look in the ISET Super Everything thread that's stickied in the dev section. BE SURE to flash something else with Odin or Heimdall (whichever you choose) before you try flashing the bootloaders. If you lose your connection while trying to flash bootloaders, you can hard brick your phone which basically means you have a shiny coaster.
2. Your external sd card is found in the emmc folder on ics ROMs. You need a root enabled file explorer to open it.
3. Using your camera flash as a flashlight which I believe is referred to as torch is one of the few known remaining bugs on Infuse ics ROMs. The flashlight app that is included is currently the only way to get it working. The flashlight should turn on everytime you open the app but it won't turn back on if you turn it off while in the app.
4. MMS is an issue with the APN settings. Look at the last few pages in the dev section. I know it was recently covered on a couple different ics ROMs threads. To get to the APN settings, go through the following path in the settings.
More (under data usage) > Mobile Networks > Access Point Names, click on the AT&T listing, then change MMS Proxy to 66.209.11.32
I'm pretty sure that is all you have to do to fix MMS but read some dev threads for more info. I think you can also try to look in the Dev Tools app if it is included with the ROM. In the app, click connectivity then start MMS. Again, further reading should give you more info.
Boz™
Sent from my SGH-I997 using xda app-developers app
Yeah, the flashlight thing, I knew was a known bug. But the latest update claiming that "all bugs squashed" misled me, I guess. Because that bug obviously persists. But, c'est la vie.
As the rainbow glitch goes, I never installed Froyo on here, I went from stock to Gingerbread to... actually, here's specifically what happened:
•Initially, I installed 3e Recovery and CWM on my stock Android 2.2 per the instructions here, http://www.youtube.com/watch?v=Y09p-J_g_Rg, and everything went fine.
•Then I flashed Gingerbread UCLB3 per this thread, http://forum.xda-developers.com/showthread.php?t=1508619, but unfortunately, I made a dumb mistake. I neglected to disable Voodoo Lagfix first and softbricked my phone.
•So, I went back to the Infuse Super Everything Thread and found this fix, http://forum.xda-developers.com/showthread.php?t=1092021, brought my phone back to stock, just fine.
•Then I flashed to UCLB3 the same way as before, only this time disabling Voodoo and it all worked perfectly.
•Then I immediately flashed to ParanoidAndroid and everything went as described in the thread and now here I am with the CWM glitch.
So I've only been stock or Gingerbread ever before on my phone.
Anyone know how to simply change the font or install a new one?
Sent from my SGH-I997 using xda premium
I use ROM Toolbox Pro.
Edit: Check the Paranoid Android dev thread end of page 32 and beginning of page 33. The guy that maintains the PA port just posted a link and instructions for the fix to rainbow recovery.
I'm no expert so I may b wrong but I'm pretty sure that if you had a stock AT&T infuse then it most likely came with Froyo originally. Just bc you flashed a GB ROM doesn't mean you got the bootloaders. To get the GB bootloaders, you need to run Heimdall a second time with the "Install Bootloaders" checkbox checked. I'm not exactly sure how it works in Odin but I think you have to have a file in the PDA slot in order to get the bootloaders installed.
I do know that if you have rainbows, it is bc you have Froyo bootloaders. Our at least that is the only reason I've ever heard of and I've read of people with the issue numerous times. I would just read through some of the dev ics threads bc there have been a few times in the last week that I've seen people pay steep by step instructions explaining exactly which Heimdall or Odin to use. I just know that you have to take extra steps to install GB bootloaders. With Heimdall that means checking the flash bootloaders checkbox. They do this bc it can hard brick your phone so they don't want you to install them unless absolutely necessary.
Boz™
Sent from my SGH-I997 using xda app-developers app
Ah-ha! Very good, someone else is having my same problems, lol. I'll definitely be using Odin, as that's how I fixed my softbrick issue and I could never get Heimdall to install on my computer properly (Java issues or something, couldn't figure it out and Odin worked anyway).
Do you know if flashing the bootloader will cause any loss of information or settings? Or will it affect nothing else?
I'm not 100% sure on that one. When I did it, I was using Heimdall to fix my soft bricked phone at the same time so I was basically starting fresh. I'm not sure if it is possible to just flash bootloaders in the Odin PDA slot and keep everything else. I would assume that you would lose everything and have to reflash the ROM from recovery but that's just an assumption.
I would get titanium backup (if u don't already have it) and backup everything and sync with your Gmail account just in case. That way u can save it apps and their settings.
You may b able to ask that question on the PA dev thread and get a better answer.
Boz™
Sent from my SGH-I997 using xda app-developers app
There's an XDA Forum restriction on newbies. I can't post in any Dev forums until I've... done something, I forget. Ten posts or ten thanks. I forget what. Either way, I'm not allowed in there yet. lol
Anyhow, based on some threads I've found, it seems possible to flash only the bootloader in Odin. I'm still just waiting to find out how much information is lost in the process before I dive into it.
But yeah, I do have Titanium, and now that I have everything installed and set up just the way I like it, it is time for a backup anyway.
Supposing I need to, is there any problem restoring system apps and data once I do this? Because everything will be identical, minus the bootloader. I just know I've read enough about the dangers of restoring system data on the threads here to be cautious. Even though I'll just be going from ParanoidAndroid to the same flash of ParanoidAndroid, plus a new bootloader, but better safe than sorry.
Thanks for all your help, man.
Appears as though that question's already been answered here:
http://forum.xda-developers.com/showthread.php?t=1603220&page=5
Bottom of page 5 states somewhat affirmatively that no data will be lost. So, lovely. Now I've just got to flash the bootloader, and then work on my forum searching skills. I can never find ****, when clearly it's somewhere. lol
dstarr3 said:
2) I'm unable to get my external SD card to mount. I've seen plenty of threads about this similar issue, and I've tried tweaking the build.prop entry regarding this, but nothing I'm doing is helping.
Click to expand...
Click to collapse
Figured out the emmc part but how do you actually open the external SD on your pc?
This guide is intended to be an all-in-one resource for people coming to Samsung phones after using other devices. It is a general introduction to the S4 and a glossary/explanation of terms you may see here in the forums.
This thread is slightly out of date but the info is still good, I will be updating again soon!!! Remember to hit thanks if this was useful
Disclaimer "Just because I am trying to be helpful does not make me responsible for anything that you do to your phone. Playing with any of this stuff could destroy your phone"
The layout of this post is as follows:
Welcome
FAQ
Glossary of terms
First off, welcome to XDA
The XDA community is home to the most talented and helpful phone developers on the planet.
These developers spend lots of their free time working on making all of our phones better. You should be nice and respectful to them and follow the rules. WHY? If the statement above isn’t enough reason then think selfishly, the less time they are dealing with redundant questions, the more time they have to develop stuff for all of us!
Help them help you by following the following basic rules:
1.If you are confused or have a question, the first thing to do is READ! Read lots, look things up both on xda and using google.
2.If after searching you still have not answered your question, then post in the Q&A forum.
3.Asking for ETAs on ROMs, updates, etc. is considered rude.. DON’T DO IT!
4.Don’t report bugs to a developer unless:
a.You know 100% that it hasn’t already been reported,
b.You know how to reproduce it
c.You can get a logcat of the problem (more on this later)
Some advice if you are new to all this and don’t want to ruin your phone:
1.Be patient. Don’t be the first or even the tenth person to flash anything. Wait until you see others using whatever Rom or kernel with success.
2.If you have any doubts about what you are doing, read more. Don’t flash.
3.Make sure you are in the forum for your device, not some similar or related device.
FAQ:
Q. Is my bootloader locked?
A. Only if you have an AT&T or Verizon phone
******* Info for AT&T users *******
Q. What is LOKI?
A. Loki is an exploit for phones with locked boot loader that allows us to bypass the locked boot loader in order to install custom roms or recoveries. More Loki info down below
Q. Whats the deal with MF3?
A. MF3 is the current firmware from AT&T that comes on any new phone. Your phone may also auto update to MF3 if you are not careful. MF3 patched the ability to use Loki to install custom roms/recoveries so if you are on MF3 things are much more difficult.
Q. How can I keep my phone from updating to MF3?
A. If you want to avoid the update, you should root your phone and freeze the following three apps using titanium backup or some similar app.
1. AT&T Software update Vxx_x_xxxx_x_x
2. FWUpgrade x.x.x
3. LocalFOTA vx_xxxx_x_x
Why flash?
by flashing your device you can make your phone act differently, look different, and enable new or disabled options. you could ,for example:
enable native tethering
enable call recording
change the look of your phone
add custom toggle buttons
overclock or undervolt
increase battery life
etc..
Kernel vs Rom vs Recovery vs Modem
Kernel is the layer between the phone hardware and the rom. it controls things like Wi-Fi power, touch sensitivity, possible range of screen brightness, phone logging, and processor max and min speed. kernel must be designed not only for your device but also for the type of rom you are using (Sammy rom or Aosp) some kernels support all roms, others are specific.
Rom is the operating system of your phone. there are three main categories of roms.
roms that are based off of the Samsung stock rom (Sammy rom)
roms that are based off of Android open source project aka AOSP (AOSP, AOKP)
roms based off of the miui project (these used to be a branch of AOSP but recently they have also used Sammy base for miui)
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs4) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
modem is a file that controls the cell radio of the phone. Helps determine what frequencies to use and settings for a particular network. It is important when flashing a radio that you flash a radio that is for the AT&T sgs4
Methods for flashing files - Odin vs mobile Odin vs. clockworkmod(cwm) vs adb
Odin is the internal Samsung tool for flashing. I believe it only exists on Windows platform. This tool is mostly used to initially flash an insecure kernel or rooted kernel, OR to return to completely stock rom.. Files for flashing in odin generally should end in .tar or .tar.md5 although sometimes they come zipped and the tar is inside the zip. Read more about Odin before using it as it can easily break your phone. !!!as a general rule make sure you never check the "partition" checkbox EVER!!!
Mobile Odin (THIS TOOL DOES NOT SUPPORT ALL S4 MODELS...make sure you check that it specifically works with yours first. I think at this time it works on your phone unless you have locked bootloader but STILL DOUBLE CHECK) is a phone based version of Odin made by the very talented developer Chainfire. It can be installed on a rooted phone and used to flash the same .tar based files as the desktop version. Mobile odin has a few advantages. 1 you can use it from your phone. 2 it can auto root a stock rom (nice if you want to try out a brand new update that has not been rooted yet)
clockworkmod(cwm) or TWRP is recovery based tool that can make backups of your entire phone, flash new roms, kernels etc.., and do many other useful tasks. Once you have this on your phone my guess is that most of your flashing will be done through this tool. The files for flashing through clockworkmod are .zip files.
ADB is the android develpment bridge. It allows for command line interface with your phone through its debugging options. ADB can do most anything as I understand it. In my several years of flashing I have only had to use it once, and i could have waited for someone to come up with another solution. In general as a noob i recommend you stay away from ADB.
open source vs Samsung base(aka Touchwiz or TW) vs miui
Open Source Roms such as AOSP/AOKP are built using Google's open source android code as a base. The developers then add functionality specific to the device. The advantages of these builds are that they often have tons of options built in to the rom that change the behavior and look of the phone. They usually allow you to change the toggles in your notification pull down, change the battery display, make all kinds of adjustments to sounds, vibration etc... Some people also prefer the "vanilla" android look and feel. These roms often provide "bleeding edge" concepts, design, and modifications. The Disadvantages of these roms is that some of the hardware coding is done closed source by the phone manufacturers, which means that things like Infrared, bluetooth, camera, video recording, and MHL video out often don't work or take much longer to get working by the developers. Basically anything that relies on the Samsung framework will not work in an open source build. This means Svoice, Snote, and the Samsung camera app will not work.
Samsung based roms (aka Touchwiz/TW) are taken from the Samsung original phone software and modified by the developer. Usually, these roms are modified in order to be faster and to make changes to some of the features. Expect to see changes to the stock rom like: debloated (ATT and samsung software removed), de-odexed (explained later), enable tethering, unlimited sms recipients, added notification toggles, etc. Most of these changes are made to: make the phone faster, improve battery life, make the phone easier to theme. The advantage of these roms is that they still use the Samsung framework so all the proprietary stuff like camera, bluetooth, MHL still work, the disadvantage is that they will never be as customisable as open source roms.
MIUI is a rom that focuses on theming. Official MIUI (Chinese) gets updated weekly on Friday and then there are lots of miui developers who adapt it to other languanges and make some tweaks to it. MIUI can be built from AOSP source or Samsung source and depending will have different features. The first MIUI rom for our phone just appeared in these forums and it is based off of AOSP. MIUI has a unique look and is also highly customizable through theming. There are tons of themes available for download through the rom itself and you can mix and match any part of any theme you want. This includes icons, lockscreen style, etc.. Some people criticize while others praise MIUI for being very "iphone like". This is because the icons look more iphone like and there is no app drawer in the MIUI launcher. However, you can still use any launcher you like within MIUI.
odexed vs de-odexed
odexed is how the phone comes stock from Samsung. Odexed means that system files and apps are split into two pieces and kept in different places on the phone. This is done to speed things up a bit. However, it makes it harder to theme the phone because the apps are split up. Most custom roms choose to de-odex (basically regroup the files back into one) so that custom themers can make themes more easily for the phone.
Flashing "dirty" vs flashing "clean"
Clean
Doing a clean install of a rom means erasing or formatting all the data from the previous rom before you flash the new one. This is the prefered way to flash a rom to ensure that it will run smoothly. It is necessary if you are switching from one rom type to another (CM to Samsung base). In order to do a clean flash you need to boot into recovery and select the following options: wipe user data (this wipes all apps and personal data, but not your photos/videos), wipe cache, advanced>wipe dalvik cache, storage/mounts>format system. This will ensure that no trace of the former rom is left on the phone. Beware that at this point your phone will not boot until you install a new rom. I suggest using titanium backup to backup apps and smsbackup+ for texts to make getting your new rom configured easy.
Dirty
Doing a dirty install means just flashing a new rom right over the top of the old one without wiping any data. The advantage to this is that you don't lose any apps or account info. The disadvantage is that you open up the possibility for problems. Generally you only want to flash this way if you are upgrading a rom (CM10 nightly to the next nightly, or from one samsung based rom to another). If you decide to flash over the top and have any issues, you should not report bugs, but try flashing clean first.
Logcat
Logcat is a way to access the android system log for everything that is going on behind the scenes. This tool is used to help developers pinpoint problems in a rom. If you want to actually be helpful to a dev when reporting a bug, you should really learn to use this tool. I am no expert on logcat but you can find some good information in this post: http://forum.xda-developers.com/show....php?t=1726238
What is the Bootloader?
The bootloader is basically what it sounds like...it loads the boot image of the device. Basically it is one of the first things to run on the phone and it shows the phone where to find the boot image and how to start. The bootloader is also responsible for allowing access to the recovery part of the phone.
Locked Bootloader?
This seems to confuse a lot of users so here goes: The AT&T and Verizon versions of our phone have a locked bootloader. What does this mean? To the noob, it means that the devs had to figure out how to bypass or unlock this part of the phone in order to be able to boot custom recoveries such as CWM and TWRP. Getting a custom recovery means being able to backup the phone as well as flash custom roms. Luckily for us, Djrbliss (make sure and thank him! his thread is here:http://forum.xda-developers.com/showthread.php?t=2292157) figured out how to bypass the locked bootloader. The exploit he used is known as Loki. Please remember that the loki exploit is not the same thing as unlocking the bootloader, it is a bypass/trick. AT&T and Verizon have fixed the exploit that allowed loki to work in there newest firmware. Loki patch will not work for MF3 firmware or later.
Loki
refers to the exploit that allows us to run custom recoveries as well as custom roms. You only need to have a loki'd rom if you have a model with a locked bootloader (AT&T). Thankfully, you can install a custom recovery that will auto-Loki any rom you flash so that you can install almost any rom built for our model phone (see below). I strongly recommend flashing an auto loki recovery if you have a phone with locked bootloader. I use this one here: http://forum.xda-developers.com/showthread.php?t=2291956
Compatible Roms
you should be able to run any rom built for AT&T, TMobile, or the I9505 international model (NOT I9500!!) as long as you flash with an auto loki recovery. You can check out this thread for more info. Make sure and thank TheAxman! http://forum.xda-developers.com/showthread.php?t=2295557
You may have to manually set the APN. If you encounter problems with the rom look in that roms thread for answers.
Sticky!!
Well damn, I thought I knew a lot, but after reading this thread, I really didn't. Well done. :good:
Incredible resource for those coming in from a different ecosystem.
Thanks much!!
Thread stuck!! Nice work!
Got my new At&t Samsung Galaxy S4 and this will definitely help me!!
this is another thread that really helped me as well these two have really helped me so far i have rooted several divices and just relied on everyone else and not i am starting to take a lot more of an interest ant these threads have been the most helpful
http://forum.xda-developers.com/showthread.php?p=42055644#post42055644
WoW
Great work! I'm sure this thread will be very helpful to a lot of people (Myself included). Tanks bro! :victory:
More! More! :d
I've been searching high and low ive read everything and maybe im not understanding but after I root my phone how do I do the whole loki thing??... I'm eager to start flashing roms... Ive read of some recoveries that do this is that an accurate assessment??
KINGDROID25 said:
I've been searching high and low ive read everything and maybe im not understanding but after I root my phone how do I do the whole loki thing??... I'm eager to start flashing roms... Ive read of some recoveries that do this is that an accurate assessment??
Click to expand...
Click to collapse
What exactly are you trying to do?
If you want to install a custom ROM or kernel, you need a custom recovery. The ROM or Kernel developer will have LOKI-fied it for you.
For TWRP (my custom recovery of choice) Download GooManager from the Play Store and install.
Inside the goo.im app, go to menu>Install OpenRecovery Script
then you can boot into recovery to apply kernels, ROMs, etc to your hearts desire
joeybear23 said:
What exactly are you trying to do?
If you want to install a custom ROM or kernel, you need a custom recovery. The ROM or Kernel developer will have LOKI-fied it for you.
For TWRP (my custom recovery of choice) Download GooManager from the Play Store and install.
Inside the goo.im app, go to menu>Install OpenRecovery Script
then you can boot into recovery to apply kernels, ROMs, etc to your hearts desire
Click to expand...
Click to collapse
Its tht ez just root and add custom recovery??.. The whole loki thing is what's been throwing me off
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
KINGDROID25 said:
Its tht ez just root and add custom recovery??.. The whole loki thing is what's been throwing me off
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Yes... the difficult part is if you are a developer. They make our lives much easier.
joeybear23 said:
Yes... the difficult part is if you are a developer. They make our lives much easier.
Click to expand...
Click to collapse
Thanx ima root tonight I jus need to get a copy of the stock firmware
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
KINGDROID25 said:
Thanx ima root tonight I jus need to get a copy of the stock firmware
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Stock Firmware:
http://forum.xda-developers.com/showthread.php?t=2261573
That is a HUGE download, but the process is simple.
im not a newb but i need to boost my post count lol...soooo spam
KINGDROID25 said:
I've been searching high and low ive read everything and maybe im not understanding but after I root my phone how do I do the whole loki thing??... I'm eager to start flashing roms... Ive read of some recoveries that do this is that an accurate assessment??
Click to expand...
Click to collapse
I have updated the OP to explain Loki, hope that helps :good:
Noob here first time posting I rooted my phone and installed cwm using casual method, created backup and installed mint rom love it but after a couple of post I see I didn't backup EFS should I be worried?
I'm not sure what the deal is with backing up the IMEI number on our phones yet. I have not seen anyone post about losing their IMEI yet so I wouldn't be too worried. On the s3 only the international model phones could be backed up by saving the efs folder. The backup process for AT&T phones was much more complex. I assume the same holds true on the s4. Will update when I find out more
Sent from my GT-I9505 using xda premium
I wanted to make sure Thx. Is it to late to back EFS or can I just restore my backup and do it?
I bought a galaxy s3 for straighttalk from some one cuz it was really cheap. I want to remove cyanogenmod from it because the camera doesn't work and I can't save pictures. They didn't back up though so when I factory reset it, it brings it right back to cyanogenmod. How do I get the original OS for the s3 back on it? Im new to this kind of stuff so I didn't even know where to look on the forums here. And the person I bought it from is no help, I think they didn't even know how they really did it. Can some one help me or point me in the right direction please?
Sincerely,
Unmarked civillian
Hello and thank you for using XDA Assist,
please check this thread.
Kind regards and good luck
Trafalgar Square
XDA Assist
Trafalgar Square said:
Hello and thank you for using XDA Assist,
please check this thread.
Kind regards and good luck
Trafalgar Square
XDA Assist
Click to expand...
Click to collapse
That guide was a bit confusing for me, the links didnt work, but i donloaded odin v3.04 and i downloaded kies. what do i do from their? both those were suppose to download on the laptop right? not on the phone? sorry im really new to all this.
Unmarkedcivillian said:
That guide was a bit confusing for me, the links didnt work, but i donloaded odin v3.04 and i downloaded kies. what do i do from their? both those were suppose to download on the laptop right? not on the phone? sorry im really new to all this.
Click to expand...
Click to collapse
I need to know if you have the Sprint version (S960L) or the Verizon version (S968C). Most likely you have the S968C.
When you tell me your device model number, I can link you to your firmware and you can flash that via Odin.
Droidriven said:
I need to know if you have the Sprint version (S960L) or the Verizon version (S968C). Most likely you have the S968C.
When you tell me your device model number, I can link you to your firmware and you can flash that via Odin.
Click to expand...
Click to collapse
Oh sorry it was originally sch s968c, I appreciate you helping me out, I'm a nub when it comes to this stuff.
Unmarkedcivillian said:
Oh sorry it was originally sch s968c, I appreciate you helping me out, I'm a nub when it comes to this stuff.
Click to expand...
Click to collapse
can you tell me how to use odin? i downloaded it, but its got so much goin on in their haha
Unmarkedcivillian said:
can you tell me how to use odin? i downloaded it, but its got so much goin on in their haha
Click to expand...
Click to collapse
If you want to flash the stock firmware, you will need to go to Sammobile.com and enter your model number in the search feature there. It will lead you to your firmware, download it on PC.
Make sure you have installed "USB drivers for Samsung phones", you can find them with a Google search, or if you already have Kies installed then you've got the drivers.
On the device, go to system settings>developer options(if you don't see this in settings, you need to go to the "About Phone" option, scroll down to the "Build Number" and tap it at least 7 times to enable Developer Options). In developer options, turn on "USB debugging".
Charge your battery to at least 75%.
Once charged, press and hold the volume down+home+power buttons, at the caution screen, press up to enter download mode.
Open Odin(make sure Kies is closed and isn't running in the background, it interferes with Odin), connect the device to PC with device in download mode. If the device is recognized, you'll get a colored COMM# box. If you don't have that, try a different USB port, make sure your cable is the stock cable.
In Odin, select the AP or PDA button(older Odin has PDA button, newer Odin has AP button). Go to where you downloaded and stored the firmware on your PC, select it.
When you get back to the Odin screen, make sure the only options that are checked are auto reboot and F. reset time.
Click start, when it is done, you will get a green PASS! and the device will reboot, go through setup wizard and enjoy your device.
you are the true MVP of the internet tonight! thanks so much for breaking it down for me haha ive asked all over, here and reddit and few other sites, no one would help me like that! the download for the firmware is going to be an hour from sammobile since im not paying for membership haha but i have work in the morning so ill let it run while i sleep, and do everything in the morning. ill post here tomorrow either in the morning or at night after work and let you know how it went! once again thanks again!
Droidriven said:
If you want to flash the stock firmware, you will need to go to Sammobile.com and enter your model number in the search feature there. It will lead you to your firmware, download it on PC.
Make sure you have installed "USB drivers for Samsung phones", you can find them with a Google search, or if you already have Kies installed then you've got the drivers.
On the device, go to system settings>developer options(if you don't see this in settings, you need to go to the "About Phone" option, scroll down to the "Build Number" and tap it at least 7 times to enable Developer Options). In developer options, turn on "USB debugging".
Charge your battery to at least 75%.
Once charged, press and hold the volume down+home+power buttons, at the caution screen, press up to enter download mode.
Open Odin(make sure Kies is closed and isn't running in the background, it interferes with Odin), connect the device to PC with device in download mode. If the device is recognized, you'll get a colored COMM# box. If you don't have that, try a different USB port, make sure your cable is the stock cable.
In Odin, select the AP or PDA button(older Odin has PDA button, newer Odin has AP button). Go to where you downloaded and stored the firmware on your PC, select it.
When you get back to the Odin screen, make sure the only options that are checked are auto reboot reboot and F. reset time.
Click start, when it is done, you will get a green PASS! and the device will reboot, go through setup wizard and enjoy your device.
Click to expand...
Click to collapse
It said pass and then phone reboots without cyanogenmod, but its stuck at screen where it says A service of TracFone Wireless, did I do something wrong their?
Unmarkedcivillian said:
It said pass and then phone reboots without cyanogenmod, but its stuck at screen where it says A service of TracFone Wireless, did I do something wrong their?
Click to expand...
Click to collapse
Did you make sure that the options I mentioned were set and ONLY those options when you flashed?
Try booting to stock recovery and do a factory reset and wipe cache partition in recovery then reboot.
i had auto reboot and f reset time and PDA checked. booting it in stock recovery, factory reset, and wipe cache partition worked! thanks so much for all your help! i have one more question for ya though. the reason i wanted to delete cyanogenmod is because the camera wouldnt load and i couldnt save images and i wasnt able to go online using data, i could only use wifi. so when out all i could do was call and text, and the mms didnt work. any clue as to why?
Unmarkedcivillian said:
i had auto reboot and f reset time and PDA checked. booting it in stock recovery, factory reset, and wipe cache partition worked! thanks so much for all your help! i have one more question for ya though. the reason i wanted to delete cyanogenmod is because the camera wouldnt load and i couldnt save images and i wasnt able to go online using data, i could only use wifi. so when out all i could do was call and text, and the mms didnt work. any clue as to why?
Click to expand...
Click to collapse
The ROMs were actually built for the Verizon S3(SCH-I535), they are 4G devices, this makes them require a SIM card to regulate the 4G data they use, this makes our device require a CDMA LTE SIM(Verizon 4G LTE SIM or Straight Talk CDMA LTE SIM from the BYOP kit, the LTE version, not the GSM AT&T/T-Mobile kit). I'm actually the one that figured out that a SIM was needed for the ROMs to work. I can explain in detail, but I'll keep it short instead.
Even though our device is 3G and doesn't require a SIM under normal circumstances, with the SIM inserted in our device with those ROMs, we then have working mobile data and MMS, sometimes it requires setting APNs in the ROM along with using the SIM to get stock MMS working, otherwise, MMS would only work when using a 3RD party app for MMS.
A lot of people bricked this device trying to figure out why mobile data wasn't working before I discovered this SIM dependency. I've actually worked with a few developers trying to remove the SIM dependency so our device could use the ROMs without a SIM but nothing works, anything done to remove the dependency, kills all chances of connectivity, even call and text. I also helped with creating the first and only TWRP custom recovery specifically compiled for our d2tfnvzw(Tracfone on Verizon network Straight Talk S3) device. The other recoveries are actually d2vzw(Verizon Wireless S3) but they work on our device also, just not specifically.
The Straight Talk S3 can use the Verizon recoveries and ROMs because it is actually a rebranded Verizon S3(SCH-I535) and actually has the I535 model number stamped on our motherboards and other hardware inside our device, the only difference is that the 4G capability was disabled in the radio(no, using the 4G SIM will not give you 4G data). It is not "similar" to the Verizon S3, it IS the Verizon S3 modified for Straight Talk.
I can actually get you set up with some very good 5.1.1 Lollipop custom ROMs packed with features including working camera(we have marshmallow but front camera isn't working, that is always an issue with new ROMs because stock camera is closed source software, developers are not allowed to use it, they have to piece the coding together from scratch so it takes a while to fix), if you can get a used, previously activated Verizon 4G SIM($3-5 on eBay, used SIMs are better than new SIMs, new SIM gives aggravating issues) or Straight Talk BYOP LTE SIM. The ROMs are MUCH better than the stock JB 4.1.2 firmware. Let me know and I can get you setup and you won't even need the PC to do any of it. It can all be done with apps and your mobile browser. Using WiFi to download on the device instead of mobile data to download the ROM files you'll need, the apps that will flash the files you need are very simple to use. After the files are downloaded all you need is a click here and a click there and about 30 minutes of time and you'll be running something much better than stock with everything working as it should.
I have a guide posted here for flashing CM/CM based ROMs on our device and how to set up SIM and APNs, along with precautionary steps for your protection and troubleshooting steps for data issues after flashing the ROM and how to restore data connectivity if you do something wrong along the way.
If you do a google search using our model number, you'll find stuff everywhere that I have posted about this model number.
wow thats impressive stuff! i wish i could learn to do all that haha. I would love a working ROM on my s3 though, touch whiz is lame! i wont be able to buy the card till tomorrow because i dont have a card right now because i just moved to CT and had a bank that was only in TX and havent opened anything here yet, so ill have to give the cash to a buddy and have him order with his. I actually did the BYOP to straight talk as well when i couldnt use my s3 and i bought my friends s5, it had at&t, and thats where my straight talk service is on right now.. You have ROMs that would run on that by chance? Either one of them would be fun, I dont mind toying with the s3 a bit more though since its basically my side phone incase something happens with my s5.
Unmarkedcivillian said:
wow thats impressive stuff! i wish i could learn to do all that haha. I would love a working ROM on my s3 though, touch whiz is lame! i wont be able to buy the card till tomorrow because i dont have a card right now because i just moved to CT and had a bank that was only in TX and havent opened anything here yet, so ill have to give the cash to a buddy and have him order with his. I actually did the BYOP to straight talk as well when i couldnt use my s3 and i bought my friends s5, it had at&t, and thats where my straight talk service is on right now.. You have ROMs that would run on that by chance? Either one of them would be fun, I dont mind toying with the s3 a bit more though since its basically my side phone incase something happens with my s5.
Click to expand...
Click to collapse
The ST S5 is the Verizon S5 developer edition, the same as the ST S3 is the Verizon S3, the ST S5 is a Verizon rebrand also. Fortunately since it's a developer edition, that means it has an unlocked bootloader so that means you can safely flash the device with custom ROMs if there are any for the Verizon S5, I haven't looked but I'm sure it has ROMs(the other Verizon devices have locked bootloader and they will NEVER be able use anything but stock and modified stock ROMs, they can't use true custom ROMs like Cyanogen because it hard bricks the device because of the locked bootloader).
Droidriven said:
The ST S5 is the Verizon S5 developer edition, the same as the ST S3 is the Verizon S3, the ST S5 is a Verizon rebrand also. Fortunately since it's a developer edition, that means it has an unlocked bootloader so that means you can safely flash the device with custom ROMs if there are any for the Verizon S5, I haven't looked but I'm sure it has ROMs(the other Verizon devices have locked bootloader and they will NEVER be able use anything but stock and modified stock ROMs, they can't use true custom ROMs like Cyanogen because it hard bricks the device because of the locked bootloader).
Click to expand...
Click to collapse
wow thats good to know haha, so even though it was originally bought from at&t its now verizon because of the byop plan? and what kinda of ROMs are available for the S3? Do you have a link I can check out some of the features? Im definitely going to be grabbing a used 4g sim. its the micro right? sorry if im buggin ya man, like i mentioned im real new to this and ive heard of ROMs and stuff before but never really seen them until i bought the S3 from my friend, and you are really knowledgeable about this so I hope you dont mind me picking your brain a little bit with these questions
Unmarkedcivillian said:
wow thats good to know haha, so even though it was originally bought from at&t its now verizon because of the byop plan? and what kinda of ROMs are available for the S3? Do you have a link I can check out some of the features? Im definitely going to be grabbing a used 4g sim. its the micro right? sorry if im buggin ya man, like i mentioned im real new to this and ive heard of ROMs and stuff before but never really seen them until i bought the S3 from my friend, and you are really knowledgeable about this so I hope you dont mind me picking your brain a little bit with these questions
Click to expand...
Click to collapse
Sorry, I misunderstood you, if your S5 came from AT&T then it is AT&T. I was saying that the Straight Talk version of the S5 is a Verizon S5 dev edition. AT&T is not. It will need to use the AT&T S5 ROMs if any exist.
There are a plethora of ROMs for the S3, they are all different so you'll have to check them out for yourself. OctOS 5.1.1 is my favorite and is the most stable and has everything working including front camera. I will have to link you to my copy of it though because it is no longer available for download on XDA. I'm using OctOS marshmallow right now but front camera isn't working yet.
To find the other ROMs, view this forum in a PC or mobile browser, find the Compact tab, click it, then find the Verizon SIII on the list, click it and it will take you to the Verizon S3 forum, then you'll see an Original Android Development and an Android Development subforum there. The ROMs can be found in threads in those two forums, use ONLY the ROMs that specifically say "d2vzw" in their names, do not use anything that says stock or TW or anything that mentions locked bootloader, modem, firmware, Safestrap recovery or Fashfire, that stuff is specifically for the Verizon S3 ONLY and will brick your device, read the threads, the first post in each ROM thread will list the ROM features and instructions for flashing(ignore these instructions and use the ones I link you to instead), but you'll need to be rooted and have custom recovery installed(my guide will explain how to get custom recovery).
Install the Towelroot app on your device, open it, tap the "make it rain" button and you'll be rooted.
Then go to Playstore and install SuperSU, open it to update the binaries.
Then, once you've found the ROM you want and its' compatible Gapps package(Google apps, the thread should mention which one you need), download them and put them both on extsdcard.
Then follow this thread to get a custom recovery installed, flash the ROM and Gapps and setup SIM/APNs. It is a very long guide but it is detailed step by step as simple as I could make it. Pay attention to the warnings and do the things I listed as safety measures for future reference.
http://forum.xda-developers.com/gal...de-to-flashsetup-sim-apn-cm-cm-based-t3351290
If you need help with anything you can reach me with a personal message here instead of posting in the thread.
Droidriven said:
Sorry, I misunderstood you, if your S5 came from AT&T then it is AT&T. I was saying that the Straight Talk version of the S5 is a Verizon S5 dev edition. AT&T is not. It will need to use the AT&T S5 ROMs if any exist.
There are a plethora of ROMs for the S3, they are all different so you'll have to check them out for yourself. OctOS 5.1.1 is my favorite and is the most stable and has everything working including front camera. I will have to link you to my copy of it though because it is no longer available for download on XDA. I'm using OctOS marshmallow right now but front camera isn't working yet.
To find the other ROMs, view this forum in a PC or mobile browser, find the Compact tab, click it, then find the Verizon SIII on the list, click it and it will take you to the Verizon S3 forum, then you'll see an Original Android Development and an Android Development subforum there. The ROMs can be found in threads in those two forums, use ONLY the ROMs that specifically say "d2vzw" in their names, do not use anything that says stock or TW or anything that mentions locked bootloader, modem, firmware, Safestrap recovery or Fashfire, that stuff is specifically for the Verizon S3 ONLY and will brick your device, read the threads, the first post in each ROM thread will list the ROM features and instructions for flashing(ignore these instructions and use the ones I link you to instead), but you'll need to be rooted and have custom recovery installed(my guide will explain how to get custom recovery).
Install the Towelroot app on your device, open it, tap the "make it rain" button and you'll be rooted.
Then go to Playstore and install SuperSU, open it to update the binaries.
Then, once you've found the ROM you want and its' compatible Gapps package(Google apps, the thread should mention which one you need), download them and put them both on extsdcard.
Then follow this thread to get a custom recovery installed, flash the ROM and Gapps and setup SIM/APNs. It is a very long guide but it is detailed step by step as simple as I could make it. Pay attention to the warnings and do the things I listed as safety measures for future reference.
http://forum.xda-developers.com/gal...de-to-flashsetup-sim-apn-cm-cm-based-t3351290
If you need help with anything you can reach me with a personal message here instead of posting in the thread.
Click to expand...
Click to collapse
Awesome! Thanks a bunch again droidriven for all your time and effort in helping me out! Ill order the sim tomorrow and hopefully be flashing a few roms by the beginning of next week!
Unmarkedcivillian said:
Awesome! Thanks a bunch again droidriven for all your time and effort in helping me out! Ill order the sim tomorrow and hopefully be flashing a few roms by the beginning of next week!
Click to expand...
Click to collapse
Cool, just don't forget to use Towelroot or Cydia Impactor to root the S3 then install SuperSU, that must be done before you do anything else.
Let me know if you need anything.
Droidriven said:
Cool, just don't forget to use Towelroot or Cydia Impactor to root the S3 then install SuperSU, that must be done before you do anything else.
Let me know if you need anything.
Click to expand...
Click to collapse
Just rooted and downloaded supersu, I tried to pm you but its saying you aren't accepting them. I have one last question before I head to bed. I just realised, I can still flash a rom in here without the 4g sim still just won't have service, is that correct?
Unmarkedcivillian said:
Just rooted and downloaded supersu, I tried to pm you but its saying you aren't accepting them. I have one last question before I head to bed. I just realised, I can still flash a rom in here without the 4g sim still just won't have service, is that correct?
Click to expand...
Click to collapse
Sorry, I forgot that I blocked messages from the public because I was getting too many people asking for help. I have it set to only allow friends and forum administrators. Oops!!
There are older builds of Kit Kat 4.4.4 that can be flashed without SIM and everything works, but they probably aren't available for download anymore.
Yes, you can flash the ROMs just fine, you'll still have call and text, you'll just need to put the SIM in when you get it and reboot the device then set up the SIM and APNs like my guide says and then reboot again and you should be good to go, make sure you backup your IMEI(NVdata backup) like the guide says also, then be careful when you flash. If you flash and you lose all service including calling then don't do anything until you get in touch with me, if you make the wrong move from there, you'll make a mess that will be difficult to fix.
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint. It would appear that Boost and Virgin Mobile variants can be flashed as they are used on Sprint's network, but no promises will be made.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing.
In the "CSC" box, use the file beginning with "home_CSC" to retain your user data, or use the "CSC" file to completely wipe user data. If you bricked your device, you may need to resort to using the "CSC" file. If you flash with "home" and it still fails to work, use "CSC." (that's my understanding of the two files anyways)
If you are down-grading, you may have to select the "NAND erase all" check box. This will completely wipe the device and should allow a fresh install. Be careful, if the phone dies, I would worry about a hard brick, but I'm not positive about that though.
Google Drive link:
https://drive.google.com/file/d/0B2iEgzRTFjrQWlpEbURIWUlXLWc/view?usp=drivesdk
There have been several reports that these Odin ROMs fail to flash. If that happens to you, you may be able to try an alternate procedure here. Keep in mind this procedure will trip Knox and probably void warranty if you haven't done that already:
https://forum.xda-developers.com/general/general/rom-stock-pl1-samsung-galaxy-j3-emerge-t3689346
The newer QI1 version is posted here, and has been confirmed:
https://forum.xda-developers.com/showpost.php?p=74171277&postcount=39
and if you're more enterprising with your computer and image file skills:
https://forum.xda-developers.com/showpost.php?p=74137125&postcount=29
Greaper88 said:
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing. I'm not sure what the difference between the "CSC" and the "HOME _CSC" files is (or that it really matters), but I'd imagine that if one is resorting to this, then someone could tell us... Based on my previous devices, I'd recommend the "CSC" file.
https://drive.google.com/file/d/0B2iEgzRTFjrQWlpEbURIWUlXLWc/view?usp=drivesdk
Click to expand...
Click to collapse
good stuff broseph,might (MIGHT) have a go ,idk re cinfiging my type of peivacy and workarounds aint time cheap so ill leave it at that, good ish tho, I wanna create a deodexed verasion myself but had a setback pc wise regarding a unbootable Hdd , I believe a deodexed rom to be a pre-requisite to having the xposed framework workout ....am i correct in believing this guys and gals? Let me know because I really love my ubuntu pc and would most likely buy a hdd just for these type of tasks since compipation would require over 100gb from what I have heard ,. 4 gb file then decompile and rexompile eaxh of the apps and framework resources.
Doctur said:
good stuff broseph,might (MIGHT) have a go ,idk re cinfiging my type of peivacy and workarounds aint time cheap so ill leave it at that, good ish tho, I wanna create a deodexed verasion myself but had a setback pc wise regarding a unbootable Hdd , I believe a deodexed rom to be a pre-requisite to having the xposed framework workout ....am i correct in believing this guys and gals? Let me know because I really love my ubuntu pc and would most likely buy a hdd just for these type of tasks since compipation would require over 100gb from what I have heard ,. 4 gb file then decompile and rexompile eaxh of the apps and framework resources.
Click to expand...
Click to collapse
The system ROM is actually about five and a half gigabytes based on the storage info in the device settings (on my device anyways). So here's what I'm thinking makes sense for space required. I'm just gonna round the decompiled ROM up to 6GB to allow room to play with. Here's the space you'll need at a minimum:
1. 6GB for the compiled ROM.
2. 6GB for the decompiled ROM.
3. 6GB minimum for working with the ROM, so that your source is unmodified.
4. 6GB for the recompiled ROM.
So you'd need a minimum of 24 GB to work with, but the more you have, the more breathing room you have. This is just my 2¢... As for the rest of it, I have no real clue.
I just bought the j327p last week and I am returning it today if I can't get the tethering to work.
I tried editing a lot of the easily searchable fixes which there aren't many.
Do you know if installing this might work?
Just obtained this phone from Boost Mobile. Am I correct in thinking that this ROM should work on a Boost Mobile phone seeing as Boost is an MVNO of Sprint?
SammaelAkuma said:
Just obtained this phone from Boost Mobile. Am I correct in thinking that this ROM should work on a Boost Mobile phone seeing as Boost is an MVNO of Sprint?
Click to expand...
Click to collapse
It works and it's been updated from APL1 to AQB6 .. at least mine has .. and I don't know what was updated or what's new but it's still on Android 6.0 .. I just used this to fix my Boost J3 Emerge after it got stuck installing an app from the Galaxy S8
Doctur said:
...I believe a deodexed rom to be a pre-requisite to having the xposed
This link will get xposed to work...
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
TD378
Divided we stall,
United We Install!
Click to expand...
Click to collapse
Actually Wanam got xposed working on our device. Nice tut but its really almost standard issue when dealing with samsung. Im guessing this is your first galaxy phone? Personally done myself on the galaxy s4 sch r970 (ya the one from 2013.. ), j7 j700t and this galaxy emerge 327p, there are also many tutorials on how to do so, thanks for trying to help, but you could have just linked wanams thread wich has all cautions and tuts in like 12 words a HUGE thanks to Wanam for spending countless hours making a modded version of xposed that is compatible with ours as well as many other galaxy devices!!!
Project89Odin said:
...Im guessing this is your first galaxy phone? Personally done myself on the galaxy s4 sch r970 (ya the one from 2013.. ), j7 j700t and this galaxy emerge 327p...
Click to expand...
Click to collapse
Choose to stay away from "main stream" phones for a number of reasons.
But at the request of your post, link has been updated!
TD378
DIVIDED WE STALL
UNITED WE INSTALL
Thank you, the Galaxy J3 is not a very followed device by samsung of the fact that it is not high-end
________________________________________________________________________________
http://iphon8.fr/ galaxy note 9
Greaper88 said:
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing. I'm not sure what the difference between the "CSC" and the "HOME _CSC" files is (or that it really matters), but I'd imagine that if one is resorting to this, then someone could tell us... Based on my previous devices, I'd recommend the "CSC" file.
Click to expand...
Click to collapse
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
vivianajeanty said:
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
Click to expand...
Click to collapse
Download the default firmware here...
http://updato.com/firmware-archive-select-model?record=F2F2C99C28B211E7963AFA163EE8F90B
In Odin, put each file in the correct section "ex. APxxx goes in AP section."
Use CSCxxx file NOT Home_CSCxxx in CSC section. All data will be lost.
Brick problem will be solved. Let me know if you need a tut created.
TD378
Divided we stall
United we install
If refering to me as this being my first Samsung that would be a negative....mainly all ive dealt with or care to deal with besides a few exceptions ( IOS Not EVER being one of those) After all thesr years of either referring quickly to this site or the last 2 1/2 pouring countless hours learning random device or specific ...usefull or not (* Few times have i bee let downyet its been an occurance.. worth noting) I belived it was time to throw my hat inthe ring.
So mainly besides wanting to recontribute the resources I have.....mostly my hours of studying and stuff i picked up retentetion being put work and the test and the Love of Working in A Linux Terminal
(*Flavor preference is not important.)
And the Fact that I have a Laptop that can process at about 3.7ghz with 8 threads if you include hyperthreading...along with my growing older and not wanting to Let small contributions like that and Development left saught after by the few.....and honestly which matters in some places I am only scraping by so Financially I have nothing to offer the community along with Tha Mad Love I have for everything XDA ....put that together and you got me doing what I can..Lately it hasnt been to much but wait around and other issues that have eaten away at time leaving me unable to do simple things such as deodex......tho I was looking to do it the hard way and by hand..
My apologizies if the post after mine answered or the second one did but I have yet to read link .....so besides me knowing Wanam got a way around it for most the Install and Stuff
My true and Last Attempt at my first Question
FINGERS CROSSED
LONG
Would there be any necessity in the terms of Modular Functionality either individual or a compilation of your choosing and or combination that would specifically require you to deodex the firmware of any 5.0 or Higher Samsung Based Firmware so that one might have a higher sucess rate or all around better experince?
SHORT
Should i spend my time deodexing this rom for the few who have it in attempts to better the end user experience , spend my time else ?
Id like a little bit of step i the right direction but might just do it and then move to more time , intelectually and pc resource consuming work....
---------- Post added at 01:14 PM ---------- Previous post was at 01:04 PM ----------
vivianajeanty said:
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
Click to expand...
Click to collapse
Umm I know if you downloaded off a disrepputable and FREE source that it might be the CSC partiton. I ll pm you with a copy of my firmware that was Adb Pulled by my old Firmware subcription site and did in Fact come from my device.....or the file was set to reupload for seeding purposes....idk either way we will handle this as a community united.
NOTE
I have since given device up....
Havent given up on it ...
So yeah to modding out a new more flagship type model...
Building ,Porting , Deodexing this J3 ....
And just seeing a lil development o a mid to low end device * price =low specs=mid....ish
Growing as a person in both knowledge and contributionally as well. Thanks 4 time.... **Sorry if I ramble.**
this did get my boost samsung j3 emerge working again but the problem is no matter what i do i can not get it to pass the safety net test :/ the software version is also different from the stock version
this version:j327pvpu1apl1
stock version:J327PVPU0APJ2
am i correct in assuming that this could be my safety net issue? and if so can anyone help point me in the right direction to the stock boost firmware? ill be searching for it regardless but if i can get help before i find it then that'd be super thanks for asking
tac0xenon said:
this did get my boost samsung j3 emerge working again but the problem is no matter what i do i can not get it to pass the safety net test :/ the software version is also different from the stock version
this version:j327pvpu1apl1
stock version:J327PVPU0APJ2
am i correct in assuming that this could be my safety net issue? and if so can anyone help point me in the right direction to the stock boost firmware? ill be searching for it regardless but if i can get help before i find it then that'd be super thanks for asking
Click to expand...
Click to collapse
Are you rooted? Or running a custom kernel? Both of those things and a few others will cause you to fail. Another option would be to select NAND erase in ODIN when you flash. That will completely wipe your device before flashing, but as with any flashing procedures, it could lead to an unusable device.
Greaper88 said:
Are you rooted? Or running a custom kernel? Both of those things and a few others will cause you to fail. Another option would be to select NAND erase in ODIN when you flash. That will completely wipe your device before flashing, but as with any flashing procedures, it could lead to an unusable device.
Click to expand...
Click to collapse
I was rooted with super su but after failing safety net I began searching for a a way around it and i successfully unrooted my phone then re rooted with magisk and passed the safety net test yay! And life was good for a while until I to install xposed framework. I made a super noob mistake and flashed it with a low battery percentage and of course it died in the middle of it. I turned my phone on and no OS... Crap baskets... noob mistake number 2 my nandroid backup I must not have been paying attention and tried to save it to internal storage instead of the SD card which if you own this phone you probably know that it doesn't work that way so double crap baskets.
Fast forward to finding this post I loaded it up everything works as it should but it won't pass safety net rooted or not and no custom kernel
This is not a life or death problem as everything works flawlessly except for the safety net test But my woman likes to go on walks and play Pokémon go together and now I can't and it is slightly annoying that we are no longer able to. It's a cheap way to get outside and have a little fun towards the end of the week as opposed to Netflix and other boring stuff
tac0xenon said:
I was rooted with super su but after failing safety net I began searching for a a way around it and i successfully unrooted my phone then re rooted with magisk and passed the safety net test yay! And life was good for a while until I to install xposed framework. I made a super noob mistake and flashed it with a low battery percentage and of course it died in the middle of it. I turned my phone on and no OS... Crap baskets... noob mistake number 2 my nandroid backup I must not have been paying attention and tried to save it to internal storage instead of the SD card which if you own this phone you probably know that it doesn't work that way so double crap baskets.
Fast forward to finding this post I loaded it up everything works as it should but it won't pass safety net rooted or not and no custom kernel
This is not a life or death problem as everything works flawlessly except for the safety net test But my woman likes to go on walks and play Pokémon go together and now I can't and it is slightly annoying that we are no longer able to. It's a cheap way to get outside and have a little fun towards the end of the week as opposed to Netflix and other boring stuff
Click to expand...
Click to collapse
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Greaper88 said:
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Click to expand...
Click to collapse
Thanks for the tips I'll try it when I get home and let you know how it goes much appreciated
Greaper88 said:
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Click to expand...
Click to collapse
Had to flash three times but your advice worked thank you very much
Frp
Hello I have a question I'm a newbie and I would like to know if when I do install the stock rom does that mean I have to put in the google account information of the person providing the stock rom