Related
Hi,
I just received a brand new Nexus 7. I turned it on, logged into my account, and then the first thing I did was go to settings -> about -> check for system updates.
It started updating to 4.2
During the update, I got the android with red exclamation point.
Pressed power and volume up and it shows this. (See attached image)
I'm completely stumped. Its brand new and hasn't been rooted or modified.
I tried sideloading the update via adb but I get the same error.
Any ideas?
Any help would be greatly appreciated. Thanks
If you got it local, exchange it. You don't have a lot of time invested at this point to try to fix it.
I had the same exact problem but it was really easy to fix.
I downloaded the Nexus 7 toolkit and did the following:
1) Installed the Google Nexus 7 Drivers from the Nexus 7 Toolkit menu.
2) Unlocked my BootLoader from the Nexus 7 Toolkit.
3) Downloaded the factory stock rom for 4.1.2 in the Nexus 7 Toolkit.
4) Put my device in fastboot mode (power + volume down)
5) Selected the option to flash the device with the factory rom.
Once it was installed, I was able to apply the OTA update. Apparently many of these devices ship with this issue.
JayOui said:
I had the same exact problem but it was really easy to fix.
I downloaded the Nexus 7 toolkit and did the following:
1) Installed the Google Nexus 7 Drivers from the Nexus 7 Toolkit menu.
2) Unlocked my BootLoader from the Nexus 7 Toolkit.
3) Downloaded the factory stock rom for 4.1.2 in the Nexus 7 Toolkit.
4) Put my device in fastboot mode (power + volume down)
5) Selected the option to flash the device with the factory rom.
Once it was installed, I was able to apply the OTA update. Apparently many of these devices ship with this issue.
Click to expand...
Click to collapse
If you're going to go through the trouble of flashing a factory image to get the N7 up to date, just flash the latest. There's no need to waste time with the OTA at this point.
edit: the blurry image shows a patch assertion error on the kernel. This means that the installed kernel does not match what the OTA was expecting to find. This is typically indicative of the presence of a custom kernel.
comminus said:
If you're going to go through the trouble of flashing a factory image to get the N7 up to date, just flash the latest. There's no need to waste time with the OTA at this point.
edit: the blurry image shows a patch assertion error on the kernel. This means that the installed kernel does not match what the OTA was expecting to find. This is typically indicative of the presence of a custom kernel.
Click to expand...
Click to collapse
I agree it is indicative of a custom kernel but I had the same problem of a device pulled directly out of the box which was unfortunately shipped from Walmart since they were sold out on Google Play at the time. BTW, the box was sealed so unless Asus is shipping refurbished units as new, I don't see how this could have happened. If you google the error for the LNX device error, you will see this is more common that would be expected.
You are also correct that I could have flashed the 4.2.1 factory image, but at that point I wanted to make sure that I could actually get the OTA updates in the future. This showed I could as I was able to get the OTA update to 4.2 and then the subsequent update to 4.2.1.
You don't happen to have the original kernel or kernel information do you? I'd like to take a closer look at it to see what the deal is. Or do you happen top recall the build number that the device was shipped with?
Sent from my Nexus 4
This happened to me today, too.
I got a brand new 32GB wifi Nexus7 from the local electronics store.
Sealed box.
CBO serial
4.1.2 JZO54K preinstalled.
Made the OTA update.
At about half of the progress bar the red exlamation mark symbol came and the device rebooted on its own after waiting 1 minute.
And now 4.1.2 is still installed.
(everything stock and locked)
Can I fix it somehow else, without rooting etc?
Likewise, mines 4 days old and the update just won't install.
I tried to clear the "data" of Google Services Framework. Then did the OTA again but it failed again with the red triangle at about 1/3 of the loading bar.
Here is a workaround which didn't work for me (clearing data of Framework)
http://www.adilhindistan.com/2012/07/upgrading-nexus-s-to-jelly-bean-411.html
I tried it several times, even wiping /cache in stock recovery doesn't help.
I will continue to try the update. And either it will work all of a sudden or I really need to adb sideload the update manually on a fresh locked, unrooted device. Come on Google.
I gave up and flashed mine via ADB there's obviously something wrong with the OTA combined with the Nexus 7 32gb as it only seems to affect this model from looking at the stories.
I went to my local dealer. And after some evaluating and checking. They were able to to connect to their wifi. I then reproduced the failure in the shop. Then afterwards they called ASUS (The salesman let me talk to Asus directly, but they couldn't help, Google is responsible for software). And after this the salesman checked a demonstration model, which already had 4.21.
Then he asked the store manager I guess (at least he wore a suit as opposed to the others.)
And finally they exchanged my model to a new one. Now I have another CBO device but this time it updates flawlessly.
I'm happy.
JayOui said:
I agree it is indicative of a custom kernel but I had the same problem of a device pulled directly out of the box which was unfortunately shipped from Walmart since they were sold out on Google Play at the time. BTW, the box was sealed so unless Asus is shipping refurbished units as new, I don't see how this could have happened. If you google the error for the LNX device error, you will see this is more common that would be expected.
You are also correct that I could have flashed the 4.2.1 factory image, but at that point I wanted to make sure that I could actually get the OTA updates in the future. This showed I could as I was able to get the OTA update to 4.2 and then the subsequent update to 4.2.1.
Click to expand...
Click to collapse
I got my 32gb in December and have had the same problem. Google support said it was an asus issue and of course asus said it was a google issue. Both only had factory reset as a suggestion, which did not work. There seems to be hundreds of users with this issue because I have found tons and tons of people with the same problem, but no real answers. Rooting and flashing is of course a fix but not really a solution. I root my phones, but really do like the nexus as is and like you would want to be able to receive further ota updates without issue. I'm intrigued by your wrong kernal idea. I got mine new from a local gamestop.
I've attached a screenshot of my info. Can you tell me, please, is this the wrong kernal? If so and I follow your steps from the nexus toolkit, what will happen to everything that is on here? Will apps, data, personal file , and settings all be wiped? Are there any backup opttions? Not being rooted I can't use my titanium backup so will a copy to pc get everything?
Thanks so much!
@Sorraia3
That release - JRO03S - seems kind of old for a device which was purchased in December. Setting that aside though, there have been a few reports on here of "pure factory" JRO03S devices that would not properly accept the OTA update.
To know what the exact error condition is, you would either need to show a picture of the recovery screen with the error message, or if there is none, get a copy of the recovery log file (which might require root and therefore poses a chicken-vs-egg problem).
If you don't want to pursue a return/exchange/repair with Google/Asus, you could try identifying the exact problem - but to do that you would need to unlock the bootloader... which causes a full tablet wipe & in any event would be more difficult than just flashing a (new version of the) full factory ROM.
Look at the "return to stock with fastboot" thread for instructions on the latter.
You need to make backups of anything worth saving as the tablet gets completely wiped during this process. You might also want to look into the "Carbon" app for backing up market apps & their data on an unrooted device before you begin.
Also, the fact that you will be unlocking your bootloader does not mean that you need to flash custom ROMs or any other "rooting" activities - you can certainly just re-lock the bootloader after installing the factory ROM, and stay in a "pure stock" condition (with the newer factory ROM).
good luck
I know it has been awhile since I posted in this thread, but I got sidetracked. I'm now going to be taking care of this and was wondering if I can jump right to the newest build or should I graduate up them? If the latter, can someone give me the proper build order? If the former, what is the most current stable build I should use?
Also, I no longer seem to be able to find the thread mentioned "return to stock with fastboot" would you have a link for it?
Wait I think I just found it. Is this it?
http://forum.xda-developers.com/showthread.php?t=1907796
So the recommendation is to go through adb rather then use the toolkit?
Thanks much!
Sent from my Nexus 7 using xda premium
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.
I've searched but apparently it seems like most of the answers have been deleted or redacted.
My problem...
I was just given a Yoga Tab 2 from my sister who has given up on trying to fix it.
The tab was on 5.01 and rooted when she got a system update. She ran the update but now the tablet freezes during/after the boot animation.
It will go into fastboot but is not recognized by ADB.
She tried to install the original Lollipop firmware through recovery but ended up getting a system 7 error.
This is exactly what I see when in the bootloader screen
FASTBOOT MODE
PRODUCT_NAME - YT2
VARIANT - YOGA Tab1
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI VERSION - Blade_21.x64.0005.R00.1504101447 FFD8_X64_R_
SERIAL NUMBER - BaytrailD454B***
SIGNING - ?
SECURE_BOOT - ?
E: No valid installer medium found
I know nothing about Lenovo and how they do things but I know that with HTC you have to go back to 100% locked and stock before you can install an OTA. If you do try the OTA usually just won't install but unfortunately this thing seems to be at least soft bricked.
Is there a way for me to maybe roll back? I've read about people going back to KK in order to get the LP OTA but all links to the KK firmware are gone.
Thanks a lot, I appreciate any help I can get...
BTW, She is under warranty but of course she was rooted and is worried that repair will cost her almost as much as she paid for the Tab when they realize and void her warranty.
If its the same as the 1050f try these files.
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo do not bother about the warning with this one, its something to do with its size, just download it.
corasman said:
If its the same as the 1050f try these files.
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo do not bother about the warning with this one, its something to do with its size, just download it.
Click to expand...
Click to collapse
Thank you. I used the Restore KitKat Bios you posted along with an 830F specific KitKat firmware from the Russian Lenove site. Worked fine after editing the flash.xml file to allow for a larger system.img file.
The tablet is now back from the dead. Unfortunately it gets the 5.0 update but fails in the Lenovo Recovery when trying to flash the OTA. It gets to 100%, stays like that for a bit and then a blue X saying flash failed. After that I'm back to a black screen and have to reflash the kitkat firmware to get up and running again.
I have no idea why the OTA flash constantly fails but I guess I have to do a bit more research and hope I can get her up to date.
Did you set the country code , without setting it updates fail.
Look at this advice from ionioni to me about setting the code
http://forum.xda-developers.com/thinkpad-tablet/general/set-country-code-t3308024
corasman said:
Did you set the country code , without setting it updates fail.
Look at this advice from ionioni to me about setting the code
http://forum.xda-developers.com/thinkpad-tablet/general/set-country-code-t3308024
Click to expand...
Click to collapse
Outstanding!!! I entered the code in contacts and it gave me a menu of different countries to choose from. I Chose US and she rebooted, went into recovery, ran a bit and rebooted into another fresh install which looked completely different. We're talking different wallpaper, and different apps. After that it successfully installed 4 or 5 OTAs and as far as I can tell it is now completely up to date!
Android Version is 5.01
Build is S100250-160119
Kernel Version is 3.10.20-x86_64byt-g9f7fad7
Security patch is dated 2016-02-01
I'll wait a few days before I root and install Xposed just to be 100% certain it's up to date.
Of course my sister will probably ask for it back now.
Either way, THANK YOU VERY MUCH corasman!!! Your help has been invaluable!
I am so pleased it worked for you, ionioni helped me so much and now I am trying to do the same for others.
So, today I finally decided to get around to rooting/updating my Zenfone 2 after having it for about a year and a half. Get the rooting done, then I see a way to switch to the WW version instead of the one I'm on. Of course, since I'm stuck on Android 5.0 and the WW firmware goes up to MM, I immediately wanted to switch.
Tried following a bunch of different instructions on how to upgrade, and everything I've tried fails, even after unrooting my device. Most of the methods I've tried (manual install from recovery, system update after moving files onto phone, etc.) look like they start to work, then about halfway through the update I get a message on the screen that just says "error" with the bot laying down. Try to run the sideload with adb, get a message that "error: device not found" but figure it would be the same if I even did get it to work.
Anyone have any suggestions for what I can try, or am I overlooking something dumb? Thanks.
Oh, also, tried a few different editions of the WW firmware, all do the same thing, so it's not just one bad file.
daft_inquisitor said:
So, today I finally decided to get around to rooting/updating my Zenfone 2 after having it for about a year and a half. Get the rooting done, then I see a way to switch to the WW version instead of the one I'm on. Of course, since I'm stuck on Android 5.0 and the WW firmware goes up to MM, I immediately wanted to switch.
Tried following a bunch of different instructions on how to upgrade, and everything I've tried fails, even after unrooting my device. Most of the methods I've tried (manual install from recovery, system update after moving files onto phone, etc.) look like they start to work, then about halfway through the update I get a message on the screen that just says "error" with the bot laying down. Try to run the sideload with adb, get a message that "error: device not found" but figure it would be the same if I even did get it to work.
Anyone have any suggestions for what I can try, or am I overlooking something dumb? Thanks.
Oh, also, tried a few different editions of the WW firmware, all do the same thing, so it's not just one bad file.
Click to expand...
Click to collapse
After doing a Google search, I think you should first switch to WW version of Stock 5.0 than upgrade to Stock 6.0.1
You are in CN or TW , right?
Going by everything I've seen, I'd assume I'm on a CN version, going by what release I'm currently on. However, the firmware on my phone claims it's a WW version, so I'm not completely sure. Guessing it started out as a CN, then switched to a CERTAIN version of WW at some point, but doesn't seem to be in-line with the other WW updates, seeing how I'm visibly several iterations back from the most current WW release.
If it helps:
Model Number: ASUS_Z00AD
Baseband Version: 1603_5.0.68.9_0810,1546_7.0.29.0_0413
Kernel Version: 3.10.20-x86_64_moor-265437-g6ab076a
Build Number: LRX21v.WW-ASUS_Z00A-2.20.40.198_20160930_8756_user
daft_inquisitor said:
Going by everything I've seen, I'd assume I'm on a CN version, going by what release I'm currently on. However, the firmware on my phone claims it's a WW version, so I'm not completely sure. Guessing it started out as a CN, then switched to a CERTAIN version of WW at some point, but doesn't seem to be in-line with the other WW updates, seeing how I'm visibly several iterations back from the most current WW release.
If it helps:
Model Number: ASUS_Z00AD
Baseband Version: 1603_5.0.68.9_0810,1546_7.0.29.0_0413
Kernel Version: 3.10.20-x86_64_moor-265437-g6ab076a
Build Number: LRX21v.WW-ASUS_Z00A-2.20.40.198_20160930_8756_user
Click to expand...
Click to collapse
From your build number, you are already on the latest version of WW stock 5.0
In order to upgrade to Android 6.0.1 Download the firmware file(WW-4.21.40.223) from ASUS ( https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/ )and rename it to MOFD_SDUPDATE.zip Put the MOFD_SDUPDATE.zip in internal storage as well as micro sd card (if you have one). Boot into recovery and it will update automatically.
Well, I'll be darned. That actually did it. Before, i was trying with the update file on EITHER my internal storage or my SD card, and that ended up just giving me an error message. Putting it on both at once caused it to go through properly. Thanks!
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