[Q] [ROM MK3 ROOTED] SPHL710 All In One Installer [ODEX/DEODEX] - Issues - Sprint Samsung Galaxy S III

http://forum.xda-developers.com/showthread.php?t=2549136
Wanted to start by saying a big THANK YOU to @ThunderStick and all the other devs that have worked on this. I came from Stock Rooted 4.1.2 and it was great to have a stock 4.3 (MK3) ROM with all this awesomeness added already (and KNOX removed). I flashed the "SPHL710_ALLINONE_MK3_ODEX_12-04-2013_1030pm.zip". That said, I'm having a couple minor issues...
Reoccurring download notifications:
Issue: Every few minutes my notification tray fills up with all the files I downloaded previously.
Fix: Open the Downloads app and clear the list on both tabs.
Apps constantly crashing
Issue: Several apps crash on boot and more won't open.
Fix: I'm able to remove/reinstall these apps and the problem is fixed, but this doesn't seem like it should be necessary.
Android Upgrading on every boot
Issue: Every time I boot I get the notification that Android is upgrading. I don't know that it upgrades the apps every time, but still annoying to have the delayed boot.
Fix: No fix yet.
NFC/Google Wallet
Issue: I'm getting the NfcPaymentSetupFailure: 1 error, which I read means my Secure Element for Tap and Pay is busted.
Fix: No fix yet. I was able to restore my backup and setup Google Wallet and Tap and Pay without problems. Still won't work on new ROM though - even after clearing things in the app.
Now for the real questions
Should I try the DEODEX version? Would it be better to just flash all the updates/changes separately instead of using this script? Has anyone else had these issues or know fixes? The NFC thing is probably my biggest concern at this time - I can deal with the rest probably.
Thanks for your help!

First question is did you do a clean install ? Meaning did you do a FULL Wipe before flashing the Rom ? By FULL Wipe I mean : system - data - caches - factory reset. I would also suggest wiping internal storage on the device. Especially if coming from 4.1.2 . Second question is did you verify the MD5 checksums before flashing ?

prboy1969 said:
First question is did you do a clean install ? Meaning did you do a FULL Wipe before flashing the Rom ? By FULL Wipe I mean : system - data - caches - factory reset. I would also suggest wiping internal storage on the device. Especially if coming from 4.1.2 . Second question is did you verify the MD5 checksums before flashing ?
Click to expand...
Click to collapse
Thanks for the reply. No, I did not do a complete wipe. The ROM I flashed did a wipe on System, but I didn't wipe data. That would likely solve the Android Upgrade reoccurrence and crashing apps, but kinda defeats the point in taking an upgrade based on a factory upgrade. I did wipe cache and Dalvic Cache a few times after flashing - just to make sure...
I did have difficulty downloading from the Goo.im link and ended up downloading to my PC then transferring over. Checked the MD5 once I got it to my phone and it matched.

Doing a FULL Wipe may seem like it's more work than it is worth. But in the long run it will save you time, and headaches. Also there are many apps that will help restore some, if not most of your data. Although I will caution you. It is best to tread lightly when restoring data. Especially system data. Which I suggest you stay away from doing.

Related

[Q] Reset to Stock ICS/Unroot/etc. (Boot Issues)

So I've found a lot of threads on here giving me great info on how to handle various situations, but given what I'm looking to do with my phone, I'm not sure what order to do everything in and what tools are best. Currently, my T989 is on ICS 4.0.3 (UVLE1), rooted, with CWM installed. When I originally upgraded to ICS, something got messed up that caused my phone to hang on "Goodbye" anytime I try to turn it off/reboot. I've read that Darkside's Cache Wipe can fix that issue, but basically I'd like to wipe the device, start fresh with a stock build and get everything right from the start. I will likely root it again later, but I'd at least like to get it reset to stock and have everything working correctly first.
What I'm looking to do:
Unroot and uninstall CWM
Wipe the phone clean (all data, cache, partitions, etc.)
Clear the phone entirely back to stock OS/stock recovery/stock everything
Upgrade to the latest stock OS (if necessary)
I'd like to do all this while also fixing whatever caused the hang while shutting down/rebooting. I'd also like to use a stock OS image from Kies instead of downloading one from other places if at all possible (I'm a tad paranoid/OCD when it comes to stuff like that). I've seen two Darkside tools-- cache wipe and super wipe, and I'm not sure if I need one or both of them to help with clearing off the device/fixing my reboot issue.
So with all that in mind, what's my best route to take? I'm just looking for what tools to use and in what order, there are enough great guides on here on how to use the various tools that I can figure out the rest from those. In other words, "Use X to clear blah, uninstall Y while choosing yadda, install Z" etc. I hope that's not too tall of an order Thanks to all for your help!

[Q] Grand rebooting problem help

my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
chrowley said:
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
Click to expand...
Click to collapse
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
ashwin77sgg said:
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
Click to expand...
Click to collapse
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
chrowley said:
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
Click to expand...
Click to collapse
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
ashwin77sgg said:
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
Click to expand...
Click to collapse
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
chrowley said:
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
Click to expand...
Click to collapse
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
ashwin77sgg said:
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
Click to expand...
Click to collapse
i already tried it sir but it didnt solve the problem, it passes the setup but after a few minutes the phone reboots.
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
naufalhadyan said:
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
Click to expand...
Click to collapse
This is probably the best explained and most direct definition of what to do and what may be happening with our ever-rebooting Grands.... Thank you!!!
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
victorsmarotta said:
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
Click to expand...
Click to collapse
Even iam facing the same issue
phone reboots automatically and doesnt even start... infinite bootloop. Was working fine and suddenly this issue came up from nowhere(past 2 weeks) ..
Iam using Resurrection rom 5.7.4 (Marshmallow)
Damn I was on AICP 11, when this exact strange bootloop problem occurred for no rhyme and reason. I know the hardware is fine, the issue arises from installing apps from playstore, the moment it goes beyond a certain app limit in the device, it will start endless bootloop, I am sure this is Google's doing. Anyways this is not a hardware issue and I know more people will be coming here looking for answer to this issue. I have tried both the opengapps and deltagapps, same behaved this way, it never happened before and lately google have introduced one other app which is google's android instant app that will sit in your device, even though you need it not not. very well google for using our precious internal data to around 500Mb to 1Gb.
formating data partition solves this issue, temporarily but you lose your apps and data.
I had successfully avoided this issue when I stopped installing more apps on my device, It took me 2 tries and I found a perfect balance of 4-5 apps, it came crashing again when I tried installing the 7th app.
I don't know if other ROMs will be able to handle this bug, but I know it's time for me to look for another ROM, I was happy with AICP 11, for more than a year. Sad.
Reading about this issue, I came to know this is prevalent on all CM marshmallow based ROMs. So, going to flash Nougat or kitkat or the stock ROM should probably fix this.
Try a new battery.

[Q] [ROM][10 Sep][4.0.4][Sense 4.1 Lite][OTA|HUB|EQS... -- stuck bootscreen

Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...
im not sure why
but have you tried re-flashing the ROM?
PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.
KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl

[Q] Super Sluggish: 4.4.2 or Root?

Long story made short, I upgraded to 4.3 after switching over to AT&T and fell quickly in love with the selective privacy app. However, my battery would only last about fifteen seconds (exaggeration) so I upgraded again to 4.4.2 without performing due diligence. As you all well know, Google took away the privacy app. So I took the next logical step and rooted my phone (TowelRoot rocks!) and added xPrivacy.
My problem now is an extremely sluggish phone. Would this be due to the upgrade (4.4.2) or the root process? Would it make more sense to downgrade or flash a custom ROM?
Root should have no effect on performance at all. Its more likely that there is some data from a previous build causing a process to hang.
I would factory reset and start over clean. Only restore essential data.
You can also use Better Battery Stats. Find it here on xda. Great app for solving battery problems.
DocHoliday77 said:
Root should have no effect on performance at all. Its more likely that there is some data from a previous build causing a process to hang.
I would factory reset and start over clean. Only restore essential data.
You can also use Better Battery Stats. Find it here on xda. Great app for solving battery problems.
Click to expand...
Click to collapse
I think I can't see the forest for all the trees. Is a factory reset done through the phone itself? (i.e. Settings->Accounts->Backup and reset->Factory data reset) Or are you referring to finding the proper ROM and flashing through Odin?
TNAR said:
I think I can't see the forest for all the trees. Is a factory reset done through the phone itself? (i.e. Settings->Accounts->Backup and reset->Factory data reset) Or are you referring to finding the proper ROM and flashing through Odin?
Click to expand...
Click to collapse
You can do a wipe of the cache and data via recovery. Factory reset via the phone should work too.
Factory resetting from Settings actually just reboots recovery and performs it from there. So doing it either way will net the same result. And yes, thats the factory reset I was referring to.
Note, if stock recovery is on the device, factory reset formats the data partition, so ALL apps and data are wiped. If custom recovery is installed, it instead will selectively delete everything but your Internal SD Card, preserving any data you have stored there. Either way, always have a current backup.

Need major help/advice from the community

I'm so disconcerted right now. I have the Verizon LG G3, everything stock but rooted, and just recently was fiddling with the Bump bootloader bypass. Everything was going well, and I remember this thread from a while back because I'm heavy on customizing my phone. Long story short, I download the "Clean Lockscreen" mod, flashed it, and now I get a "unfortunately the process com.android.systemui has stopped" when I boot up my phone. Skips the lockscreen, the home pages load up normally, but the only thing I can interact with is the Power Menu and the "Ok" to dismiss the "unfortunately..." message.
(mod was directly from http://forum.xda-developers.com/lg-g3/themes-apps/theme-g3-clean-look-kk-4-4-2-t2834442)
Short of factory resetting, is there any quick dirty fix that will let me stop having a panic attack? I'm so lazy/dumb for not having a backup, but I was so eager to start flashing things I couldn't be bothered to set one up. I gambled and lost. Hard.
Also, is there anyway to extract my photos before, worst case scenario, I do have to factory reset? I have so many pictures since I bought this phone that losing them all because of this little mistake is what's driving me crazy, on top of losing every little tweak I did here and there for the past few months.
Lastly, if I do factory reset, does that also erase everything on my SD card? The Quick Circle case is on there pretty snug.
**My theory is that someone with a Verizon LG G3 V10B (didn't update because I was afraid to lose root) has the original file that whatever the "Clean Lockscreen mod" file replaced, and I can just flash that and be sane again** please please please
TL;DR --> Verizon user, got Bump, got excited, started flashing things with no backup (dumb dumb dumb), going crazy, now hoping that I can replace that one thing I flashed with the stock original and be fine (whatever the Clean Lockscreen mod changed)
BE VERY CAREFUL READING THIS POST, IF YOU FOLLOW MY SUGGESTIONS AND LOSE YOUR PICTURES FOR ANY REASON I AM NOT RESPONSABLE.
~ You shoulda done a backup.
Just booting into recovery is 90% of the work needed to do a backup, The other 10% of the work is just clicking "backup" and waiting 15 seconds. (You were just lazy/impatient, Not dumb.)
~ Did you flash a mod that was specifically for your exact model?
~ Can you still get into your custom recovery?
~ Before you try anything in my list I would first see if you can locate the stock lockscreen files on the internet for your model and flash them back onto your phone.
~ The FC issues you're having is usually related to not having the proper permissions.
If you can still go into recovery, Boot into recovery and wipe the Cache, Dalvik cache, & go to advanced and click fix permissions.
~ It looks like to me that your launcher may be pooched.
(In my experience the lockscreen/keyguard seems to be tied to the actual launcher/UI itself, Which is why I believe your UI is broken)
Because you can't install a new launcher in the operating system I would try and find a flashable .zip version of another launcher, like nova launcher or something and flash that in recovery.
~ I'm 99% sure a Factory reset won't help your situation.
I'm almost positive you're gonna have to re-flash your firmware to return your phone to working condition.
~ Try a dirty flash, Using same type of rom. (YOU "COULD" LOSE YOUR PICTURES DOING THIS, BUT PROBLY WON'T, Use as one of your last resorts)
Try and find a flashable .zip rom that is flashable in recovery, One that is the same type as your current rom and try a dirty flash "without" wiping anything.
Only flash using the recovery without wiping "OR YOU WILL LOSE ALL YOUR PICS", Also if you flash using your PC it WILL DELETE EVERYTHING.
(If your current rom is stock or stock based rom, Find a stock/stock based .zip based rom and dirty flash in custom recovery)
(If your current rom is AOSP based rom, Find a AOSP based .zip based rom and dirty flash in custom recovery)
After you dirty flash, Backup your pictures & anything else you may need then do a clean flash.
~ There are apps that can recover "deleted/inaccessible" data. (THIS IS ABSOLUTLY LAST RESORT, DON'T TRY THIS UNTIL YOU HAVE ABSOLUTLY NO OTHER OPTION.)
When you delete something off a storage device, It doesn't delete the actual data, It deletes the operating systems directories where the said info is stored, Resulting in what looks like to the operating system as "empty space" Which it actually isn't.
If you "have to" wipe your phone before being able to recover your pictures, Avoid installing ANYTHING you can (If/when possible) until you recover your pictures if you have to wipe your phone, Because anything that goes on your phone while your stuff is deleted CAN be overwritten. (You're gonna have to google a bit to find what apps are capable of this on android.)

Categories

Resources