Have a decent understanding of how to unlock/root/xda, just want to make sure, so any help would be appreciated.
Still on 7.1.1, (Google edition? Bought on eBay and not really sure because oem unlock is greyed out, no Verizon apps though) wondering best way to get to android O/P with the bootloader unlocked. Should I OTA then try the Verizon unlock method? Or try the unlock method on 7.1.1 then flash a android O/P rom/modem/baseband etc? Got some reading to do....
Any other tips would be appreciated as well, thanks for your time.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So if your Button is greyed out... It's a Verizon variant.
https://www.facebook.com/IsMail.AmZdak reach out to that guy and donate what ever you can and ask if he can bootloader unlock your phone. it doesn't matter what version of Android you're on.
Once he unlock your bootloader proceed to downloading developer preview 4 and run flash all command.
Once it has finished flashing Android p the phone will then reboot let it get to the main screen and then reboot the phone and put into bootloader mode.
Download TW RP image and run Fastboot boot ( twrp image ) and wait for it to boot twrp. When you're computer reads the phone, drag and drop twrp installer into phone and the install. Reboot to recovery >> flash magisk >> boot up
You can use the Verizon method on 7.1.1 or newer as far as I know.
lafester said:
You can use the Verizon method on 7.1.1 or newer as far as I know.
Click to expand...
Click to collapse
So even though there are no vzw apps, bootanimation or any vzw stuff, this phone still a Verizon one? Weird....
lordodin912 said:
So even though there are no vzw apps, bootanimation or any vzw stuff, this phone still a Verizon one? Weird....
Click to expand...
Click to collapse
Are you on Verizon? The apps only load with their sim.
lafester said:
Are you on Verizon? The apps only load with their sim.
Click to expand...
Click to collapse
Yes on Verizon, still no apps, rebooted multiple times and updated all playstore apps......no vzw stuff anywhere (not complaining, ha) just seems odd.
Is it better to OTA update to 8 then unlock/root, or is there another way (flash rom/modem...etc over 7.1.1, might not play well with bootloader though, jw).
Thanks.
Screens for proof....
Well im not on vzw but have a vzw pixel. My fi app downloaded when I put in the sim. Figured vzw would be the same.
lordodin912 said:
Screens for proof....
Click to expand...
Click to collapse
lafester said:
Well im not on vzw but have a vzw pixel. My fi app downloaded when I put in the sim. Figured vzw would be the same.
Click to expand...
Click to collapse
Gotcha.
Edit: CID getter shows rom.boot.cid:[VZW_001], also checked verizon account, shows up as Pixel XL, not "non vzw device" which someone said it should say if it's google edition.
Ugh, any real difference between the Google edition vs VzW (except, ya know, the bleeping bootloader unlock)?
Edit: Got root/twrp, no problems.
Thanks again.
lordodin912 said:
Ugh, any real difference between the Google edition vs VzW (except, ya know, the bleeping bootloader unlock)?
Click to expand...
Click to collapse
Not sure if this was answered already, but no. The bootloader being locked is the only difference.
Related
Hi,
I bought brand new inactivated sprint htc one m8 harman kardon. I managed to get it bootloader unlocked, S-Off, rooted, and TRWP 2.7.0.2. I'm trying to get the SIM unlocked but I couldn't. I used the following method to unlock the sim but I couldn't pass step 4 as I reach to hit "start" but nothing happens. (http://forum.xda-developers.com/showthread.php?t=2718150&page=5)
I also tried to install roms but when the mobile boot after I get successful installation, it reboots on bootloader screen only.
I appreciate any help.
Thanks.
you do realize that post you linked to right at the top it says 100% works from GSM unlocks. nowhere does it say anything about CDMA phones...? which your sprint model is...
and yes i know what your going to say it has a GSM sim card slot but it doesnt matter.
when people say compatible with GSM models it mostly means international GSM and US(ATT/TMOBILE) phones. CDMA phones are a bit more complicated. cause theres the extra CDMA radio partition.
syaoran68 said:
you do realize that post you linked to right at the top it says 100% works from GSM unlocks. nowhere does it say anything about CDMA phones...? which your sprint model is...
and yes i know what your going to say it has a GSM sim card slot but it doesnt matter.
when people say compatible with GSM models it mostly means international GSM and US(ATT/TMOBILE) phones. CDMA phones are a bit more complicated. cause theres the extra CDMA radio partition.
Click to expand...
Click to collapse
It's Sprint htc one m8 harman kardan.
which means its probably.. though i'm gonna go out on a leg here and say 100% NOT COMPATIBLE with that sim unlock your trying to use.
syaoran68 said:
which means its probably.. though i'm gonna go out on a leg here and say 100% NOT COMPATIBLE with that sim unlock your trying to use.
Click to expand...
Click to collapse
There are some users who said the managed to get it unlocked. At least, can I install roms for unlocked sims?
Zeeking said:
There are some users who said the managed to get it unlocked. At least, can I install roms for unlocked sims?
Click to expand...
Click to collapse
you dont need to unlock the SIM in order to use custom roms. all you need is to unlock the bootloader using the HTC unlocker
syaoran68 said:
you dont need to unlock the SIM in order to use custom roms. all you need is to unlock the bootloader using the HTC unlocker
Click to expand...
Click to collapse
I did unlock the bootloader in addition to S-Off. However, I'm not able to install any rom. After I try to install the rom (zip file) and I get the message to rebbot after I get successful installation, it boots back to bootloader screen!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Zeeking said:
I did unlock the bootloader in addition to S-Off. However, I'm not able to install any rom. After I try to install the rom (zip file) and I get the message to rebbot after I get successful installation, it boots back to bootloader screen!
Click to expand...
Click to collapse
and your on TWRP?
syaoran68 said:
and your on TWRP?
Click to expand...
Click to collapse
Yes. Itried both recovery files.
Users can still use SamFirm_V0.3.6 to download SM-G930U_G930UUEU2APG9 firmware to flash on our US Verizon S7's. The firmware contains the latest 8/1/16 security patch.
Thanks to zxz0O0 for this program and OP! Thanks to princecomsy for the modded Odin 3.1.2.
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
The OP said that the software has depreciated, but it still works!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reserved!
This one too, just in case!
Wait I'm confused the firmware version says its for the G930U, but also saying its for VZW? Which is it lol, the G930U or G930V. I know you can flash the U firmware on the V model but I'm just asking to make sure.
There were two identical versions of the "U" firmware. Sorry for the confusion. You can use the program to download the "U" firmware to flash on on our Verizon S7's.
DeathAngel66669 said:
There were two identical versions of the "U" firmware. Sorry for the confusion. This firmware can be used to flash said firmware on our Verizon S7's.
Click to expand...
Click to collapse
"This" firmware can be used to flash "said" firmware?
Sorry to make you elaborate it seems simple but I can't quite tell whats going on haha.
I need to download both and flash half from each? Or flash one first then the other?
You can download either one. The XAA and VZW firmware are identical. I just flashed the "VZW" one and it made no difference.
DeathAngel66669 said:
You can download either one. The XAA and VZW firmware are identical. I just flashed the "VZW" one and it made no difference.
Click to expand...
Click to collapse
Oh lol, and it came with VZW bloat and worked with the Verizon specific features and all that?
I'll let you know once I get through the setup.
Edit:
Added screenshots. The firmware is unbranded, no Verizon bloatware.
DeathAngel66669 said:
I'll let you know once I get through the setup.
Click to expand...
Click to collapse
Sweet thanks
I found these for the S7 edge:
http://updato.com/firmware-archive-select-model?q=sm-g935u
Again, either one will work. I hope this helps.
DeathAngel66669 said:
I found these for the S7 edge:
http://updato.com/firmware-archive-select-model?q=sm-g935u
Again, either one will work. I hope this helps.
Click to expand...
Click to collapse
Yeah thats the one I downloaded, but when I loaded it into Odin the CSC showed as OYM, and not VZW.
Oh well lol I'll keep this running I don't have it set up yet so I can't speak on battery life or performance (although I'm sure it will be similar to PF2) but as far as my signal goes there are no issues so I'll keep this installed. Thanks for the guide and for helping me out.
Edit: Oh, didn't know the U firmware let you straight up uninstall some of the Samsung crap, not just disable it. Also didn't realize that all the 3rd party bloat was Verizon's doing, not Samsungs I disable all that crap with Package Disabler Pro anyways, but still didn't realize how sh*tty Verizon is lol.
Sure thing, no problem. One problem... If you use visual voice-mail, it will be lost. I have not found a suitable working replacement either... I just long press the "1" in the dialer to check my voice-mail, lol. Old-school....
Oh okay
Lol I know benchmarks don't really mean anything but damn
Beat the OnePlus 3 in RAM score even though it has 2GB less ram LOL
Nice!
Why do I get:
error loading library:
Checking firmware for SM-G930V/VZW/G930VVRU2APE1/G930VVZW2APE1/G930VVRU2APE1/G930VVRU2APE1
Error loading library: 14001
Please make sure "Microsoft Visual C++ 2008 Redistributable Package (x86)" and "Microsoft Visual C++ 2010 Redistributable Package (x86)" are installed
Error: Could not send BinaryInform. Status code 200/401
Authorization failed
Try installing those two MS VC C++ packages, reboot and try again. I have them installed and did not experience that error. Works on my laptop and desktop.
I flashed the new U firmware and man my phone is back to normal. I want to root it but it was so sluggish with the root kernal even with the v15 fixes and all the tweaks I read here. Opening apps were taking 5 seconds, unlocking the phone was taking a few. It literally felt like I was running some crap $50 chinese phone lol. Also my battery was going down 10% every half and hour. Now with the fresh stock install no root no tweaks I've lost 3% in 1h and 33 minutes
What exactly are the benefits of doing this? Doesn't the U firmware have an unlocked boot loader, or something along those lines?
Nobiscis said:
What exactly are the benefits of doing this? Doesn't the U firmware have an unlocked boot loader, or something along those lines?
Click to expand...
Click to collapse
No unlocked bootloader, just 0 Verizon bloat to bog down the phone, so it tends to run much cleaner.
I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
WhiteReign said:
I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
Click to expand...
Click to collapse
i just use the factory images
https://developers.google.com/android/ota
Here's the OTAs. I've circled the right one. Maybe you were downloading the UK one?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 2 XL using Tapatalk
I can only get the DEC 5 To work. When I do it wont let me up grade to the newer version. kinda stuck here.
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
sharkie405 said:
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
WhiteReign said:
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
Click to expand...
Click to collapse
There are multiple step-by-step guides here on how to do just this. Suggest you take a step back and read one or two. There are two separate unlock commands to use and from your photo you did not complete that. Secondly, it looks like you may be using an outdated version of the adb/fastboot binaries. Lastly you don't flash an OTA with flash-all. If you are attempting to sideload an OTA, you use the "adb sideload" command with the phone in Recovery, not flash-all in fastboot mode. At this point, you should probably update your adb/fastboot binaries, download the full factory image (not OTA) and flash it instead. Slow down and read more.
Damn Sir! Thank you very much for the help!
WhiteReign said:
Damn Sir! Thank you very much for the help!
Click to expand...
Click to collapse
Not blaming anyone but instead just using your post for calling out there are what seems like dozens of variations for doing the same few tasks on this device. There are a couple really good tutorials that are either 100% or were until something like TWRP of magisk changed something. At the end of the day there are a few givens that will eventually shake out into something like the Heisenberg thread over on the 6P device.
For anyone reading this, unlock critical if you have not, install a custom kernel if you have touch issues in TWRP, really really really read up on the few custom roms that just hit as they add a few variables that most of us have never experienced, make a list of things you install as you do it. All too often people spend countless time and effort helping someone with a boot loop only to find out something not mentioned was in play. Poor steps were attempted from some other thread only to not help or made it worse or different. Examples of this would be xposed, custom kernel, any zip file mods you flashed, viper, Dolby, substratum, you get the idea. We all wanna help and we all need help at some point. Let us try to make the game as easy to play as possible. Flash on brothers and sisters!!
Hi Everyone,
I'm trying to re-lock my bootloader but the OEM Unlock toggle is stuck to the left position whilst displaying the message "Bootloader is already unlocked".
If I try to switch the toggle to the right position, the device will factory reset and then when it powers back up, the toggle is in the left position again.
Is this a result of knox being tripped?
In DL mode it displays both FRP and OEM lock as OFF.
Thanks for the help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just ignore it, it causes no problems and others have had the same problem since unlocking theirs
*Detection* said:
Just ignore it, it causes no problems and others have had the same problem since unlocking theirs
Click to expand...
Click to collapse
Yeah I know that it's not technically an issue but I want to sell the phone and would like to lock the bootloader before doing so.
Is there no way to re-lock it?
If not... would it stop the phone from passing safetynet/google pay checks?
Thanks
EDIT: I've just tested and google pay won't work on it in this state.
You tripped KNOX, many things won't work on it again anyway
*Detection* said:
You tripped KNOX, many things won't work on it again anyway
Click to expand...
Click to collapse
I'm quite aware of that. What i'm specifically trying to ascertaine is whether or not the bootloader is re-lockable.
If need be I'll just install magisk on stock and put the info in the eBay listing.
Thanks for the assistance anways!
As I said, other members have already posted about the same problem, I have not seen a solution yet, although you could read through a few of those threads and see if they were updated
Any news on this? I want to relock too! With it unlocked and stock os. I can't use Google pay or citrix workspace etc!
Hi, is there new news about this problem? the same happens to me. I have the bootloader unlocked with the button to the left, so I can't block it in a rom stock. This causes Google Play to say that the device is not certified and some applications are not installed. Can anybody help me?
MadSilence said:
Any news on this? I want to relock too! With it unlocked and stock os. I can't use Google pay or citrix workspace etc!
Click to expand...
Click to collapse
why in gods green earth would you actually WANT Citrix? Kidding, i use it 40 hours a week and its abysmal, as if you didnt already know that.
naztam said:
Hi, is there new news about this problem? the same happens to me. I have the bootloader unlocked with the button to the left, so I can't block it in a rom stock. This causes Google Play to say that the device is not certified and some applications are not installed. Can anybody help me?
Click to expand...
Click to collapse
So, the bootloader is unlocked, have you guys tried flashing the Odin files with a newer revision of the bootloader?
Thanks for your answer! I have tried to update it, to make a downgrade, to wait 7 days ... and nothing, everything remains the same. The bootloader is binary 6, and the only move I have been able to do with odin is update and donwgrade in the July and August updates. Maybe if Samsung updates the bootloader to binary 7, it will be solved, it is honestly the only thing left for me to try.
naztam said:
Thanks for your answer! I have tried to update it, to make a downgrade, to wait 7 days ... and nothing, everything remains the same. The bootloader is binary 6, and the only move I have been able to do with odin is update and donwgrade in the July and August updates. Maybe if Samsung updates the bootloader to binary 7, it will be solved, it is honestly the only thing left for me to try.
Click to expand...
Click to collapse
what firmware version are you on currently? if your bootloader is revision 5, flash a rev 6 and see what happens
I am in the last firmware
I have the rev6, I can only flash the firmware of July and August
naztam said:
I am in the last firmware
I have the rev6, I can only flash the firmware of July and August
Click to expand...
Click to collapse
[email protected] then. maybe a ver 7 will release soon?
Pixel 3 XL cant boot, stuck on this screen:
https://imgur.com/ObUasvG
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cant boot to recovery or system and bootloader is locked.
Is there any way to unlock bootloader and flash ? or any other solution to fix this state.
deadwolf666 said:
Pixel 3 XL cant boot, stuck on this screen:
https://imgur.com/ObUasvG
Cant boot to recovery or system and bootloader is locked.
Is there any way to unlock bootloader and flash ? or any other solution to fix this state.
Click to expand...
Click to collapse
How did you get to this state? Was it random, or did you do something to it?
There's really nothing you can do if you have no recovery, a locked bootloader, and no valid OS.
Badger50 said:
How did you get to this state? Was it random, or did you do something to it?
There's really nothing you can do if you have no recovery, a locked bootloader, and no valid OS.
Click to expand...
Click to collapse
Random, Ive took it out of my pocket and Ive seen this screen.
deadwolf666 said:
Random, Ive took it out of my pocket and Ive seen this screen.
Click to expand...
Click to collapse
Then RMA that puppy back to google. Unless you at least have a stock recovery, there's no way to side load an OTA to get back to your OS.
Badger50 said:
Then RMA that puppy back to google. Unless you at least have a stock recovery, there's no way to side load an OTA to get back to your OS.
Click to expand...
Click to collapse
Ohh, no firehouse for this model ?
deadwolf666 said:
Ohh, no firehouse for this model ?
Click to expand...
Click to collapse
Did you buy this new or did a friend give it to you? The picture you posted is meaningless without context.
bobby janow said:
Did you buy this new or did a friend give it to you? The picture you posted is meaningless without context.
Click to expand...
Click to collapse
new from ebay, it worked just fine for almost 2 months
deadwolf666 said:
new from ebay, it worked just fine for almost 2 months
Click to expand...
Click to collapse
So you were just minding your own business, pulled it out of your pocket and this is what you saw? No attempts at OTA, root, bl unlock? Was this after a reboot? That's what I mean by context.
That happened to me on my pixel 2xl a couple of times.
My phone was sitting on my desk and would pop a reboot and come up with the 2XL version of your message.
but I was rooted w/stock rom.
I just kept rebooting it until it finally loaded.
then flashed factory w/wipe
Maybe keep rebooting until it works?
then unlock bootloader and take control of your hardware.
bobby janow said:
So you were just minding your own business, pulled it out of your pocket and this is what you saw? No attempts at OTA, root, bl unlock? Was this after a reboot? That's what I mean by context.
Click to expand...
Click to collapse
Exactly, if the bootloader was unlocked I wouldve flashed it. I think I recived an OTA a week ago.
parakleet said:
That happened to me on my pixel 2xl a couple of times.
My phone was sitting on my desk and would pop a reboot and come up with the 2XL version of your message.
but I was rooted w/stock rom.
I just kept rebooting it until it finally loaded.
then flashed factory w/wipe
Maybe keep rebooting until it works?
then unlock bootloader and take control of your hardware.
Click to expand...
Click to collapse
Unfortunately Ive tried that for few dats and its the same