Related
I attempted my first rooting and install of darthstalkers rom last night. the step by step instructions were well laid out, and the process was pretty smooth. however after completing the rom install, and began getting various errors such as 'gallery not responding', 'omacp has stopped working',etc. over a dozen different errors in total. kies wouldnt connect to restore my settings,etc.
i decided to flash back to stock, and followed the instructions perfectly, which again were very easy. kies connected instantly on stock, and everything seemed ok. however im still getting the same errors as i was with the darthstalker rom. now i bought my s3 outright (its not part of any package), so i have no warranty issues, however my phone is completely hosed now. i cant send texts, cant view email, nothing. i'm honestly regretting ever doing this.
any help/tips/suggestions so that i can go back to the way i was? ive tried everything that my googlefu has led me to, and nothing has worked.
Rawt said:
I attempted my first rooting and install of darthstalkers rom last night. the step by step instructions were well laid out, and the process was pretty smooth. however after completing the rom install, and began getting various errors such as 'gallery not responding', 'omacp has stopped working',etc. over a dozen different errors in total. kies wouldnt connect to restore my settings,etc.
i decided to flash back to stock, and followed the instructions perfectly, which again were very easy. kies connected instantly on stock, and everything seemed ok. however im still getting the same errors as i was with the darthstalker rom. now i bought my s3 outright (its not part of any package), so i have no warranty issues, however my phone is completely hosed now. i cant send texts, cant view email, nothing. i'm honestly regretting ever doing this.
any help/tips/suggestions so that i can go back to the way i was? ive tried everything that my googlefu has led me to, and nothing has worked.
Click to expand...
Click to collapse
have you tried booting into stock recovery, wiping data and cache?
xBeerdroiDx said:
have you tried booting into stock recovery, wiping data and cache?
Click to expand...
Click to collapse
I did it last night, but in my tired confusion, i may have fudged it up. going to do it now and ill update in a few minutes. Thanks for the help thus far.
when flashing to stock through Odin you retain the same cache and therefore you can have some issues of force closes..which is why a factory reset is always best....and mandatory when going from 4.1.1 to 4.0.4
That's a very stable ROM and I'm surprised at the issues you had. I have a feeling it wasn't the ROM or anything you did persay but bad flashes happen which it why most of us have a nandroid to fall back on just in case. Sometimes a re-flash does the trick to fix problems.
hednik said:
when flashing to stock through Odin you retain the same cache and therefore you can have some issues of force closes..which is why a factory reset is always best....and mandatory when going from 4.1.1 to 4.0.4
That's a very stable ROM and I'm surprised at the issues you had. I have a feeling it wasn't the ROM or anything you did persay but bad flashes happen which it why most of us have a nandroid to fall back on just in case. Sometimes a re-flash does the trick to fix problems.
Click to expand...
Click to collapse
Ok well i wiped cache/data in recovery mode and all seemed ok (not sure if its worth noting, but the recovery menu/screen was totally different from last night - the one last night was touch screen with ++++ before and after each menu choice, and the one today has me using the volume keys to move and power to select).
i went to do kies restore and it went smoothly, but is now sitting on the last option, 'restoring call log', for quite a while. So i guess ill update this again when kies finishes up.
10 minutes later and its still sitting at restoring call log. should i abort this?
Rawt said:
10 minutes later and its still sitting at restoring call log. should i abort this?
Click to expand...
Click to collapse
you can if you want
since call logs aren't important as long as your contact list is restored
pcshano said:
you can if you want
since call logs aren't important as long as your contact list is restored
Click to expand...
Click to collapse
seems to have worked. all my contacts are there, and i can send/receive texts. only issue is, none of my apps, settings, layout, wifi,etc transferred over for some reason. so i guess im stuck manually entering in all of this data. what a ****ing hassle this was.
do any of you trusted members do this for a fee? i really liked what i saw with darthstalkers, but cannot be bothered to go through this again.
Rawt said:
seems to have worked. all my contacts are there, and i can send/receive texts. only issue is, none of my apps, settings, layout, wifi,etc transferred over for some reason. so i guess im stuck manually entering in all of this data. what a ****ing hassle this was.
do any of you trusted members do this for a fee? i really liked what i saw with darthstalkers, but cannot be bothered to go through this again.
Click to expand...
Click to collapse
Settings, not much can be done about that. It's needed to wipe them when going to a custom ROM (same goes when updating to avoid issues).
Titanium Backup can save your Wifi, apps and apps data (requires root). Also can save your texts and call logs with it.
Rawt said:
Ok well i wiped cache/data in recovery mode and all seemed ok (not sure if its worth noting, but the recovery menu/screen was totally different from last night - the one last night was touch screen with ++++ before and after each menu choice, and the one today has me using the volume keys to move and power to select).
i went to do kies restore and it went smoothly, but is now sitting on the last option, 'restoring call log', for quite a while. So i guess ill update this again when kies finishes up.
Click to expand...
Click to collapse
Sounds like you booted into stock recovery which is what you wanted.
I used to think it was a pain restoring settings all the time but after 100 or so ROM's over various devices its takes 10-15 minutes to do that and install my apps form the market (I only use maybe 20 or so and maybe are one I have apk for already.
Everyone's first time is a bit awkward and messy... gets fun after you do it enough
So its possible it was just a bad install? This isnt a very technical or tough thing to do, but becomes a serious pain int he ass when things go awry. Would love to have the darthstalkers setup, though. I just hate to do it and have it all be FUBAR'd again.
hednik said:
.
Everyone's first time is a bit awkward and messy... gets fun after you do it enough
Click to expand...
Click to collapse
This line is awesome!
Sent from my SGH-I747 using xda app-developers app
Rawt said:
So its possible it was just a bad install? This isnt a very technical or tough thing to do, but becomes a serious pain int he ass when things go awry. Would love to have the darthstalkers setup, though. I just hate to do it and have it all be FUBAR'd again.
Click to expand...
Click to collapse
Keep in mind that flashing a custom ROM also means flashing the updates (as it can always get better and there are bugs to fix), meaning that you will have to factory reset every time (which resets your settings, cleans your apps and such). So it's something you kinda have to get used to when flashing.
That's also why I suggested Titanium Backup, it saves a lot of time when it comes to apps, wifi, call logs, texts, etc. You'll still have to go through your settings, emails and accounts though.
If you wanna go ahead and give Darthstarkers another try, re-download it and make sure you follow their full instructions.
hednik said:
Everyone's first time is a bit awkward and messy... gets fun after you do it enough
Click to expand...
Click to collapse
its true. the first time around is always a little bumpy. as long as you are doing things correctly and installing the correct files, things will only go smoother with time.
this is just my preference, but once i've transcended stock (to aosp), i dont mess around with kies anymore. i know you had your things backed up via that route but ask around and you'll see, there are a lot of useful apps out there that can backup and seamlessly restore everything you want after flashing.
dont give up. everyone deserves the performance and style they want on their device. next time you're ready, let us know. between myself, hednik and a few others, we can get you the best way to do this right here in one thread versus 20 different sites/threads/opinions. cheers
I didnt think about the future and rom updates, etc. I think ill pass for now, my time for this is limited. I'd love to have something like darthstalker working, but i cannot afford to spend the time if it all goes to hell again.I do sincerely appreciate the help, and if theres some way i can say thanks other than clicking thanks for each of you (already done), please let me know.
Rawt said:
I didnt think about the future and rom updates, etc. I think ill pass for now, my time for this is limited. I'd love to have something like darthstalker working, but i cannot afford to spend the time if it all goes to hell again.I do sincerely appreciate the help, and if theres some way i can say thanks other than clicking thanks for each of you (already done), please let me know.
Click to expand...
Click to collapse
It's basically the way to show your gratitude, you've said thanks and pressed the button, can't ask for much more :highfive: Especially from a new user.
I hope you find the time to enjoy one of those custom ROM at some point and we'll be here if you need help again. Good luck!
Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
dokgu said:
Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
Click to expand...
Click to collapse
I agree with Elesbb. If the goal is jus tto get back to stock, just do an odin flash of the stock ROM. Be advised if you flash the latest Kit Kay update you will nto be able to go back to Jelly Bean. From your post it seems like you are partial to Jelly Bean. So if that's what you want, but sure you use the stock 4.3 ROM. You can find it around here on XDA somewhere with a quick search to make sure you have the right one.
As Elesbb said, you won't loose the 'sim unlock'. But you will lose root. However you can root the stock ROM just fine.
You might also consider one of the myriad of TouchWiz based custom ROMs. They are look just like TouchWiz that your wife wants, but have a lot of optimizations and options in them. Those should flash just like any ROM. If you still get the reboot issue then do the Odin back to stock, reroot, then flash the custom TW roms.
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Thread cleaned.
Rather than bashing a ROM or user let's keep on topic and help the OP resolved the problems he's having. Arguing over the virtues of a ROM doesn't help anyone.
Thank you,
Rwilco12
Before posting this thread I sent the aforementioned guide's poster (arocker). He sent me a reply saying not to use gapps as the stock ROM for Metro PCS already comes with Google apps. I'll try his suggestion first and see if the phone still reboots a lot.
If the problem persists, I will try the solutions mentioned here. Thanks a lot!
elesbb said:
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
dokgu said:
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
Click to expand...
Click to collapse
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Hello PanchoPlanet,
Thanks for the link. I went ahead and tried to unroot without Windows (Mobile Odin) as per the instructions on the link. I downloaded everything and went ahead to install the Mobile Odin APK. When I ran it to install the Flash Kernel, the app told me that the device is not supported.
To my understanding the guide is for M919 devices but should work for my wife's device as well (M919N - Metro PCS). I would like to try the guide for using Windows but I'm not really expecting for it to work or I might mess it up more. I'll try to search some more and provide the links where this forum will lead me to. But if you have any ideas, please let me know asap. Thanks!
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Ok, here's what I found:
forum.xda-developers.com/showthread.php?t=2446497
It seems like the perfect thread for what I am trying to achieve. Will let you guys know if it is successful. But it will have to wait for tomorrow. Gonna catch some sleep.
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And 100% of the time, they eventually just get old.
dokgu said:
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
Click to expand...
Click to collapse
That's a wierd situation, by swapping batteries you basically performed a battery pull, which acts as a reset, that in it self may have cleared your issue.
Now if battery is bad that could be an unusual problem. Maybe just replacing the battery will be the end of your mystery.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
The batteries are all the same. Don't worry about that.
Even if its a new battery if could have just been bad. A manufacturing defect perhaps.
Sent from your phone. You should be more careful where you leave that thing.
dokgu said:
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
Click to expand...
Click to collapse
This battery thing is wacky, anyway swapping batteries should not be a problem, it's just an energy storage container. Pulling the battery isn't like powering down the phone or resetting/rebooting ,sometimes devs request a battery pull to get the proper wipe effect that reboots can't provide.
You inadvertently solved your problem by accident. That's a good thing.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
PanchoPlanet said:
You inadvertently solved your problem by accident. That's a good thing.
Click to expand...
Click to collapse
I have quite literally solved the vast majority of my problems this way.
Its a preferred method.
Sent from your phone. You should be more careful where you leave that thing.
Sometimes it's that "total disconnect "of power that kind of gets all the ducks lined up in a row and everything flows in the dynaflow.
Good.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
its very important topics and it might seen for every galaxy s4 users.just wonderful topics.
This exact same thing happened on my mother's 6-month old S3. If you're still wondering, you could try putting the old battery and running a CPU stress test app. It should increase the current draw and trigger a shutdown.
EDIT: whoops, sorry to kind of zombie. Didn't check the date.
Sent from my Galaxy S4
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!
Hello,
When I woke up a few moments ago I noticed that a system update icon was in my notification bar, which I assume is the new ZVD update and right now my phone is on ZVC and is stock rooted using ioroot25 and I have TWRP 2.7.0.0 AND download mode both working thanks to AutoRec and everything is working fine but it was a difficult getting to this point because I was one of the early adopters of the AutoRec method and I had to to go back to stock and re-tot my phone numerous times to get root, recovery, & download mode all 3 working on my phone without issue.
Now that the ZVD update is waiting to be downloaded on my phone I do not want to have to go through all this stuff again nor do I want to lose anything I have on my phone currently so I would like to ask what is the recommended / safest way to install this update so that I can keep root, recovery, and download mode all 3 and not lose any of my data at the same time ?
Of course, I want to also make sure that this does not mess up my phone like the white screen issue some people had when using AutoRec on the Sprint version of the G2 or other issues so what are my choices and thanks in advance for any and all replies.
MTCell
You won't be able to until they fix the update. Even just root will lock the system on the update.
Only safe way right now is to tot back to stock zvc, take the update. Root with ioroot25. If you want recovery, you can use auto-rec and then flash dorimax kernel. Which has the zvd knock code in it.
Sent from my LG-LS980 using Tapatalk
secret.animal said:
You won't be able to until they fix the update. Even just root will lock the system on the update.
Only safe way right now is to tot back to stock zvc, take the update. Root with ioroot25. If you want recovery, you can use auto-rec and then flash dorimax kernel. Which has the zvd knock code in it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I also have a similar issue as the OP. I am currently rooted, stock rom. ZVD update has downloaded and is ready to install. However, what would be the nessesary steps to take prior to updating my phone? I dont care if I have to re-root again. I rooted me device using IOroot25. How can I unroot?
Thanks!
Supersu has the option to unroot permanently. Doing a full unroot. Weather the system accepts that, I'm not sure.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
...Only safe way right now is to tot back to stock zvc...
Click to expand...
Click to collapse
But, reflashing the ZVC tot will erase all data, correct?
jlv3 said:
But, reflashing the ZVC tot will erase all data, correct?
Click to expand...
Click to collapse
Yes, complete everything. Data, pictures, documents, downloads.
Sent from my Nexus 7 using Tapatalk
mtcellph said:
Hello,
When I woke up a few moments ago I noticed that a system update icon was in my notification bar, which I assume is the new ZVD update and right now my phone is on ZVC and is stock rooted using ioroot25 and I have TWRP 2.7.0.0 AND download mode both working thanks to AutoRec and everything is working fine but it was a difficult getting to this point because I was one of the early adopters of the AutoRec method and I had to to go back to stock and re-tot my phone numerous times to get root, recovery, & download mode all 3 working on my phone without issue.
Now that the ZVD update is waiting to be downloaded on my phone I do not want to have to go through all this stuff again nor do I want to lose anything I have on my phone currently so I would like to ask what is the recommended / safest way to install this update so that I can keep root, recovery, and download mode all 3 and not lose any of my data at the same time ?
Of course, I want to also make sure that this does not mess up my phone like the white screen issue some people had when using AutoRec on the Sprint version of the G2 or other issues so what are my choices and thanks in advance for any and all replies.
MTCell
Click to expand...
Click to collapse
From what i understand , you will need a stock ZVC recovery and boot loader to apply the update. if you have any modification done in ROM (debloat/deleting/modifying system files) then the update might not complete.
So flash stock aboot(bootloader), recovery and kernel and then only apply the update.
TOT reflash is too cumbersome process and requires lot of restoration of apps setting etc.
I have same situation and am searching for stock files from ZVC. Please if any one has these stock file please do share.
Cheers
Phuq! I wish I read these forums more frequently.
Hey all,
Okay now, let me begin this horror story by say what I think needs to be said first and foremost.
"No matter your level of knowledge, there is always something new for you to learn."
With that being said, I phuqed up!!
I had my dream setup running almost perfectly. I mean heavily modded. Stock kitkat 4.4.2. from Sprint so I didnt have to upgrade anything. I rooted via .apk file. I autorec'd TWRP recovery. I first flashed a furnace kernel that gave me 2.49GHz overclock. And added in xdabebs cam mod. And loved it. I kept reading and researching. I found more goodies to play with. I install xposed framework and some useful add-in's. I find some old apps I love, like hide softkeys, and several quick launchers like pie control, and gestures. I eventually find D's kernel and was elated! 2.8GHz, whoopee! (although I have seen someone @3GHz.)
After about a weeks worth of additions, and stupid auto-updates from google play (omfg they take up so much room) I got that dreaded icon in my notifications bar that Im out of room!!!! Stupid phuq'n non Korean model phones! (I feel that is hella racist of LG to show their people love and phuq us over with no external memory support. We should arrange a class action law suit. Thats purposely shaping the market favorably in your region, and selling obsolete hardware to the rest of the world. "shameful behavior LG")
So to remedy the space issue, I go through my most painful, and totally ridiculous ritual of removing "my" bloatware. All the launchers that I dont really NEED or use OFTEN. The apps that are convenient to have , but that convenience is never utilized. Or its rarely needed. And that helped me out about say, oh 200mb.
DAMN IT! need more room! Need room now!! Ahhhhhhhhhhh!
Okay so a few Big boys had to go. So I dumped a game or two, and the 2nd OS I forgot about on my device, Kali Linux. That gave me the much needed room. I gained about 4GB back. Cool beans, I figure before I do any new major changing of this phone I will force myself to make room for backups, ON device! :angel:
Well that didnt pan out. Instead I did one better, (I thought) I chose to back up on device, then rip it to my PC. Cool , it has the space for storing crap like that..
"ahh, life and its inevitable bullshnikeys"
BAM!! a day or so later, my PC froze, in the middle of a gnarly drift. Crap, restart, checks disk , fixes one error, bam froze again, "ah shiz, I need to back up my back ups!" checks disk, a few errors , I have seen worse. I got it up and running then, ZZZzzzzrrrrttt! NOOOoooooooh! So the PC goes down hard. No HDD found style.
So I reach for my G2 to take a much needed brake on the throne and plan somethings out. I sit down, hit the pwr button, and my phone was in TWRP! Odd I think to myself, and proceed to reboot. TWRP! look through settings, look for anything new on the sdcard (internal) nothing. So I power it down and turn it back on. TWRP! Furious!
Now Im at defcon5 using my LIVE OS, BT5r3 KDE, and decided to hear back into the XDA jungle to see what might have happened.
I got the update for ZVD it would seem. And it bit me in the ass at the worst time. I do not have the Android drivers that the phone installs to the PC installed and configured because I cant cycle into Android OS. Im seriously stuck in TWRP mode. I managed to get into download mode once after trying for 20minutes to do so. ( I need to practice that) But for no avail, I couldnt configure/install/set anything up that would have allowed me to communicate with the phone.
Im so very tired and stressed. Normally I would throw this crap away and go back to my trusty and (IMO) more stylish motorola RZRv3, but its battery is like a joke with its 3 minute, PERIOD life time. SMH
So now I come before you, alone, tired, confused, and depressed, (I do not, like reinstalling anything, ever, in anything.) I just really dont want to hit that brick wall (pardon the pun) an know I have to, ahem, configure, so many apps that I enjoy using. All because I lost my recovery.
What is it about the recovery file that makes the option for keeping your user installed apps, achievable, versus the wack (not even an option at all) choice of having to wipe everything and start over? Because (IMO) that is in no way, a recover. Thats a fumble, oh, interception. Thats dropping the ball. If you waste all the space for "backing things up" then something happens, and you still have to completely wipe the IMPORTANT stuff!! Whats the point?
I have found and installed on this VB PC running windows 7 non sp1, x86-
LG Flashtool 1.8.1.1023
LG-Mobile-Driver v 3.8.1
adt-bundle-windows-x86-20140702
adbpush
LG PC Suite (that just serves no purpose other than to annoy me by not working WITH my phone)
I have downloaded the .dll for MY phone for Flashtool
I found and downloaded the 45475791e80904201311e1051ea628c3b98eef87.LS980ZVC_12-LS980ZVD_19_update from sprint
I have downloaded CloudyG3_1.2 and cm-11-20140623-nightly-ls980
What can I do to attempt to simply boot back into my android.
and if there is no option for simply restoring the functionality of the devices previous state,
what ROM/OS do you suggest I shove in this brick or what method should I use to punch the life back into my phone?
Im dyin ova eeeah!!!
Thanks in advance,
Orcinus
ZVD bit me too-not sure how, NEVER told it to install
adamant_orcinus said:
Hey all,
Okay now, let me begin this horror story by say what I think needs to be said first and foremost.
"No matter your level of knowledge, there is always something new for you to learn."
With that being said, I phuqed up!!
I had my dream setup running almost perfectly. I mean heavily modded. Stock kitkat 4.4.2. from Sprint so I didnt have to upgrade anything. I rooted via .apk file. I autorec'd TWRP recovery. I first flashed a furnace kernel that gave me 2.49GHz overclock. And added in xdabebs cam mod. And loved it. I kept reading and researching. I found more goodies to play with. I install xposed framework and some useful add-in's. I find some old apps I love, like hide softkeys, and several quick launchers like pie control, and gestures. I eventually find D's kernel and was elated! 2.8GHz, whoopee! (although I have seen someone @3GHz.)
After about a weeks worth of additions, and stupid auto-updates from google play (omfg they take up so much room) I got that dreaded icon in my notifications bar that Im out of room!!!! Stupid phuq'n non Korean model phones! (I feel that is hella racist of LG to show their people love and phuq us over with no external memory support. We should arrange a class action law suit. Thats purposely shaping the market favorably in your region, and selling obsolete hardware to the rest of the world. "shameful behavior LG")
So to remedy the space issue, I go through my most painful, and totally ridiculous ritual of removing "my" bloatware. All the launchers that I dont really NEED or use OFTEN. The apps that are convenient to have , but that convenience is never utilized. Or its rarely needed. And that helped me out about say, oh 200mb.
DAMN IT! need more room! Need room now!! Ahhhhhhhhhhh!
Okay so a few Big boys had to go. So I dumped a game or two, and the 2nd OS I forgot about on my device, Kali Linux. That gave me the much needed room. I gained about 4GB back. Cool beans, I figure before I do any new major changing of this phone I will force myself to make room for backups, ON device! :angel:
Well that didnt pan out. Instead I did one better, (I thought) I chose to back up on device, then rip it to my PC. Cool , it has the space for storing crap like that..
"ahh, life and its inevitable bullshnikeys"
BAM!! a day or so later, my PC froze, in the middle of a gnarly drift. Crap, restart, checks disk , fixes one error, bam froze again, "ah shiz, I need to back up my back ups!" checks disk, a few errors , I have seen worse. I got it up and running then, ZZZzzzzrrrrttt! NOOOoooooooh! So the PC goes down hard. No HDD found style.
So I reach for my G2 to take a much needed brake on the throne and plan somethings out. I sit down, hit the pwr button, and my phone was in TWRP! Odd I think to myself, and proceed to reboot. TWRP! look through settings, look for anything new on the sdcard (internal) nothing. So I power it down and turn it back on. TWRP! Furious!
Now Im at defcon5 using my LIVE OS, BT5r3 KDE, and decided to hear back into the XDA jungle to see what might have happened.
I got the update for ZVD it would seem. And it bit me in the ass at the worst time. I do not have the Android drivers that the phone installs to the PC installed and configured because I cant cycle into Android OS. Im seriously stuck in TWRP mode. I managed to get into download mode once after trying for 20minutes to do so. ( I need to practice that) But for no avail, I couldnt configure/install/set anything up that would have allowed me to communicate with the phone.
Im so very tired and stressed. Normally I would throw this crap away and go back to my trusty and (IMO) more stylish motorola RZRv3, but its battery is like a joke with its 3 minute, PERIOD life time. SMH
So now I come before you, alone, tired, confused, and depressed, (I do not, like reinstalling anything, ever, in anything.) I just really dont want to hit that brick wall (pardon the pun) an know I have to, ahem, configure, so many apps that I enjoy using. All because I lost my recovery.
What is it about the recovery file that makes the option for keeping your user installed apps, achievable, versus the wack (not even an option at all) choice of having to wipe everything and start over? Because (IMO) that is in no way, a recover. Thats a fumble, oh, interception. Thats dropping the ball. If you waste all the space for "backing things up" then something happens, and you still have to completely wipe the IMPORTANT stuff!! Whats the point?
I have found and installed on this VB PC running windows 7 non sp1, x86-
LG Flashtool 1.8.1.1023
LG-Mobile-Driver v 3.8.1
adt-bundle-windows-x86-20140702
adbpush
LG PC Suite (that just serves no purpose other than to annoy me by not working WITH my phone)
I have downloaded the .dll for MY phone for Flashtool
I found and downloaded the 45475791e80904201311e1051ea628c3b98eef87.LS980ZVC_12-LS980ZVD_19_update from sprint
I have downloaded CloudyG3_1.2 and cm-11-20140623-nightly-ls980
What can I do to attempt to simply boot back into my android.
and if te youhere is no option for simply restoring the functionality of the devices previous state,
what ROM/OS do you suggest I shove in this brick or what method should I use to punch the life back into my phone?
Im dyin ova eeeah!!!
Thanks in advance,
Orcinus
Click to expand...
Click to collapse
Sorry Dude, I was in the same spot, maybe I can save you hours of reading. This is what I had to do:
http://forum.xda-developers.com/showthread.php?t=2432476 it's the dreaded tot to zvc
I've always been interested in installing ROMs, rooting, and all the cool stuff that comes with it, since my first android phone. Unfortunately, my first two android phones ended up having a lot of issues with just working stock, so when I finally ended up getting a Samsung Galaxy Note II (I317M - Rogers/Canadian) and it worked... I held off on the modding. Well, my cell contract is up, the warranty has expired, sounds like the perfect time to start.
Of course, this is post KNOX, so after reading around and watching some videos, it was unclear as to whether I could actually install ROMs at all. I wasn't worried about the warranty, just if I could do it, and it would work. So I decided to just jump in anyway.
First task is to root. I tried flashing a CWM+Root with Odin 1.85. No go. Just wouldn't work. So I ended up using chainfire's CF-Auto-root. It would give me the root I wanted, and the stock recovery. The package came with Odin 3.07, and everything worked. It flashed, I downloaded Titanium Backup and launched it, and SuperSU did prompt for root access, and everything went fine. Excellent! Two years after getting the phone and 3 years since I've wanted to do this, everything is going well.
Next task is a custom recovery. I picked TWRP, mostly because I wanted to try the Ditto Note ROM, and they suggested using that. Flashed the recovery in Odin 3.07 and reboot into Recovery with the three finger salute of volume up, home, and power. TWRP launches. Excellent. First order of business is to click the backup button and check all the boxes. Takes 1400-1500 seconds to backup the 6.5GB.
Time to get the ROM and jump in. Downloaded Ditto Note 4 v 2.2 from the team Electron site, and transfer it to my phone. So far things are looking good. Still don't know for SURE if my bootloader is locked or if KNOX will not let me do things, but I have a couple of backups, so I'm going to take the plunge. I reboot into TWRP, wipe the dalvik cache, cache, data, and system, then I install the ROM. Didn't take long at all. Time to see if it works.
At this point I should mention that the reboot function on TWRP(v2.8.6.0) seems to just loop me back into TWRP, no matter which option I choose. So I hold the power button to actually reboot... and...
TA DA! Ditto Note 4 is going through it's first start. I come across a black and white gradient fill background with some sort of animated tesseract sphere in the middle. I'm cool with that, but that also means I can add in my own animation at some point which is even more cool. Go through the start up prompts and...
The first problem. Wifi won't turn on. The other Canadians here will know the pain of not having wifi for your cell with our data prices up here. This is something that needs to be solved. Back on to the forums to see if anyone else has had the same issue, and someone did, the solution? Flash the latest AGNi kernel. Hey, I'm down, now do I flash a kernal with odin or TWRP? After spending way too much time on google, I went to the actual AGNi thread and after a few pages found out that people were installing it with CWM. TWRP it is then. I tried installing it through TWRP, all seemed to go well, though I did note that in the terminal window I did say that it failed to set permissions. That can't be good, but it did say that it installed successfully. Let's give it a go.
The phone started... but nothing had changed. I noticed the OTA Updater app, so I tried using that. Once it was done downloading I clicked the install/flash button. That wasn't a good idea. I flashed it, but ended up in a loop that would only show me TWRP. Even after removing the battery it would only go to TWRP.
What else could I do? I restored the backup in TWRP. Let's start over.
Rooted with the same method, Installed TWRP again, installed DN4 again, tried to run the AGNi settings app and found out that root wasn't working. So after some searching I came across the 2.14 SuperSU update and installed it with TWRP. Root is back. Awesome. Time to get my wifi back, installed the 4.4.5 AGNi kernel, and this time, no permission sets failed. This too, is a great sign. Got the OTA Updater download and this time, decided not to have the program reboot to install it, and just rebooted into TWRP myself to do it manually. Installed fine, rebooted and... my wifi is working.
Mission accomplished. I haven't fully tested everything yet, but I did check to make sure that the s-pen was working, the camera, and after messing with the APN settings a bit, had LTE as well.
All things considered, for a first time, not too bad. So glad I had made that backup before hand. Glad I had remembered to do that, and also to write down the APN stuff before hand. It was mostly correct to what I had, but there were 2 fields that were different, changed them and had full LTE.
So far things seem great! More testing is needed, but I can call and recieve calls, wifi/cellular data works, camera and s-pen works.
Still a noob in this department, but due to the xda-devs making good products, nothing killed the phone, and things are working great.
Thanks to Chainfire, Team Win, Team Electron, psndna88, and anyone else that has worked on any of these projects. So far things work well, and those of us with older phones really appreciate your effort and work on breathing new life into these devices. Cheers mates!
Nice first post for your first one my friend excellent ?! If you need any help with Dn4 you can post in the q&a section since your so new to Xda.
And welcome to the world of Android and Xda enjoy your stay here.. Ttys
Bajan