My (Sloppy) Verizon S7 Root Effort Needs Correcting - Samsung Galaxy S7 Questions and Answers

EDIT: I've since gone through the motions again using these instructions and all went smoothly, though I'm still left with the bizarre icons despite having followed the instructions mentioned below. I also now understand that the fingerprint system coincides with Samsung Pay, so no-harm-no-foul.
Hi all.
I've probably been out of the root game a little too long. I only root when a replacement phone hits my hands. Recently, my "perfected" S5 took a spill (cracked glass + water damage to charger port) and now I'm rockin' a VERIZON S7 (SM-G930V).
I weighed the root pros/cons as well as my own patience to get it right before opting to do so. Now, I'm left with a phone that is rooted but, well ... a bit on the janky side. I'm hoping the experts here can help me correct/bolster it's behavior.
About my phone: bought yesterday, updated to Nougat, Verizon carrier.
Here are the bullet points as to what steps I took and the result:
Googled around with what care I could to avoid anything shady.
Found a popular XDA thread with "something something auto-root blah" that failed with download mode security message of "recovery" (on the phone's screen).
Moved on to jusmejose's instructions via Google before learning of his championship in the effort.
In following his instructions, the phone FIRST rebooted to recovery but displayed a "no command" error, or something to that effect. It eventually booted into recovery mode but I've no idea if that recovery was his install or not.
Found that many of his "now do this in recovery" menu selections weren't present, such as install->filename and the like.
Went on with his instructions to install the ENG file. Odin: Passed!
Couldn't get SuperSu to my phone ... oops ... not installed so lots of "insecure actions detected" or whatever it was.
Sifted through the information on this page and made use of it's files where possible, LAYERING THE ROOT EFFORT ON TOP OF WHAT I'D ALREADY DONE with jusmejose's information by way of root_with_tweaks, thinking that would remedy the volte + hurricane icons (it doesn't)
... so, here's where I'm at (more bullet points)
I have root.
SuperSu is now installed and working.
I attempted the ADB push fix from this page to remedy the menu bar icons. ADB went through but they're still there.
Fingerprint no longer works.
SetCPU (my goto cpu governor app) doesn't work.
I'm a little in the dark about the stability based on my perhaps bizarre Frankenstein effort.
I'm absolutely, 100% fine with starting from scratch so long as it's all coming from one source that's stable and ready to rock AS OF THIS POST DATE (phone updated to Nougat on May 24, 2017 before rooting).
I wouldn't mind having a custom rom installed, either but the only one I found appears to be from T-Mobile (?)
What would you more experienced fellows recommend I do to "really get this right" and via which threads?
Regards.

Related

[Q] Cannot pass a welcome screen (G tablet)

Cannot pass a welcome screen
I just got my GTablet. Power it up first time and it did not ask me for any setup (no welcome screen and agreement acceptance). I played couple minutes and power it down (have no time).
So now I powered it again and did get the welcome screen (surprise ) but after I select “Agree” with a agreement and press next – I got message “application unexpectedly foreclose, please try again” . And I tried many many times but I cannot pass this message.
Can some one help me? Should I return it right a way?
gtab_11 said:
Cannot pass a welcome screen
I just got my GTablet. Power it up first time and it did not ask me for any setup (no welcome screen and agreement acceptance). I played couple minutes and power it down (have no time).
So now I powered it again and did get the welcome screen (surprise ) but after I select “Agree” with a agreement and press next – I got message “application unexpectedly foreclose, please try again” . And I tried many many times but I cannot pass this message.
Can some one help me? Should I return it right a way?
Click to expand...
Click to collapse
Depends, If you are adventurous, you could download and re-flash back to stock using any one of several posts that detail re-flashing youre tablet (Look for NVFLASH BACK TO STOCK), if not then I would return it.
In any case, once you have a working unit, you will most likely want to replace the stock ROM with one of the updated roms that the developers on this forum have created. There are FROYO, GINGERBREAD ROMS that are very stable and fully functional. There are a couple Honeycomb ROMS that are in alpha stage.
Spend some time reading thru the threads before you make a decision and good luck
Look at this POST for re-flashing your tablet back to stock. READ the entire post before trying!!!
http://forum.xda-developers.com/showthread.php?t=861950
http://forum.xda-developers.com/showthread.php?t=865245
Or look here^^^^ for a great guide to flashing a better os.
Thank you folks, I am kind uncertain about refreshing my gtablet with custom rom before having fully functional original one.
what do you think is it safe ?
any ideas why original one crashed on set-up screen? does anyone had this type of issue?
thanks in advance.
gtab_11 said:
Thank you folks, I am kind uncertain about refreshing my gtablet with custom rom before having fully functional original one.
what do you think is it safe ?
any ideas why original one crashed on set-up screen? does anyone had this type of issue?
thanks in advance.
Click to expand...
Click to collapse
Nearly everyone had this problem right out of the box: http://forum.xda-developers.com/showthread.php?t=896395
Clear all the FC dialogs, set up your wifi network, download the OTA update to 3588. After that's applied you will have a much more stable machine.
Ok, it looks like I solved it. And the issue was – NO WIFI access at the time!!!
I am going to explain as I have understood it (may not be the case but I am quite confident) helpfully it will be useful info for others.
First when I got my gtab I powered it up and did not get any “welcome screen” (where you are agree with a user agreement and set time and location as well as set up accounts). So I played with it a little bit (set-up WIFI) and powered it off. So next time when I have powered my gtab up I was in a different location with no WIFI available. And this time a get “welcome screen” but when I tried to complete the “welcome screen “it crashed (and I believe because it require access to internet). And until I get to the first location I could not pass “welcome screen”! BUT as soon as I get to the location with WIFI, everything went fine!

[Q] boot loop on inspire after set cpu

Hello...
I'm a newbie to modding phones (obvious from the question/problem I've about to ask). I have an HTC Inspire and I followed the one click rooting guide and installed Coredroid7 with the 3rd set of radio/RIL listed in that thread. With a bit of a struggle I got it working - worked great and I loved it. Unfortunately I found on the market place an app (Overclock Widget by Billy Cui ) - clicked on "load on boot" and a few bad settings and the entire phone froze. Since then whenever I boot my phone is stuck on the white screen with green HTC logo. The config on my phone is:
s-off
hboot 0.85.0019
micop-0438
radio 26.09.04.11_m2
emmc boot
I've googled all of the internet and followed advice such as reflashing the radio/RIL. went into recover and typed the "adb shell, etc... to remove files indicated (but they were not there)". tried to do recover but the recovery files werent there. At this state, there is only so many combinations you can do and I feel I have done it all.
there are a lot of advice on set cpu problem with other HTC devices but none of them work/can be applied to the Inspire.
Can someone please help me? In your answer please answer me in a dumb down way - keeping in mind I am new and have a hard time understanding acroynms and how to perform complex operations with the hint of a word phrase (ie - please be explicit for me on how to flash radio, instead of saying flash radio XYZ)
Thanks in advance
PS: I am already nervous/scared of what has happened, I am hoping I don't have to do a eng s-off as part of the solution please
based on my description (white screen with HTC logo) have i bricked my phone or is it in a boot loop?
i tried the following
http://forum.xda-developers.com/showthread.php?t=1033353
and when i say install PD98IMG.zip it just says installation aborted. This is the image I got from Coredroid7 that was working before the problem started.
also tried this:
http://forum.androidcentral.com/lg-...cks/50301-setcpu-forgot-uncheck-set-boot.html
but my phone does not have the file they wanted me to delete
If you see the white HTC logo your always okay. The problem comes when there is nothing showing, you must have changed some settings that won't let the phone complete some core processes.
This can easily be fixed by pulling battery hold volume down button and power and booting into Hboot. Then go into recovery factory reset and wipe dalvik_cache(under advanced) and flash the desired ROM or do a restore from a point your phone worked perfectly.
Sent from my Inspire 4G using XDA Premium App
ThEiiNoCeNT said:
If you see the white HTC logo your always okay. The problem comes when there is nothing showing, you must have changed some settings that won't let the phone complete some core processes.
This can easily be fixed by pulling battery hold volume down button and power and booting into Hboot. Then go into recovery factory reset and wipe dalvik_cache(under advanced) and flash the desired ROM or do a restore from a point your phone worked perfectly.
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
First... THANK YOU very very much for telling me it is not as bad as it seems.
I have done the following:
go into hboot
recovery option
wipe dalvik
flash coredroid7 again by having it be embedded in PD98IMG.zip however like mentioned above this fails.
Right now I am redoing the process again by formatting my sdcard, creating /download to put the PD98IMG.zip in follow the procedures again above. In case this fails, what are my options?
thanks for the guidance. i flashed it again with:
CoreDroid_Desire_HD_GB_2.3.3_V7.0_RV
and I am out of the white screen mode.
Just remember if your phone boots up but not all the way its still ok you can save it. The easiest although most annoying solution is reflash the rom. Also i know you hear about people bricking there phone. I truly think its harder than anyone thinks. Good luck with the inspire. Also if you want overclocking/underclocking stick with setcpu(you can get it free for being an xda member just search xda). Let it auto detect speeds. Give it root permission (itll pop up asking make sure you check remember above the allow button). If your overclocking I recommend staying undler 1.6 ghz (1600 on setcpu) and go to profile select enable. Then set up a profile for screen off and set it for around 300 mhz to help with battery life.
Carlrobling said:
Just remember if your phone boots up but not all the way its still ok you can save it. The easiest although most annoying solution is reflash the rom. Also i know you hear about people bricking there phone. I truly think its harder than anyone thinks. Good luck with the inspire. Also if you want overclocking/underclocking stick with setcpu(you can get it free for being an xda member just search xda). Let it auto detect speeds. Give it root permission (itll pop up asking make sure you check remember above the allow button). If your overclocking I recommend staying undler 1.6 ghz (1600 on setcpu) and go to profile select enable. Then set up a profile for screen off and set it for around 300 mhz to help with battery life.
Click to expand...
Click to collapse
I think I've had about every kind of soft boot thre is on the sticky guide, and one that isn't, and I have always been able to recover (knock on wood). Even black screens...
I was stuck in a similar situation once:I forgot to take off "load on boot" and increased the max speed all the way to like 1.9. And phone froze.
SetCPU gets permissions in the process of phone boot up, after the whole OS is loaded. There is a tiny time gap between home screen coming up, and SetCPU being granted SU permissions. So this is what I did:
I did a reboot. And after the phone starts, without giving any time opened the app drawer for "SuperUser" app, and took off SetCPU permissions from there. This denied SetCPU of it permissions and it was loaded at default speeds. Then I went into Settings-->Applications, and erased all SetCPU data.
Well, it took me like 3-4 reboots before I could master the timing to get to SuperUser and take off SetCPU from there. But it atleast saved me the hazzle of reflashing everything again. And yes sir, I forgot to take a nandroid backup
thanks
Thanks All
Problem fixed
same issue only worse
I have the same situation. I flashed absolution 2.0 last night. Everything went good. Turned it on this morning seemed to work fine also then I turned it off for work and tried turning it back on at the end of the day and it just runs a loop. I can get to the HBOOT menu but I only have 5 options; fastboot, recovery, factory reset, sim lock, and image crc. There is no advance settings and when I choose any of the available options nothing happens except the phone reboots (crc does run a check but then nothing). Hooked to my pc and it says found android 1.0 but I can't do anything with it. I have also pulled the battery and sims card.
freedompc said:
I have the same situation. I flashed absolution 2.0 last night. Everything went good. Turned it on this morning seemed to work fine also then I turned it off for work and tried turning it back on at the end of the day and it just runs a loop. I can get to the HBOOT menu but I only have 5 options; fastboot, recovery, factory reset, sim lock, and image crc. There is no advance settings and when I choose any of the available options nothing happens except the phone reboots (crc does run a check but then nothing). Hooked to my pc and it says found android 1.0 but I can't do anything with it. I have also pulled the battery and sims card.
Click to expand...
Click to collapse
What happens when you select recovery and press power?
It just turns off and starts back up and runs its loop. Same for fastboot and factory reboot.
Go here, I've already informed attn1 and his group that you'd be coming.
Going to the link.
They'll get ya fixed up.
Thanks TX. Those guys on that site were awesome. Attn1 worked with me for over an hour. Unfortunately, my phone itself has a hardware failure. Never the less, GREAT support. I wish there was a thank you button for them. This was my first android phone (lasted 3 months) and b/c of the DEV's and other members it won't be my last. Just hope the next one lasts longer.
freedompc said:
Thanks TX. Those guys on that site were awesome. Attn1 worked with me for over an hour. Unfortunately, my phone itself has a hardware failure. Never the less, GREAT support. I wish there was a thank you button for them. This was my first android phone (lasted 3 months) and b/c of the DEV's and other members it won't be my last. Just hope the next one lasts longer.
Click to expand...
Click to collapse
Dang man, that sucks. I can honestly say I've never had a device fail like that.
Good luck on your next device, whatever it may be.
Tx
Disregard... posted in error
sent from my secret agent phone in my shoe

Zoom stuck in perpetual Boot Animation, but will load to Start Screen

OK Guys, I don’t like to bother you until I have already tried everthing I know how to try. The error and solution should hopefully become quite apparent to you once I explain, as you experts are far more knowledgable regarding Android than I will probably ever be.
I am a long time coder and IT manager, with a Bsc in Computer Science back in the early 90‘s, probably before a lot of you were born, sadly for me.....but, as I am sure you can relate, most of the errors I have run into are self inflicted because I HAVE to try the newest Rom, the Newset Kernals, the Newest tweats, Loaders, Launchers, Beta programs, even worse, ALPHA testing, etc, etc and I have wiped and rebuilt so many times it’s sickening.Factory resets, for me, are an ABSOLUTELY LAST RESORT, as I have my tablet set up for my Business Network(s), my home business network, my home entertainment network, multiple VPN’s, and a few custom apps that I had to write myself as there are none out there that do EXACTLY what I need them to do, so doing a Factory Reset is a very large undertaking, and even with Nandroid and other backups, I still have to spend days reconfiguring, initializing, and debugging (basically juggling to get them all to work in a semi harmonious configuration!)
Tablet: Motorola Xoom WIFI MZ604
Rom: CM-10.1-20130605-Nightly-Wingray.zip
Kernal/Loader: TWRP_2.5_RedLacE_Mjamocha_Theme.zip
Launcher: SPB-1.6.4
Fortunately, or at least I hope, this problem is a little different:
Everything has been running perfectly for more than a couple months. I have had no installation issues with other apps, no gliches, no delays, no slowdows, no anything. I wanted to reboot into recovery to do a Nandroid backup, since I hadn’t done one in more than a month. When I pressed the power button for my reboot options, I noticed, for the first time, an option that said “Desktop” (normal). Of course, curiousity getting the better of me, I tapped it, and it switched to “Desktop” (extemded. or Enhanced, I am not sure exactly which one). As soon as I changed that, my Xoom IMMEDIATELY jumped into the Cyanogen Boot Animation. It stayed in that state for about triple the time it normally does on boot, but eventually the main start screen came back up, so I tried to unlock the screen and return to what I was doing. Unfortunately, as soon as I touched the screen, it once again IMMEDIATELY jumped back to the Boot Animation. So I rebooted again, leaving it long enough so that Circle, a program that can act as a screen saver, among other things kicked in, so I thought I was OK. All I wanted to do was hold the power button down long enough to bring back up my power menu, but, alas, LITERALLY, the second I touched the power button.....BAM, back into B.A. No matter how long I left it, no matter what I have tried, always immediately back to the B.A.
Now, I have Full access to all files from Root Up, and can edit or delete any of them, so, logically, there has to be a configuration file that stored this Desktop Enhanced selection, which, by my logic, is about 99% chance of being the cause of this current issue. I believe the option is part of the SPB launcher, but could be wrong, since I have instaled a couple programs that add options to the reboot menu, however, I really do believe that it’s from the SPB Launcher.
ANYTHING that ANYONE of you would be able to do to assist me in fixing this WITHOUT haveing to do a factory reset and restore, would leave all of you forever in my debt.
Thanks so much in advance, and, though I will be checking the posts frequently, feel free to email or PM me.
Regards, Jason
(Sorry for the length!!!)
Sent from my SGH-I827D using xda app-developers app

[BUG][6.0.1 Stock]Home Button Ignored and Other Perfidious Symptoms

This mean bug hit us twice, so that it might be helpful do document it in order to help other persons with the same problems.
Symptoms:
Home button does no longer work.
Notifications and notification pulldown menu do not work (as consequence, data transfer via USB cable is impossible).
Quick settings do not work.
Factory reset does not work.
Developer mode cannot be enabled (as a consequence, no adb connection possible).
Automatic orientation disabled after every reboot.
Mobile data enabled (!) after every reboot (very funny if you pay 0,23 EUR per megabyte and do not notice...)
When changing volume using the physical keys, the device sometimes reboots.
This list is not necessarily complete, as there might be more symptoms.
According to various investigations (see links below) the system thinks that the Setup Wizard is still running. This bug presumably was introduced with some Android version (Oct 2015), came to the Moto G, and when the bug was removed, the Moto G did not get the corrected OS version.
When does the problem appear?
There are strong indications that the problem always occurs whenever the device runs out of (flash) memory. Note that our device did not have an SD when the problem appeared.
How can one heal the device?
There have been some recommendations how to repair the phone (see links below):
Change user
Run the SetupWizardTestActivity via adb
Run some additional command (see below) via adb.
Run the SetupWizardTestActivity via Nova Launcher.
Factory reset via Recovery.
What did really help?
In fact all methods 1 .. 4 failed, because no adb connection could be established (see Topic 5. of the symptoms), and the Setup Wizard got to an endless loop when I started it via Nova Launcher. So finally I used the Recovery system to reset the device.
If anybody ran into the same trap or has a better solution, please tell!
See also:
http://forum.xda-developers.com/2015-moto-g/help/moto-g3-properly-t3449495
http://forum.xda-developers.com/2015-moto-g/help/status-notification-bar-pull-t3435441
http://forums.androidcentral.com/an...me-button-not-working-many-more-problems.html
http://forums.androidcentral.com/mo...sing-huge-problems-moto-x-2nd-gen-2014-a.html
http://infomash.net/home-button-not-working-after-updating-to-android-marshmallow/
How to reset the Moto G
Reflash stock image via fastboot... if it continues to fail and you followed all instructions EXACTLY, your handset is defective, get it repaired or replace it.
The "setup wizard" bug is a known, but extremely rare, issue... but the symptoms are not the same as what you are experiencing. Home/Back/Recent buttons do not work -AND- the notification pull down do not work, in every case reported simply re-running setup wizard corrects the issue.
symptoms same , root reason may differ
Tenebrous sound thy words, and partially enigmatic is their meaning.
In fact:
- I forgot to mention the non-working notification pulldown menu, so I added this in post #1.
- Thus the noticed symptoms exactly match those described in the links I provided.
- However, the root reason might subtly differ, and, additionally, all proposed therapies except factory reset failed in our case.
- It might help to re-flash the stock or flash an alternative image to cure the device, but it was not necessary in our case, so it's not really a better solution.
I found this Lenovo Moto G3 forum dealing with the same problem:
https://forums.lenovo.com/t5/MOTO-G...cations-and-lock-screen-not-work/td-p/3255406
Post #9 mentions "my storage was running out".
Here is another one, for a slightly different device:
https://forums.lenovo.com/t5/MOTO-X...on-notifications-lock-screen-not/td-p/3354948
hey to chime in, I've got the same situatrion as of a few days ago on my Motorola Droid Maxx 2. WISH I could find a root exploit for this damned thing. I hate dealing with issues on it. Who has time for this garbage? I plan to do a factory reset (or try while expecting a failure as noted in original post here.)
Thanks for documenting your issue Ahkah as it at least has helped me feel OK about myself here. Excellent choice of wording. To the other poster, why do you speak so authoritatively to say that if _____, phone is defective? That's annoying and not true unless somehow here at android-is-still-interesting.com "defective phone" means "I dont know what happened."
What I have in common to your described condition:
- ran "low" on storage according to pop up.
- used some feature offering to "clean" hard disk or whatever. This may have been in FX file browser or else a native android feature or else a motorola app feature. Unfortunately dont recall. One of the few options it gave was to clear cache of all apps. Seemed risky to me but I hit it any way. This may have been the root cause.
- notification pull down reads only "no notifications."
- circle and square softkeys do nothing but give the visual feedback or sometimes vibration feedback that acknowledges the button press.
- pulling down from top of screen while bnotification area is already pulled down does nothing whereas normally it would open quick actions.
- searching /system for "wizard" comes back with a lot of results for apks, all of which do nothing, throw error, or install more of themselves.
- clicking developer options tells me that dev options are not available for this user. As far as I can tell there are no other users on my phone.
- clicking build number or whichever item in about phone multiple times to enable dev options does nothing.
- volume buttons to act funky and while fiddling with the phone that was one of the few things i was doing. simultaneously the phone was repeatedly rebooting. maybe correlated but i dont know i was messing with everything i knew to try.
Additional observations:
- phone takes a long time to boot up on some power off/ power ons.
- phone largely works if i could somehow ignore all the above.
- phone sometimes reboots mid-boot animation
- all above is observed after freeing up 3 gb on internal memory and i've had multiple gb free on sd card throughout issue.
I hate you motorola. I hate you google. I hate you verizon. I hate you CIA and NSA. I hate you United States. I hate you capitalism. I hate you imperialism. I hate you western world. I hate you ideology. I hate you technology. I DONT EVEN WANT A PHONE and this is how i get to spend an hour today.

Issues with the Android Pie Update (Google Play Store and Camera -> Gallery App)

Hello everyone!
Today I updated my HTC U12 + (128GB) to the Android Pie version (9.0):
First I received an update of approximately 350 MB, which was downloaded and installed without any problem, the cell phone restarted without any problems (I clarify that my cell phone is encrypted and when it restarts, ask for a password to continue with the restart). For now everything is going well.
After a while the main update was downloaded (950 MB approx) and I had it installed as soon as the download was finished.
Again the cell phone restarted, he asked me for the password to decrypt it, but after that, it went completely black, he did not advance anything else for several minutes. Amid the panic, fear and despair, I pressed the power button to restart the cell phone, asked for the password again, and apparently charged the rest of the installation.
When I went to use the Camera application, the option thath appears in the lower right corner to see the last photos taken (like a gallery) is not working well, the application crashes and is not letting me see the photos taken. (Here goes the first problem).
Another problem I have is with the Google Play Store app: It doesn't allow me to download apps from the store, as if it were locked or something like that. (Here goes the second problem).
Now, the main problem is: Like any good engineer, any problem can be solved with a reboot to see if everything loads well, but I already tried and it didn't work. And following the good traditions of the good engineer, it can be said that I do a hard reset (erasing all the settings and content of the cell phone, which I also consider an effective solution, I will not deny it), but currently I am outside the country where I have hired My phone number, and for work I need WhatsApp (and as you know, I need a text message with the code to login), and I have no way to activate Roamming.
Can anyone help this good citizen with any advice, trick, recommendation or magic spell that does not involve formatting the phone and solving these problems?
Thanks!
PD: A friend with the "same" model (64GB) had no issues with the instalation, and we compared the camera version number, and everythings is the same.
Delete camera and gallery data in settings and reboot. If that don't work do a factory reset... Sometimes after an update it is necessary to delete old caches that get stuck
dioggo92 said:
Delete camera and gallery data in settings and reboot. If that don't work do a factory reset... Sometimes after an update it is necessary to delete old caches that get stuck
Click to expand...
Click to collapse
I have already deleted the cache of the applications with problems, but it still does not work properly.
Thanks for your answer and support with this.
(Until I can return to my country, I cannot do the hard reset... sadly)
no issues here since yesterday evening
So far it's great, very smooth, phone (64GB blue on TMO US w/ 128GB SD) is faster & battery life seems to have improved a lot though it's only 1PM here so we will see...
Upgrade went the same way like yours except I waited patiently to come back from the "blackout" after the decryption was done, thanks for the heads-up (though I usually wait a while anyway.)
UI is a tad more responsive - I have a lot running on my phone, I use it heavily for business all day long.
I like the clock's new location in the upper left corner actually more than the previous one - however the new UI design is a too bubbly and too colorful, too 'pop' for my taste, the previous one was far more elegant, I think. I will give it some time, see if I get used to it - if not I will just look up some more subtle theme.
I only had to re-apply my notification sound setting, everything else was kept intact so it's all good.
All in all I'm satisfied so far, very smooth upgrade - it did worth the wait, thank you HTC!

Categories

Resources