Related
Last week I rooted my primary phone, a Samsung Admire with Gingerbread 2.3.4. This was done only after successfully rooting my older LG Optimus T running Fryo. I had no trouble with either phone during the process. However, as of 2 days ago the Admire has had some troubles, namely that the phone function crashes when I press the send key. I get the error message stating “Sorry! The process com.android.phone has stopped unexpectedly. Please try again.” It will receive incoming calls but they cannot be answered and when I try, it crashes
I’ve spent much of the time since researching the problem to find the cause and it’s fix. In doing d\so I have read of multiple causes from screen resolution changes to attempted over clocking, which I have played with. I’ve read that there might be problems with the phones attempting to switch from 2g to 3g too rapidly, something this phone cannot do I believe.
I came to the conclusion, probably erroneously, that I needed to reset it back to factory and then reinstall apps and data out of the backup I made using Titanium Backup prior to the phones troubles. So I did so, doing the three button cocktail I’ve read about here on XDA Forums. After doing this, the problem persists. I’ve read some more becoming more baffled as I went along. So I tried to reroot the phone using one click root, and that was unsuccessful as well, no root. I then read that all I needed to do was to install Superuser from the Market. In attempting this I found my device was no longer recognized by Market and after going through their troubleshooting process it’s still unrecognized, Next I decided, also most likely erroneously to reset the phone again using the three button combo as before. This time I noticed at the bottom of the screen written in yellow, E: File is written: not updated
Also as a side note my phone currently says that there are 133MB available and after the reset(s) my bloat ware has not returned,
So that’s it. I seem to have deleted something that kills the phone app and prevents me from rooting. Other than those two things the phone is working well. However as it sits it’s merely a small Internet tablet with no phone capability. Can anyone help me out with this? And yes, I have read and read and read about it but clearly this is beyond my ability to fix on my own.
Thanks,
Zeke
Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.
Reached said:
Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.
Click to expand...
Click to collapse
I will research this Odin you mention as I have no clue as to what it is. Thanks, anyone else care to chime in?
Zeke
Hi everyone,
I am writing this post out of some need: I really just am not capable of the rooting process. I'm plenty savvy enough, and have used computers intensely for almost 30 years. I understand the benefits and risks of rooting, have rooted phones before, but have never delved too deeply.
I am also physically disabled, and the endless simultaneous button presses, unplugging and plugging, and on and on, make rooting an activity that I just can't easily keep up with.
I own two Samsung phones: a Note 3, and a Mega, both from AT&T. I rooted the Mega easily, and was really enjoying it until one day the yellow triangle with the unauthorized software on system message appeared - I had not attempted to flash a custom ROM, so I'm not sure what is wrong. I bought the Note 3 from a friend who had flashed Knoxraid onto the phone to then decide he didn't like it. He removed root, thinking that would return him to stock. Which it didn't, of course. I have tried rooting the phone again to no avail.
I would just like to have both phones rooted and in good working order. I don't much care about flashing ROMs. Given a good launcher like Nova, apps like Wanam and Greenify, and a few others, I find my needs are well met.
Can anyone help me?
did you try this http://forum.xda-developers.com/showpost.php?p=53406788&postcount=1
its a one click app for root.
Hi, I'm new to these forums. Someone redirected me here because of the anomaly, but I'll get to that in the story.
A couple months back, my old S4 (Verizon SCH-I545) had to be replaced due to the 4G hardware failing. I did not initially want to root my replacement, but needed to after within a day (without downloading any apps; restored old ones from Titanium), some weird browser hijacker found its way onto my phone. I gave in to the android update notifications because another thread somewhere said it fixed security issues. It did not fix mine, in fact, it locked my external SD card as well. I should have done my research first before allowing that update, but too late after that; time to root. Next I found that towerlroot was the newest method of rooting of the SCH-I545, so I read up on what needed to be done, downloaded the required firmware, and fired up Odin mode and the Odin flasher. Here's where things got weird: No Knox Warranty Void or Knox Kernal Lock flags. They simply weren't there. "What the hell? Screw it, I'm rooting anyway". Everything seemed to work fine and it rooted, but soon after I started getting the infamous frequent crashing and resetting that so many other users get. I've tried reflashing and wiping the cache several times, neither worked. I've just dealt with the problem as I've been very busy, but now I'm fed up. Any help with the crashing would be greatly appreciated, as would insight as to why my phone does not have Knox.
I tried posting a picture of the picture of my phone's Odin Mode, but apparently new users can't post them, so: i(dot)imgur(dot)com(slash)wpU3uT7(dot)jpg
You may wish to post your question here there is still lots of support for that phone there. Please be careful though, you likely still have a locked bootloader so keep that in mind
Good luck
Thanks for pointing me in the right direction; updating to baseband -NK1 fixed it! Still curious about the missing flags, though.
root confirmed. Basically keep running kingroot. If it reboots it didnt work. It will say it failed only. When you get the root failed msg, close app and then reopen. It will ask for permission to optimize a few things..grant it. Boom rooted. Unfortunately, root is lost if you reboot. About to try supersu me when i get off work.
Update- Supersu me seems to be uneffective
http://1drv.ms/1TgZCJm
Fingers crossed !
We're gonna need someone that has been down these type of roads before to help. I got supersu in and busybox in and removed kingroot through terminal, but when I tried to put in the supersu binaries, NO GO. I still think the wide release of MM to all LG will get more people onboard.
jmacie said:
We're gonna need someone that has been down these type of roads before to help. I got supersu in and busybox in and removed kingroot through terminal, but when I tried to put in the supersu binaries, NO GO. I still think the wide release of MM to all LG will get more people onboard.
Click to expand...
Click to collapse
I wonder if Dominick has even seen this yet? Seemed like he would have said something by now. Maybe I'll shoot him a text when I get a few.
I sent him one yesterday, no response
Man hope they can get it to stay after reboot
Tapping fingers....anxiously waiting....
waiting for status update..... please devs dont leave us hanging on lol we need yall
All this stuff is getting passed around and some have made reference to a dev here on the G4 that might have some answers, and others are optimistic on androidforums. I think and I may have stated it before, that the wide spread adoption of MM on LG will provide more help. I tried to get some info on the kingroot thread here, but they really are focusing on 5.1 and lower. The kingroot that we used here is for 5.1, theoathkeeperalpha kept on keeping on an it worked as a temp. The guys on androidforum seem to think that temp root and busybox and manipulating selinux is all that might be needed, except for some expertise on manipulating selinux. We, us that know little, can only keep the convo going. It is, I'm not buying a nexus to get root.
we will keep it alive till then...... phone isnt dead yet still has potential i am still as happy with it as i was day one..even after 2 times rma lol. just wish it had unlocked bootloader this version of phone needed it soooo bad
read a post dom is gone from here for now he left due to mods or something so our hopes are starting to go away as he was only one as of lately even trying to work on this phone.
There are quite a few, with much more experience than Dominic on, http://androidforums.com/forums/lg-g-stylo.3133/ , that are knee deep in what is going on. We knew there would be an impasse from the beginning if using any phone with MM without having an unlocked bootloader. But at least with temp root through kingroot, and some say one-click root from here, you can alter your build.prop and de-bloat some of the google bundle. So it's not like we are completely blocked.
When kingroot starts doing MM exploits then maybe we'll be saved. Kingroot has only done root up to 5.1 Lollipop, so they either get out of the future of they're money making game or set to work to exploit it. It's the same with the boss here at XDA, @Chainfire. Without an exploit for MM on phones without unlocked bootloaders (the vast majority, I might add) supersu slows forward progress. So an exploit of sorts WILL materialize when demand (MM enthusiasts) aren't spending money at supersu and kingrootland.
Bricked my phone. Sent it off to LG yesterday. I got all carried away with altering the build.prop and root-uninstalling google apps. I had disabled the apps previous to the kingroot exploit, and decided that now with temp root I would be O.K. Well, I started getting this google service quitting popup continuously and it un-nerved me enough to do a factory reset. I foolishly forgot to at least try to clean out all the kingroot and supersu files etc that were in there, and when it re-booted I couldn't get beyond wi-fi setup as when it attempted to hook up with my google account, the dredded google services stopped popped up. Even after reset. So off to LG. They were nice at 2:30 am and that was pretty cool. I hope they don't give me grief, but it was factory reset and the temp root was gone. So fingers crossed. @[email protected] did you ever find out how to check your bootloader? It seems to me the times I booted into recovery (volume dwn/power) and chose restart bootloader the phone would just reboot. If the bootloader was unlocked would it go into the bootloader menu? That's where fastboot would come into play. Anyway I'm going to be skiddish about messing around if and when my phone gets returned, like everyone else.
jmacie said:
Bricked my phone. Sent it off to LG yesterday. I got all carried away with altering the build.prop and root-uninstalling google apps. I had disabled the apps previous to the kingroot exploit, and decided that now with temp root I would be O.K. Well, I started getting this google service quitting popup continuously and it un-nerved me enough to do a factory reset. I foolishly forgot to at least try to clean out all the kingroot and supersu files etc that were in there, and when it re-booted I couldn't get beyond wi-fi setup as when it attempted to hook up with my google account, the dredded google services stopped popped up. Even after reset. So off to LG. They were nice at 2:30 am and that was pretty cool. I hope they don't give me grief, but it was factory reset and the temp root was gone. So fingers crossed. @[email protected] did you ever find out how to check your bootloader? It seems to me the times I booted into recovery (volume dwn/power) and chose restart bootloader the phone would just reboot. If the bootloader was unlocked would it go into the bootloader menu? That's where fastboot would come into play. Anyway I'm going to be skiddish about messing around if and when my phone gets returned, like everyone else.
Click to expand...
Click to collapse
I stopped using the stylo before I even found the temp root. So I wasn't afraid to screw it up lol. Same thing happened to me that happened to you and I flashed the file Dom posted the untouched 6.0 and it worked for me. Still tinkering and the stylo has pretty much become the phone that's teaching me my way around adb .
I bought the Irulu V3 6.5 inch screen 16gb ROM and 2 gigs ram off amazon for 149 bucks..don't let the price fool you..damn good phone so far! If you're around WiFi all the time like me you can get unlimited talk text and 100mb of web at airvoice wireless for 20$. Make sure you have good at&t service where you live . Its like a sore peter,you can't beat it.
[email protected] said:
I stopped using the stylo before I even found the temp root. So I wasn't afraid to screw it up lol. Same thing happened to me that happened to you and I flashed the file Dom posted the untouched 6.0 and it worked for me. Still tinkering and the stylo has pretty much become the phone that's teaching me my way around adb .
I bought the Irulu V3 6.5 inch screen 16gb ROM and 2 gigs ram off amazon for 149 bucks..don't let the price fool you..damn good phone so far! If you're around WiFi all the time like me you can get unlimited talk text and 100mb of web at airvoice wireless for 20$. Make sure you have good at&t service where you live . Its like a sore peter,you can't beat it.
Click to expand...
Click to collapse
You mean you flashed Dominic's untouched 6.0 on top of a bricked 6.0? I maybe should have tried that.
jmacie said:
You mean you flashed Dominic's untouched 6.0 on top of a bricked 6.0? I maybe should have tried that.
Click to expand...
Click to collapse
Yea, flashed right over the top
Been ghosting on this site for a while now, but now I should really start putting my 2 cents in.
Anyways, I had the G Stylo for VM and bricked it when I tried to replace the Kingroot binaries with SuperSU ones. Ironically enough, before I did that, It seemed that my root permissions didnt stick until AFTER my reboot. When I bricked I stayed up all night trying to get my phone back but was unsuccessful seeing as I also factory reset :crying: But I just got my second phone back from Best Buy after I had issues with my sim. Gonna go try to get kingroot back on it. Any tips for me prior? Weirdest thing is that this phone came from the factory with Marshmallow.. Connect at VM told me the manufacture date was January 1st. Running Ubuntu 15.10 and am struggling to get ADB backup to save a file that has a size higher than 0 bytes..
I got my VM Stylo from Best Buy too. It came with 6.0 as well. kingroot has not worked on it at all. Maybe that's a good thing...
Sent from my LGLS770 using Tapatalk
KrYmSiiN said:
Been ghosting on this site for a while now, but now I should really start putting my 2 cents in.
Anyways, I had the G Stylo for VM and bricked it when I tried to replace the Kingroot binaries with SuperSU ones. Ironically enough, before I did that, It seemed that my root permissions didnt stick until AFTER my reboot. When I bricked I stayed up all night trying to get my phone back but was unsuccessful seeing as I also factory reset :crying: But I just got my second phone back from Best Buy after I had issues with my sim. Gonna go try to get kingroot back on it. Any tips for me prior? Weirdest thing is that this phone came from the factory with Marshmallow.. Connect at VM told me the manufacture date was January 1st. Running Ubuntu 15.10 and am struggling to get ADB backup to save a file that has a size higher than 0 bytes..
Click to expand...
Click to collapse
I had trouble with Ubuntu 15.10 as well. Having better luck with 11.4. Hope this helps
Realistically i'll just skip the backups til i get root. Any news of getting into the bootloader? My first one would go into what I believe to be bootloader mode but still wouldnt come up under fastboot unless im getting things mixed up. And what are we using to flash on this pile?
Ok more specifically I'm pretty used to the stock android experience (modded of course) but I read about that audio issue and I'm pretty terrified of it because music and calls are the main things I need a phone for. I've been out of the modded android loop since CM10 so I don't really know present day standards or processes for unlocking/rooting let alone standards for ROMs etc. Anyone got any advice?
WhenSuddenly said:
Ok more specifically I'm pretty used to the stock android experience (modded of course) but I read about that audio issue and I'm pretty terrified of it because music and calls are the main things I need a phone for. I've been out of the modded android loop since CM10 so I don't really know present day standards or processes for unlocking/rooting let alone standards for ROMs etc. Anyone got any advice?
Click to expand...
Click to collapse
just go to the guides subforum of a8 2018 and press on the thread that can help u flash twrp lol, all you gotta do is just follow the instructions word by word
WhenSuddenly said:
Ok more specifically I'm pretty used to the stock android experience (modded of course) but I read about that audio issue and I'm pretty terrified of it because music and calls are the main things I need a phone for. I've been out of the modded android loop since CM10 so I don't really know present day standards or processes for unlocking/rooting let alone standards for ROMs etc. Anyone got any advice?
Click to expand...
Click to collapse
my words of advice would be to make sure that you need root before you root it. what i mean by that is think about what you stand to gain by rooting it vs the PITA it is to root this thing. Pay close attention to the 168 hour thing as its been a thorn in many a persons side and caused many a headache. Ive had dozens of android phones and all have been rooted with the exception of the HTC Rezound, which required the OMG PITA "wire trick" to root properly. These phones run very well as stock and dont have much bloatware, so rooting them is becoming less necessary. I got mine in july '18 and have been happy with its performance overall so far. Ive reflashed the stock tar.img a few times for varying reasons, and even rooted it. But after losing SPay capability with root, i flashed back to stock as the gains werent worth the losses to me. Also, SHealth is a task to get working after you trip knox btw.
youdoofus said:
my words of advice would be to make sure that you need root before you root it. what i mean by that is think about what you stand to gain by rooting it vs the PITA it is to root this thing. Pay close attention to the 168 hour thing as its been a thorn in many a persons side and caused many a headache. Ive had dozens of android phones and all have been rooted with the exception of the HTC Rezound, which required the OMG PITA "wire trick" to root properly. These phones run very well as stock and dont have much bloatware, so rooting them is becoming less necessary. I got mine in july '18 and have been happy with its performance overall so far. Ive reflashed the stock tar.img a few times for varying reasons, and even rooted it. But after losing SPay capability with root, i flashed back to stock as the gains werent worth the losses to me. Also, SHealth is a task to get working after you trip knox btw.
Click to expand...
Click to collapse
Yeah tbh I'm ok with the interface now and aside from making the volume buttons change tracks when you hold them down the only things id need root for is clearing out bloatware etc. I think I'll take your advice and not root it for now (until something breaks) but what is this 168 hour thing?
WhenSuddenly said:
Yeah tbh I'm ok with the interface now and aside from making the volume buttons change tracks when you hold them down the only things id need root for is clearing out bloatware etc. I think I'll take your advice and not root it for now (until something breaks) but what is this 168 hour thing?
Click to expand...
Click to collapse
there has been a great deal of discussion about how to get the OEM unlock toggle to show up in the developer options, many suggest that its only obtainable by leaving the phone powered off for 168 hours and then rebooting, not connecting to any network (including cellular) and then enabling developer options and then the toggle should be there.
youdoofus said:
there has been a great deal of discussion about how to get the OEM unlock toggle to show up in the developer options, many suggest that its only obtainable by leaving the phone powered off for 168 hours and then rebooting, not connecting to any network (including cellular) and then enabling developer options and then the toggle should be there.
Click to expand...
Click to collapse
Your wrong your suppose to keep phone on for 168 hours no reboots then oem should show up again.
mchlbenner said:
Your wrong your suppose to keep phone on for 168 hours no reboots then oem should show up again.
Click to expand...
Click to collapse
youre*
and youre correct, i said it backwards.
youdoofus said:
there has been a great deal of discussion about how to get the OEM unlock toggle to show up in the developer options, many suggest that its only obtainable by leaving the phone powered off for 168 hours and then rebooting, not connecting to any network (including cellular) and then enabling developer options and then the toggle should be there.
Click to expand...
Click to collapse
So wait. My phone is showing the OEM unlock toggle and I can change it. Does that mean I can root? Or would trying to root then make me wait 168 hours? I never tried any custom stuff with it btw. Just bought and installed Lawnchair lol.
Amirk365 said:
So wait. My phone is showing the OEM unlock toggle and I can change it. Does that mean I can root? Or would trying to root then make me wait 168 hours? I never tried any custom stuff with it btw. Just bought and installed Lawnchair lol.
Click to expand...
Click to collapse
Hit the toggle and it'll ask for your pw, then you can flash a custom recovery via Odin
Amirk365 said:
So wait. My phone is showing the OEM unlock toggle and I can change it. Does that mean I can root? Or would trying to root then make me wait 168 hours? I never tried any custom stuff with it btw. Just bought and installed Lawnchair lol.
Click to expand...
Click to collapse
be careful with starting down the root rabbit hole tho. if you flash anything in download mode, youll trip the knox security counter and that is 100% irreversible without sending it to samsung. Root is cool and allows you to do stuff, but honestly ive not found too much reason to root this phone yet. Ive literally had over 20 android phones and i rooted and modded all of them (except the rezound, if you want to know why that one wasnt fully rooted, just google "rezound wire trick" and youll see) and this one just really doesnt need root IMO. Sure it would be nice to have a few root things, but its not worth the trade off of losing samsung pay so i can pay for stuff with my watch. That feature is just waaaay too valuable to me
youdoofus said:
be careful with starting down the root rabbit hole tho. if you flash anything in download mode, youll trip the knox security counter and that is 100% irreversible without sending it to samsung. Root is cool and allows you to do stuff, but honestly ive not found too much reason to root this phone yet. Ive literally had over 20 android phones and i rooted and modded all of them (except the rezound, if you want to know why that one wasnt fully rooted, just google "rezound wire trick" and youll see) and this one just really doesnt need root IMO. Sure it would be nice to have a few root things, but its not worth the trade off of losing samsung pay so i can pay for stuff with my watch. That feature is just waaaay too valuable to me
Click to expand...
Click to collapse
If his oem is showing and if he marks it and follow the directions he will be fine I have been rooted since day one of having it.
I never got locked out.
mchlbenner said:
If his oem is showing and if he marks it and follow the directions he will be fine I have been rooted since day one of having it.
I never got locked out.
Click to expand...
Click to collapse
ill never trade my SPay on my watch for root
youdoofus said:
be careful with starting down the root rabbit hole tho. if you flash anything in download mode, youll trip the knox security counter and that is 100% irreversible without sending it to samsung. Root is cool and allows you to do stuff, but honestly ive not found too much reason to root this phone yet. Ive literally had over 20 android phones and i rooted and modded all of them (except the rezound, if you want to know why that one wasnt fully rooted, just google "rezound wire trick" and youll see) and this one just really doesnt need root IMO. Sure it would be nice to have a few root things, but its not worth the trade off of losing samsung pay so i can pay for stuff with my watch. That feature is just waaaay too valuable to me
Click to expand...
Click to collapse
Thanks for the advice,but this isn't my first rodeo with Samsung lol. I messed around with the Verizon S5 alot and was lucky to have the version able to unlock it's bootloader.
Amirk365 said:
Thanks for the advice,but this isn't my first rodeo with Samsung lol. I messed around with the Verizon S5 alot and was lucky to have the version able to unlock it's bootloader.
Click to expand...
Click to collapse
np, the G900V was a major disappointment with its locked bootloader. i recall spending several hours bricking one and having to restore it with the stock tar.img file. total PITA
youdoofus said:
np, the G900V was a major disappointment with its locked bootloader. i recall spending several hours bricking one and having to restore it with the stock tar.img file. total PITA
Click to expand...
Click to collapse
Will you stop telling people that you will mess up phone if you try to root it.
If people follow directions they have nothing to worry about.
You where bootloop not bricked a brick device is usually a unfix able.
If is fine you what to keep Sam pay but your info you are telling is wrong.
I recently unroot my phone guess what Sam pay work fine.
Then root phone again no lock out and enable treble and flashed gsi image.
So their nothing wrong with rooting if you want to do that.
mchlbenner said:
Will you stop telling people that you will mess up phone if you try to root it.
If people follow directions they have nothing to worry about.
You where bootloop not bricked a brick device is usually a unfix able.
If is fine you what to keep Sam pay but your info you are telling is wrong.
I recently unroot my phone guess what Sam pay work fine.
Then root phone again no lock out and enable treble and flashed gsi image.
So their nothing wrong with rooting if you want to do that.
Click to expand...
Click to collapse
dude, i dont think youre reading what im saying right. Ive never said that rooting your phone will mess it up. the stuff about the G900V is a DIFFERENT PHONE. FFS. This isnt my first rodeo rooting and modding. Hell, i even was writing mods back in the Evo and S3 days. Im refamiliarizing myself with some of this, but i havent ever said youd mess your phone up if you follow the root instructions. Ill even go as far as saying as long as you dont Odin flash the tar.img for a completely different phone, these things are virtually impossible to hard brick. And yes, a bootloop is referred to as a soft brick. But, it is important to know that if you do root your phone, it WILL make samsung health not work as it did when stock and there is NO WAY of bringing it back without swapping the motherboard
youdoofus said:
np, the G900V was a major disappointment with its locked bootloader. i recall spending several hours bricking one and having to restore it with the stock tar.img file. total PITA
Click to expand...
Click to collapse
Unlocking the bootloader was completely dependent on the type of EMMC chip that the G900V that you had was using. I got three of those and only one was able to unlock after the Marshmallow update.
Amirk365 said:
Unlocking the bootloader was completely dependent on the type of EMMC chip that the G900V that you had was using. I got three of those and only one was able to unlock after the Marshmallow update.
Click to expand...
Click to collapse
the last tinkering i did with the G900V was several years ago and that was at the point when all hope was lost on the locked bootloader. I havent looked into it since as the G900's i had were G900P's which were FAR easier to work with. I did also root and ROM a couple G900VL's, but again was years ago
youdoofus said:
the last tinkering i did with the G900V was several years ago and that was at the point when all hope was lost on the locked bootloader. I havent looked into it since as the G900's i had were G900P's which were FAR easier to work with. I did also root and ROM a couple G900VL's, but again was years ago
Click to expand...
Click to collapse
Good times. Anyways I'm not rooting for now. Waiting for Pie and see how it goes.
Amirk365 said:
Good times. Anyways I'm not rooting for now. Waiting for Pie and see how it goes.
Click to expand...
Click to collapse
good times, yeah LOL!!! major waste of time on those friggin G900V's is more like it yeah, i wouldnt root yet, keep the stock recovery so it automagically updates to pie in a few weeks and manually check for updates every so often to force its hand. Also sammobile.com posts them too if you want to force it on via Odin and trip knox. Anyways, if you get the update in the near future, let us know!