Help Needed - Pixel 4 - No WiFi+Data after update - Google Pixel 4 Questions & Answers

Hello everyone. I recently purchased a used Pixel 4. Past owner said WiFi+Data stopped working after updating Android and that the phone is unlocked and carrier-free. I need to unlock bootloader in order to install GrapheneOS but it is greyed out. As you can see in the screenshots, it seems like the phone is not recognizing WiFi and IMEI hardware while booted. IMEI does show up in the barcode menu option in fastboot. System UI crashes if I try to open WiFi config. The only thing I could try was tethering via Bluetooth from my other phone and updating Android OS and apps. Already tried wiping everything and forcing phone to connect to Google while on Bluetooth tethering by pressing (*#*#2432546#*#*) in the dialer as sugested here: https://source.android.com/setup/contribute/flash#preparing-your-device
This doesn't show any success or error message.
One thing that may have happened is this: https://www.phonearena.com/news/google-pixel-android-12-verizon-update-issue_id136367
Apparently Google sent OTA Verizon update to unlocked Pixel 4's by mistake. Maybe the wrong software is what is making it not recognize WiFi+Data?
Current installed build is 12.1.0 (SQ3A.220605.009.A1, Jun 2022). Maybe I should wait for a new SP* instead of SQ* build to come out and try installing it? This is because P is for the main platform branch as explained here: https://source.android.com/setup/start/build-numbers#build-ids-defined
Hopefully it comes out before October since that is the end-of-support date.
OTA builds: https://developers.google.com/android/ota#flame
Other option would be to try out this but it seems the riskiest and last resort option:
Unlock carrier locked bootloader Pixel [BETA]
UPDATE AS OF 16 OF MAY 2023 This project isn't working right now, but I am still working on it. However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get...
forum.xda-developers.com
And yet another option would be to purchase a new board and replace it.
What do you think? I tried submiting the IMEI to T-Mobile's site and it says it is OK to be ported. Verizon's site didn't let me submit the IMEI I don't know why. And for AT&T I didn't find any site for that. IMEI checks say it is not blacklisted.

Did u solve this?

Related

[Bounty]Kin brick recovering / OS flashing

Hi everyone.
I'm bit tired of having the phone being just placed over the table without doing anything (it's on the "updating modem..." state)with it, and no one seems to "seriously developing" for it, so here it goes.
I'm offering a real cash for solutions to it.
The bounty goes on two options (mutually exclusive, so if one is done, the other is cancelled):
Description
Option A: Solve my factory mode "brick"
Prize: 50€ (~70$)
I must get my phone unbricked with some software program, so i can recover some time to try to hack the mtpz protocol and so on.
There is no need to get a new OS on the device,as the kin default it's ok.
Option A.2: Get a bypass for "Updating modem" screen from Verizon
Prize: 25€ (~35$)
Mmm just a way to bypass the "Updating modem" screen over the phone, called "OTA update" from verizon radio by hotkeys or software (both are ok).
Option B: Get a OS on the device
Prize: 100€ (~141$)
Get the above done by flashing a new OS or a winCE-like (or android, or X), so i can have my phone back and also enjoy a new OS there.
Carrier software does not matter.
Payment
Payment would be done only through PayPal, so the guy/gal solving this must provide or have a destination PayPal address.
Payment would NOT be done if the requirements specified below are not met. Specially if my phone doesn't work after the end of one of the options.
Currency conversion would be done on paypal automation conversion OR if donation / transaction is in dollars, it would be done on the google €->$ conversion rounded to floor (so 100,9$ is 100$ and 100,1$ is also 100$).
Solutions would be tried on a first got first processed option so if i get an option B solution before an option B (or the opposite), the first one working OK would get the cash, even if the other is better.
My own main purpose here is to get my phone operative again.
The above means that if Option A solution is met, Option B is CANCELLED and the bounty is FINISHED. Same for option B.
Rules for the options
General
I can't be waiting forever so i give a month timelapse from the posting date, so this ends on April 21th.
I have no access to 64 bits hardware, so all the 64 bits software is not accepted.
I can't and wont access CDMA networks, so not able to get Verizon update OTA to fix the "modem updating" problem.
I do not, repeat do not need any of the verizon / carrier options, so the software or roms can just not have it as I don't care. As long as the phone boots on it and can have wifi & usb connections(and GPS optionally) i'm fine with it.
Software (if available) will be sent together with instructions and detailed. I'm a developer and "advanced" PC user, but i may not know all the steps in mobile flashing just by opening a program.
Solving person may be from outside here, as long as it's available by forum rules and so on. So if you know a mobile guy wizard, you can tell this.
Software SHOULD be sent to me before paying (obviously) to test the solution to either option. If the author wants it that way, the software could be posted publicly to the masses AFTER it works. So in plain words, if i get my phone unbricked or flashed, software will be released to everyone.
Option A: Solve my factory mode "brick" or A.2
If the phone passes the "updating modem..." state but it's not solved (aka "not booting the kin OS anymore"), i consider this option to be not-completed, so not-paid.
Option B: Get a OS on the device
Again, in this option the phone must pass the "updating modem..." state AND enter an OS.
Also, this option requires to give software that can write (succesfully, of course) to the device and load the kin OS or another OS (winCE,android, ... ). The solution may work on linux / windows / mac as the solving person decides, as long as it doesn't require 64 bits thing.
Software given, if named (like "MrGuy Kin flashing") will be still owned by "MrGuy" in the distribution itself, being binaries or sourcecode.
Note here that if flashed but not passing the brick status or not booting means again not-completed, so not-paid.
If verizon kindly gives the Kin ROM (as stated on this forums), software that flashes it to the device is OK with this option, so solving person doesnt need to find a suitable ROM and so on. Of course, as long as the flashing works, it's available to do so.
Contact
If you wanna provide solutions or make a non-public question/comment, feel free to PM me here or use [email protected] for it.
Somebody posted Sharp's SPST tool with drivers, exes, and a pdf that explains how to do alot of things include reset your phone back to its factory default. Give it a shot and reply back on that thread.
http://forum.xda-developers.com/showthread.php?t=1019223
As said there.... nothing
i put a little update and get a new subbounty for bypassing the updating modem (aka OTA update) from verizon, so i can get inside the OS, with half the option A prize: 25€ (~35$).
Response from verizon (if works) matches this solution (and payment requirements) for me.
Will update the big post later .
It's April 21th local time, and as no solution solved the issue, i consider the bounty closed from now on.

Essential PH-1 downgrade

Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
stephxo said:
Hello yall!
So I am at a complete loss on how to fix the issues with my Essential device.
So I decided to post here in as much detail as I can and hopefully receive some answers.
I purchased my phone used from eBay about a month ago.
According to the listing it was factory unlocked.
I have AT&T prepaid.
Everything was running smoothly for about a week until I receive the notification for the Android Pie OTA.
(At this time my bootloader was not yet unlocked nor was I rooted).
Again everything was fine UNTIL I installed the security patch update.
As soon as I installed and rebooted my sim read as invalid.
I rebooted, tried to mess with network settings, factory reset, etc.
Turning to Google, I realize this is a common issue with the Sprint variant of this device (of course my luck would be for me to unknowingly purchase the Sprint variant not knowing there was any issues) and the pie update.
The main fix for this issue would be of course to downgrade back to Android 8.
Here's my issues...
I unlock my bootloader.
Install the Android 8 firmware from the official Essential site. (made sure to install the one for Sprint variant).
Flash.
The touch screen is not functional. At all.
Flash back to Android Pie and install TWRP
Flash Android 8 custom ROM.
Touch screen still not functional.
So I'm back on Android Pie and touch screen is working, but sim is still invalid.
How are other essential users successful in downgrading the software?
HELP.
Click to expand...
Click to collapse
Did you unlock your critical partitions along with the bootloader?
arjunv said:
Go to the guide section and read the post that says uicc unlock there is a solution outlined.just follow it and your phone will be back in service
Click to expand...
Click to collapse
Do you think you could link that post for me? I can't seem to find it.
I also don't see any uicc option on my debice. (Not sure or that matters though)
If it's Sprint you need to wait 50 days before you can unlock it. CDMA phones are a pain in the ass to unlock, always buy International if possible!
This thread has some information that might be useful:
https://forum.xda-developers.com/essential-phone/help/unlock-sprint-version-t3720727
Sent from my PH-1 using XDA Labs
SuperBrolySSJ said:
Did you unlock your critical partitions along with the bootloader?
Click to expand...
Click to collapse
This is required for the touch screen firmware to be flashed and OP needs to see this.

Help me to prevent digitizer locking on my third PH-1

I considered posting on the main question thread, but I am requesting a comprehensive response and therefore feel a standalone post was warranted.
I am on my third PH-1 and am now scared of touching it. I need your help.
Here is my background: I received my first PH-1 in October 2018; I used it stock with a Verizon sim card and had no intention of rooting it or doing anything custom. A nice solid phone. Then, at the start of November, it rebooted and the digitizer froze out of nowhere. I knew that it had recently ran a System Update to Pie that had been prompted (apparently an OTA update). I got it to unfreeze via Safe Mode. Then it soon rebooted again out of nowhere and the digitizer froze a second time; completely unresponsive. I did another couple reboots and it unfroze, then froze a third and final time that evening. I thought it was my fault; that some app I loaded from the store killed the phone. I contacted essential support; I erased the phone via the factory reset, but the digitizer did not respond. Essential warranty replaced the phone.
I received my second phone at the end of November. I did not check what version or anything and like a good user, I ran the prompted System Update (to Pie) and reduced the number of apps I installed to the bare minimum. At the end of that week, the digitizer on this new second phone ceased working immediately after a reboot. I got it to come back two more times (again), but it eventually froze just like the first one. Essential support explained that this may be due to not having the correct kernel updated on my phone prior to accepting the OTA update. Essential warranty replaced the second phone.
I now hold in my hands the third Essential phone.
It is 7.1.1, Kernel 4.4.21-perf+
System Update keeps prompting me to download and install PPR1.181005.099
I am technically proficient, however am new to rooting and updating Essential phone firmware.
As I understand it, I need to get to the latest kernel version before I can update the Android version, as updating to the latest Android would again disable the digitizer.
How do I do that?
I have done the following so far:
Read through this guide: https://mata.readthedocs.io/en/latest/
Read through this firmware dump post: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Own a Windows 10 machine
Purchased a non-stock USB C cable - Monoprice Essentials USB Type C to USB-A 2.0 Cable - 480Mbps, 3A, 26AWG, Black, 0.5m (1.6ft) #27932 https://www.monoprice.com/product?p_id=27932
Installed Essential-PH1-WindowsDrivers.exe
Unpacked platform-tools_r28.0.1-windows.zip
Charged my phone
Activated developer options
Enabled OEM Unlocking
Disabled automatic updates (system and apps)
I am completely lost as to what my next step(s) need to be and I truly would appreciate being walked through this. At worst, I just want to disable the prompt to run a System Update and then survive like a Neanderthal on Nougat.
Can someone please help. Thank you.
Of note, I actually fear for new, non technical, PH-1 owners who, upon receiving phones during the window I also received mine, have had their digitizers fail. So far, I feel alone as the only one with this problem.
I am also prompted to update Essential Services and Essential Resources from Google Play Store, but I am hesitant to do so.
This is the thing.. Unless you want to root your phone and or flash custom roms? Don't do anything but take the friggin OTA. Period, The second you unlock your bootloader and start messing with stuff it becomes your brick and not Essential's problem. That's my two cents bud.
Sent from my mata using XDA Labs
JayLosh said:
.
It is 7.1.1, Kernel 4.4.21-perf+
System Update keeps prompting me to download and install PPR1.181005.099
Click to expand...
Click to collapse
I got my ph1 (halo grey) in Sep 2018, from Amazon during sale period, it came with 7.1.1 installed, I immediately took all updates (incl Essential ones from Play store) & am now on Android 9 build you list above & dec security patch. No problems with digitizer, but I've not rooted this phone or unlocked BL, as yet. No problems with digitizer. This doesn't seem like a common problem (not that I've read all the older posts) so maybe it is due to some other mod or app on your phone, though not sure what kernal my phone come with, now its 4.4.162-perf+

Mi a1 no network signal - please help!!!!!

Hi Devs and team,
I have no network signal (AIRTEL or IDEA) in India. (Possibly due to PIE update) No 4g, 3g or even 2g.
I will briefly explain what happened:
1. I was in Oreo November patch till 1st week of Jan 2019 and i was not upgrading to PIE update Jan patch as well, due to all the discussion on bugs and all.
2. However, one day around 8 or 9 Jan, i noticed that update has been downloaded onto my device and it was asking for a reboot to install.
3. But i was avoiding that restart as well since i was scared i would be affected by bugs.
4. Suddenly, around 13 or 14 Jan , i lost mobile signal just like that. (NOTE THAT I DID NOT RESTART MY PHONE YET)
5. I still left my phone like that for a day and there was no change in network signal. Then i thought this may be xiaomi's way of forcing me to install the pie update and then i restarted and PIE was installed.
6. But still there was no signal. Even then i waited for 1-2 days and thought that this may get resolved.
7. Finally around 16 Jan, as my phone was still not getting any signal, i went on the internet trying to search for solutions.
8. I did everything possible. DOWNGRADED from Pie to Oreo 8.0, 8.1, Nougat (Aug 2017 build), used fastboot for this process and then used even hotboot twrp for this process, rooted, then unrooted. I have done this countless times. (Maybe 10-15 times, tried various combinations) Please note that i never had any problem with my IMEI. I always had my IMEI intact during this process. But i never had my signal back. I flashed only modem firmware as well just in case. I am still searching for answers.
9. Meanwhile, i took my phone to Xiaomi service center and after checking they just said, i had to replace my Motherboard and it would cost around 8k (approx). Mind that i bought this phone for 13k. I refused and i thought i would get it checked outside.
10. I took my phone to unauthorised service center as well. Even before diagnosing my phone, he said either antenna or network IC may have been faulty. It has been 2 days and he is now saying he is not able to point out what the problem is yet.
11. It has been more than 20 days and i am without a phone. Everything else works on my phone except for the network signal.
PLEASE HELP ME. I am not able to figure out whether its a software problem or hardware.
I have read that many users have problems with signal. can someone tell me what to do.
My opinion is that maybe seamless update feature helped whatever bug is there in pie to affect my device in oreo and now, i have no signal now whatever i do.
UPDATE: I have just checked with the service center guy (unauthorised) - he says he tried everything (including replacing antenna and other stuff) except for changing network IC. He says changing network IC is risky and it may damage other components. I am not able to decide what to do.
How did you downgrade to Oreo from Pie. As of stock pie for this device, there is arb which will cause bootloops if you downgrade with the usual methods. The steps to downgrade is now more difficult.
I'm no expert, but given what you describe and what Service Center told you, it looks more like Hardware issue than anything else.
If it was software, with all the downgrades you did, you should have been able to get back to a situation where it worked. One thing though, did you try it with another SIM/Operator? SIMs can die too, and usually your operator should give you a new SIM for free or cheap, and you could as well borrow a SIM from someone else, to confirm it's really the full phone that is dead.
So your phone is most likely broken... I guess that if Service Center said you have to pay for motherboard replacement that you are out of your warranty period? Because if you're still under warranty, they should replace for free...
You sure your Sim isn't broken?
Yes to all your questions.
1) i have tried my sims in other phones (they work) and Other sims in my phone (they dont work). Tried hard reset, soft rest etc., nothing works.
2) I have downgraded as per the tutorial of downgrade in xda forums. i had no bootloop or no imei lost cases. Everytime my phone booted well with all imei's intact. I went from oreo 8.0 to pie (over OTA again after proper downgrade) and pie to oreo 8.0 oreo 8.1 nougat.
As i said, i have tried all combinations.
Request your help.
Try installing any custom rom
Can you suggest one so that i can try? Also please tell me rooting from which version would be better. Nougat or Oreo 8.1? I would prefer one which would solve my issue.
FYI: That service centre guy returned my device, saying he could not repair it.
Apart from the above, i have a doubt whether reinstalling my IMEI may kick my modem to start picking up a signal. can i do that? Can i rewrite the same IMEI again?
Str!der said:
Can you suggest one so that i can try? Also please tell me rooting from which version would be better. Nougat or Oreo 8.1? I would prefer one which would solve my issue.
FYI: That service centre guy returned my device, saying he could not repair it.
Apart from the above, i have a doubt whether reinstalling my IMEI may kick my modem to start picking up a signal. can i do that? Can i rewrite the same IMEI again?
Click to expand...
Click to collapse
U can try pie based roms like Los16 , PE latest , crdroid ,etc they r stable for daily driver.
Rooting from 8.1 would be better
Don't touch IMEI for now , try installing custom ROM , if network works then stick to custom ROM and if it doesn't work then it would be a hardware issue.
Have you checked your APN, I lost mine after an update, I manually re entered all the details and all was perfect again.
Did u got your network issue solved?
I'm facing the same issue . .

Help! I just pulled an all nighter

My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
UPDATE!
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
MajinMight said:
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
Click to expand...
Click to collapse
UPDATE #2
As you can tell I haven't given up yet. I found my current firmware version for download on a different website:
https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/"]https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/
It's another slow download option which really sucks. But I'll be able to test If I can flash the same firmware to the phone (not technically a downgrade and carries the same fused binary). So we shall see. If this doesn't work I'll be looking into the other android 9 or 10 roms and rooting the phone.
Thanks, Derek
MajinMight said:
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
Click to expand...
Click to collapse
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Dang! Well thanks for the info! I guess all the videos I've seen with S7's and custom roms have not been done on the US-Verizon phone. What a bummer. Well this was a major learning experience at least.
My only idea now is to crack her open and make sure the camera didn't come unplugged from a drop. I also seen camera replacements were really cheap online. I don't know if it's worth my time....we are due for a phone upgrade anyway.
SkylineDriver said:
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Click to expand...
Click to collapse

Categories

Resources