I'm sorry. I'm a noob and trying my best, but am confused. I unlocked bootloader, flashed TWRP and then SuperSU. I'm able to root my phone, but whenever I go into TWRP, it says the phone is encrypted. I understand that without it the radio won't work. Is there a way around that? I keep people talking about s-off. If I use Sunshine to s-off, will it decrypt my phone and allow the radio to work???
When you go into TWRP just press "cancel" at that screen.
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
rebelde80 said:
I'm sorry. I'm a noob and trying my best, but am confused. I unlocked bootloader, flashed TWRP and then SuperSU. I'm able to root my phone, but whenever I go into TWRP, it says the phone is encrypted. I understand that without it the radio won't work. Is there a way around that? I keep people talking about s-off. If I use Sunshine to s-off, will it decrypt my phone and allow the radio to work???
Click to expand...
Click to collapse
And no S-Offing won't decrypt the Data partition. You can use TWRP to format/decrypt it but why?
rebelde80 said:
I'm sorry. I'm a noob and trying my best, but am confused. I unlocked bootloader, flashed TWRP and then SuperSU. I'm able to root my phone, but whenever I go into TWRP, it says the phone is encrypted. I understand that without it the radio won't work. Is there a way around that? I keep people talking about s-off. If I use Sunshine to s-off, will it decrypt my phone and allow the radio to work???
Click to expand...
Click to collapse
What version is twrp are you using? As of 3.0.2-4, twrp was able to decrypt data. You probably have to format data in twrp for this to work, however, but you should really read through the twrp thread under the roms section, as I'm not 100% on this. But if you're not on at least -4, and preferably -5, then that's likely your issue.
If you're on the latest twrp, do you have a startup pin enabled? If so, that's what twrp is looking for.
Anyway, the latest twrp works 100% with decrypting data both with and without startup pin. If you do use startup pin, twrp will accept the same pin you use to start your device.
The thing where twrp always asks for a pin and you just press cancel should no longer be the case on new setups.
Just FYI, formatting data in twrp will wipe everything off of you internal storage, including user data (pictures, etc)
jollywhitefoot said:
What version is twrp are you using? As of 3.0.2-4, twrp was able to decrypt data. You probably have to format data in twrp for this to work, however, but you should really read through the twrp thread under the roms section, as I'm not 100% on this. But if you're not on at least -4, and preferably -5, then that's likely your issue.
If you're on the latest twrp, do you have a startup pin enabled? If so, that's what twrp is looking for.
Anyway, the latest twrp works 100% with decrypting data both with and without startup pin. If you do use startup pin, twrp will accept the same pin you use to start your device.
The thing where twrp always asks for a pin and you just press cancel should no longer be the case on new setups.
Just FYI, formatting data in twrp will wipe everything off of you internal storage, including user data (pictures, etc)
Click to expand...
Click to collapse
Thank you so much! I was using an older version of TWRP ---not the most recent. I repeated the steps using the newest one, and everything is working as it should! I have another question. I had an LG G5 before this pone, and the Note 5 before that. Whenever I wanted to take those previous phones to stock, I'd flash firmware with either odin or LGUP. How do I go about tacking the HTC 10 back to stock??
rebelde80 said:
Thank you so much! I was using an older version of TWRP ---not the most recent. I repeated the steps using the newest one, and everything is working as it should! I have another question. I had an LG G5 before this pone, and the Note 5 before that. Whenever I wanted to take those previous phones to stock, I'd flash firmware with either odin or LGUP. How do I go about tacking the HTC 10 back to stock??
Click to expand...
Click to collapse
Which variant of the device do you have? US Carrier version? US Unlocked? International?
jollywhitefoot said:
Which variant of the device do you have? US Carrier version? US Unlocked? International?
Click to expand...
Click to collapse
I have the T-Mobile version.
rebelde80 said:
I have the T-Mobile version.
Click to expand...
Click to collapse
See post #2 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540
RUU (Rom Update Utility) will get you back to stock (and wipe your internal storage too, so make sure to back everything up first. It won't touch your external SD Card).
There are two formats and both do exactly the same thing.
EXE - runs on windows, so it's dependent on your windows drivers working properly. It will just run through some screens and flash the stock rom and firmware. If this works, it's easier than Odin as there are really no options. You just have to next through several screens. Common problems with RUU.exe's are windows driver issues, antivirus blocking key install files, incomplete downloads, and no access to a windows computer (linux and mac people).
ZIP - more reliable than exe in my opinion. You can use fastboot to flash it in download mode, but there is another method that is easier, especially for people not too familiar with fastboot.
Here is that method:
Download the RUU zip file from the second post at the above link.
rename the zip file to "2PS6IMG.zip" (without quotes)
Place this zip file on the root of your EXTERNAL SD card
Reboot to download mode
In the yellow text at the bottom of the screen, download mode will notify you that it found a 2PS6IMG file on your sdcard and ask if you want to press VOL+ to flash it or VOL- to cancel.
Obviously press VOL+ and it will do the rest
Download mode should restart once or twice and when the flash is complete, it will tell you to press the power button to shut down the device (I have no idea why it forces this shutdown, but obviously, once the device has been shutdown, just hold the power button down to start it back up
Hi I'm confused how do I know the US variant equivalent if my phone is from telcel Mexico?
GRIDSpawn said:
Hi I'm confused how do I know the US variant equivalent if my phone is from telcel Mexico?
Click to expand...
Click to collapse
Sorry, I'm not familiar with telcel. You could start by finding your cid and mid and software number.
jollywhitefoot said:
Sorry, I'm not familiar with telcel. You could start by finding your cid and mid and software number.
Click to expand...
Click to collapse
My cid is HTC 332 and my mid idk my latest OTA was 1.50 or something like that
GRIDSpawn said:
My cid is HTC 332 and my mid idk my latest OTA was 1.50 or something like that
Click to expand...
Click to collapse
If you got it from Telcel México then you should have MID: 2PS650000, you can check it also in the back of the phone (there it would show two less zeroes but the correct MID is 2PS650000)
I have one from Telcel, I unlocked the bootloader via HTC Dev, S-Off via Sunshine, changed the CID to BS_US001 (didn't change the MID as is the same as the US unlocked version) and flashed the RUU exe 1.80.617.1
Now I have a US unlocked version without all the bloatware from Telcel, also as a plus I was able to SIM unlock the device as the Telcel ROM is hardlocked and doesn't let you enter a SIM unlock code (didn't show a prompt to input the code when I entered another SIM from a different carrier), flashing the US unlocked RUU did the trick as the prompt for entering the SIM unlock code appeared right away when I inserted my AT&T SIM.
I'm pretty happy with the phone right now without the Telcel stuff, the only thing I'm worried Is not having a backup of the original recovery to return it to stock for warranty, hope it doesn't fail soon lol.
ReaperHack said:
If you got it from Telcel México then you should have MID: 2PS650000, you can check it also in the back of the phone (there it would show two less zeroes but the correct MID is 2PS650000)
I have one from Telcel, I unlocked the bootloader via HTC Dev, S-Off via Sunshine, changed the CID to BS_US001 (didn't change the MID as is the same as the US unlocked version) and flashed the RUU exe 1.80.617.1
Now I have a US unlocked version without all the bloatware from Telcel, also as a plus I was able to SIM unlock the device as the Telcel ROM is hardlocked and doesn't let you enter a SIM unlock code (didn't show a prompt to input the code when I entered another SIM from a different carrier), flashing the US unlocked RUU did the trick as the prompt for entering the SIM unlock code appeared right away when I inserted my AT&T SIM.
I'm pretty happy with the phone right now without the Telcel stuff, the only thing I'm worried Is not having a backup of the original recovery to return it to stock for warranty, hope it doesn't fail soon lol.
Click to expand...
Click to collapse
Thank you so much for your answer and one more question do you have 4g? ( I believe you do because you supposed to have that us unlocked version)
Thanks!!!
GRIDSpawn said:
Thank you so much for your answer and one more question do you have 4g? ( I believe you do because you supposed to have that us unlocked version)
Thanks!!!
Click to expand...
Click to collapse
Yes, full 4G LTE signal with both Telcel and AT&T, actually is the same hardware and bands AFAIK, you should have no issues with data speed.
Related
Ok guys here is a guide for unlock/s-off/root etc while keeping your radio working, as well as getting your radio working -> http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
This week accidentally (for real, we planned on waiting until we had this PSA published first but goof'd on our build configuration, so it went live early) release SunShine for the HTC 10.
This PSA is need due to how HTC is tying in the keys for userdata encryption on newer devices and firmware. Modern device are encrypted by default, if you set a password or not. This is mostly seamless to those who don't use a password.
The way HTC encrypts the key for user data is to more or less mash up the bootloader lock status, the s-on/s-off status, and the password (for those without a password it is something like "default_password") together. Then the encrypt/decrypt the key.
What this means if you change the lock status, or the s-on/s-off status the phone can no longer decrypt your data, forcing you to wipe the device.
This will happen when you lock the device, unlock the device (which also wipes so who cares), go s-on, or go s-off. This does not matter if you use htcdev.com, SunShine, a new generation javacard, fastboot to go s-on/lock, or manually relock the device. They will all cause this to happen.
To fix this:
On stock recovery:
Do a factory reset
On TWRP:
Enter any password (doesnt matter what)
Then go to advanced, and do a format of userdata (factory reset from twrp will not fix this it must be a format).
So again, if you go s-on/s-off/lock/unlock/whatever and the phone magically is "encrypted" or "wont decrypt" or just won't work right, FORMAT userdata.
Happy Hacking
jcase said:
This week accidentally (for real, we planned on waiting until we had this PSA published first but goof'd on our build configuration, so it went live early) release SunShine for the HTC 10.
This PSA is need due to how HTC is tying in the keys for userdata encryption on newer devices and firmware. Modern device are encrypted by default, if you set a password or not. This is mostly seamless to those who don't use a password.
The way HTC encrypts the key for user data is to more or less mash up the bootloader lock status, the s-on/s-off status, and the password (for those without a password it is something like "default_password") together. Then the encrypt/decrypt the key.
What this means if you change the lock status, or the s-on/s-off status the phone can no longer decrypt your data, forcing you to wipe the device.
This will happen when you lock the device, unlock the device (which also wipes so who cares), go s-on, or go s-off. This does not matter if you use htcdev.com, SunShine, a new generation javacard, fastboot to go s-on/lock, or manually relock the device. They will all cause this to happen.
To fix this:
On stock recovery:
Do a factory reset
On TWRP:
Enter any password (doesnt matter what)
Then go to advanced, and do a format of userdata (factory reset from twrp will not fix this it must be a format).
So again, if you go s-on/s-off/lock/unlock/whatever and the phone magically is "encrypted" or "wont decrypt" or just won't work right, FORMAT userdata.
Happy Hacking
Click to expand...
Click to collapse
Wow. Awesome. Thanks man. Looking forward to getting the device!
jcase said:
This week accidentally (for real, we planned on waiting until we had this PSA published first but goof'd on our build configuration, so it went live early) release SunShine for the HTC 10.
This PSA is need due to how HTC is tying in the keys for userdata encryption on newer devices and firmware. Modern device are encrypted by default, if you set a password or not. This is mostly seamless to those who don't use a password.
The way HTC encrypts the key for user data is to more or less mash up the bootloader lock status, the s-on/s-off status, and the password (for those without a password it is something like "default_password") together. Then the encrypt/decrypt the key.
What this means if you change the lock status, or the s-on/s-off status the phone can no longer decrypt your data, forcing you to wipe the device.
This will happen when you lock the device, unlock the device (which also wipes so who cares), go s-on, or go s-off. This does not matter if you use htcdev.com, SunShine, a new generation javacard, fastboot to go s-on/lock, or manually relock the device. They will all cause this to happen.
To fix this:
On stock recovery:
Do a factory reset
On TWRP:
Enter any password (doesnt matter what)
Then go to advanced, and do a format of userdata (factory reset from twrp will not fix this it must be a format).
So again, if you go s-on/s-off/lock/unlock/whatever and the phone magically is "encrypted" or "wont decrypt" or just won't work right, FORMAT userdata.
Happy Hacking
Click to expand...
Click to collapse
Thanks
Sent from my HTC One M8 using XDA-Developers mobile app
@jcase, @beaups - Excelent job!!!!!!!
--
wysłane z HTCOne (m9) przez Tapatalk v5.8.0
Excuse my ignorance, but does this mean there is a way to root and s-off a verizon HTC 10?
klarthur said:
Excuse my ignorance, but does this mean there is a way to root and s-off a verizon HTC 10?
Click to expand...
Click to collapse
That's what I'd like to know too but sunshine site says no Verizon yet
Ndaoud360 said:
That's what I'd like to know too but sunshine site says no Verizon yet
Click to expand...
Click to collapse
Dang, that stinks. Hopefully it will soon. I went with the HTC 10 over S7 Edge specifically because I thought it would be rooted... I hope I didn't make a mistake
Sent from my LGLS990 using XDA Free mobile app
I think you can root, but there is no support (yet) for S-off.
Stephen said:
I think you can root, but there is no support (yet) for S-off.
Click to expand...
Click to collapse
Really? I hope so... I wasn't able to find anything about rooting the Verizon HTC 10 yet though... Anyone know of something?
jcase said:
This will happen when you lock the device, unlock the device (which also wipes so who cares)
Click to expand...
Click to collapse
Is it still possible to lock/unlock by editing the pg1fs partition once s-off (adding null over the HTCU flag)? If yes, do you know if this will cause the same decryption problem as using "fastboot flash unlocktoken / fastboot oem lock" ?
My Threads
klarthur said:
Really? I hope so... I wasn't able to find anything about rooting the Verizon HTC 10 yet though... Anyone know of something?
Click to expand...
Click to collapse
All I know is that you may be able to unlock bootloader if vzw doesn't lock it for us. Then root should be obtainable via normal methods. I just hope s-off comes soon. I get my 10 on Thursday if vzw is correct with their dates.
Ndaoud360 said:
All I know is that you may be able to unlock bootloader if vzw doesn't lock it for us. Then root should be obtainable via normal methods. I just hope s-off comes soon. I get my 10 on Thursday if vzw is correct with their dates.
Click to expand...
Click to collapse
Doesn't Verizon normally lock bootloaders though? And if they did lock it... what then?
klarthur said:
Doesn't Verizon normally lock bootloaders though? And if they did lock it... what then?
Click to expand...
Click to collapse
You try unlocking with htcdev website but if that fails. IDK let the professional devs here try to do something to get it unlocked for everyone it think that is how all this works
alray said:
Is it still possible to lock/unlock by editing the pg1fs partition once s-off (adding null over the HTCU flag)? If yes, do you know if this will cause the same decryption problem as using "fastboot flash unlocktoken / fastboot oem lock" ?
Click to expand...
Click to collapse
My advice is, and has always been, don't mess with pg1fs or pg2fs, particularly on some newer HTCs.
klarthur said:
Excuse my ignorance, but does this mean there is a way to root and s-off a verizon HTC 10?
Click to expand...
Click to collapse
Not yet, havent had a chance to play with one
What would happen if I tried to s-off a Verizon variant regardless of wheather it's supported or not?
TickleMeHomo69 said:
What would happen if I tried to s-off a Verizon variant regardless of wheather it's supported or not?
Click to expand...
Click to collapse
Brick?
TickleMeHomo69 said:
What would happen if I tried to s-off a Verizon variant regardless of wheather it's supported or not?
Click to expand...
Click to collapse
If you are talking about sunshine then it wont detect your phone and will say cannot obtain root or unlock bootloader. Then you can't continue...
TickleMeHomo69 said:
What would happen if I tried to s-off a Verizon variant regardless of wheather it's supported or not?
Click to expand...
Click to collapse
For sunshine, it will complain about being unable to get root
For javacard and xtc clip (Currently as of this post) it will complain about wrong version
jcase said:
For sunshine, it will complain about being unable to get root
For javacard and xtc clip (Currently as of this post) it will complain about wrong version
Click to expand...
Click to collapse
Do you know what's different about the Verizon branded version of this phone? Just that they still won't unlock the bootloader? Word is that the unlocked version works with Verizon, so I assumed the hardware was similar or the same. I didn't think it was still like previous devices where the CMDA iterations were completely different from the GSM ones.
This thread is to gather technical clarification for those of us who have wondered about this:
If a Google phone (e.g. Pixel / Pixel XL) is purchased from another retailer (e.g. Verizon [with a locked bootloader]), other than the physical hardware, are there any technical differences in SOFTWARE and/or CODING that would restrict flashing OEM firmware from Google after the bootloader is unlocked?
***** (Is the Verizon variant restricted from flashing Google firmware?) *****
My apologies if this has been covered in another thread.
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Radsolutionz said:
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Click to expand...
Click to collapse
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Radsolutionz said:
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Click to expand...
Click to collapse
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
1up1up said:
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
Click to expand...
Click to collapse
Set it up on another computer and start from scratch. Windows 10 has some issues.... If it doesn't work and you want it done just get the device to me and I'll do it for u my self. Message me and I'll work it out with u.
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
suhailtheboss said:
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
No. Until you see Jcase or another dev post a full Google Store conversion for the Verizon Pixel, do not relock your bootloader. That is, if you want to root your Verizon Pixel in the future.
Sent from my Pixel XL using XDA-Developers mobile app
1up1up said:
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
Click to expand...
Click to collapse
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
dbrohrer said:
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
Click to expand...
Click to collapse
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Mike02z said:
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
Click to expand...
Click to collapse
I updated SDK and all is working.
1up1up said:
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Click to expand...
Click to collapse
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
I see... Thank you very much for explaining that.
dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
coolhandz said:
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
Click to expand...
Click to collapse
Unlocking will not disable updates. In Developer Options there is a toggle to disable this. Depending on what you do to your phone after bootloader unlock, disabling this might be important to prevent bootloop during an update.
Aside from root, various flashable mods, custom rom, or custom kernel, there is not really a need to unlock. Your phone is certainly less secure by doing so. If you plan to stay completely stock, keep your bootloader locked.
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
remialfa said:
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
Click to expand...
Click to collapse
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
auceto63 said:
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
Click to expand...
Click to collapse
I did that and yeah it entered this mode but it's not valid bootloader/fastboot mode. It's some service mode to update firmware. Anyway it's not visible in pc as a normal fastboot and I cannot proceed further with unlocking bootloader...
Edit: it's download mode... So as I said it's not fastboot mode.
Anyone can help?
Seriously nobody? I thought this phone has good community and support...
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
charith262 said:
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You can check out UsU. That is an unofficial bootloader unlock
ThePiGuy said:
You can check out UsU. That is an unofficial bootloader unlock
Click to expand...
Click to collapse
Thanks yeah I checked but that's for ARB<=2 devices. I forgot to mention earlier this godforsaken thing is ARB3.
I have an H811 (T-Mo) running firmware H81120p, ARB3. Doesn't seem to be much that can be done with it as far as rooting. It also has no stock recovery, only boots to system.
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
if you use bank apps, install magisk before installing rom, do not get SU
samadee3 said:
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
Click to expand...
Click to collapse
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
SofaSpud said:
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
Click to expand...
Click to collapse
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
ThePiGuy said:
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
Click to expand...
Click to collapse
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Sent from my SAMSUNG-SM-G935A using Tapatalk
SofaSpud said:
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Click to expand...
Click to collapse
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
ThePiGuy said:
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
Click to expand...
Click to collapse
Got it. Guess that it makes sense. ARB prevents rolling back to earlier release than 20o, I'm ok. Will try the BL unlock today then.
Sent from my SAMSUNG-SM-G935A using Tapatalk
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Florimer said:
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Click to expand...
Click to collapse
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Florimer said:
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Click to expand...
Click to collapse
Do you have more details about this? I seem to be in a similar situation than you and I'm struggling to make it work.
Hello,
I have a Sprint Galaxy Note 4 I'd like to unlock. I called sprint and got the unlocking code. I was to wait 72 hours for the phone to be fully unlocked. Then, I needed to swap my sprint SIM with a different network SIM, and the phone would prompt me to enter the code, and that would be it. Unfortunately, I received an email with the following message:
Letting you know your CPO SAM N910 WHT SNGL on line XXXXXXXXXX cannot be
unlocked due to programming restrictions associated with phones like
yours that were manufactured before February, 2015. You can try
providing your master subsidy lock (MSL) code XXXXXX to your new
carrier to find out if it will work on their network.
Keep in mind we can't guarantee your older phone will operate correctly
on another carrier's network. Each wireless provider determines whether
or not they will utilize the MSL code to reprogram a phone for use on
their network.
Click to expand...
Click to collapse
I put a different SIM in my phone, boot it up, and I get an invalid SIM error, but the phone does not prompt me to enter a code.
I have read and seen multiple Note 4, including the Sprint variant, being unlocked. Does anyone know what I need to do to unlock it?
Thanks
Aloupha said:
Hello,
I have a Sprint Galaxy Note 4 I'd like to unlock. I called sprint and got the unlocking code. I was to wait 72 hours for the phone to be fully unlocked. Then, I needed to swap my sprint SIM with a different network SIM, and the phone would prompt me to enter the code, and that would be it. Unfortunately, I received an email with the following message:
I put a different SIM in my phone, boot it up, and I get an invalid SIM error, but the phone does not prompt me to enter a code.
I have read and seen multiple Note 4, including the Sprint variant, being unlocked. Does anyone know what I need to do to unlock it?
Thanks
Click to expand...
Click to collapse
Use this tool to permanently unlock your device.
Download link for tool is in video description.
Screw the carrier
By this tool you can unlock all Samsung sprint devices.
https://youtu.be/tkrI7PTaZqA
Tool is free but watch carefully and follow instructions exactly as shown in video.
Let me know if it worked for you.
Trex888 said:
Use this tool to permanently unlock your device.
Download link for tool is in video description.
Screw the carrier
By this tool you can unlock all Samsung sprint devices.
https://youtu.be/tkrI7PTaZqA
Tool is free but watch carefully and follow instructions exactly as shown in video.
Let me know if it worked for you.
Click to expand...
Click to collapse
Thanks - it's kind of hard to follow the instructions. It's unclear what he is doing.
It would appears that you first place the phone in download mode. In his instruction, he attempted to do that, but the phone rebooted. Is this a necessary step? Then he put the phone in recovery mode. But after that, he doesn't show you want happens. He simply moves on to unlocking a different phone. Is simply putting the phone in recovery mode unlock it? I doubt it... do I click on the Unlock button while in download mode to unlock it? It's not clear
Aloupha said:
Thanks - it's kind of hard to follow the instructions. It's unclear what he is doing.
It would appears that you first place the phone in download mode. In his instruction, he attempted to do that, but the phone rebooted. Is this a necessary step? Then he put the phone in recovery mode. But after that, he doesn't show you want happens. He simply moves on to unlocking a different phone. Is simply putting the phone in recovery mode unlock it? I doubt it... do I click on the Unlock button while in download mode to unlock it? It's not clear
Click to expand...
Click to collapse
Follow these steps exactly
Before you begin you must have samsung usb drivers installed in your windows pc.
1 download cdma yemen tool that i mentioned in my earlier replies.
2 put your phone in adb mode by dialing ##3424# and choose adb+dm (very important)
3 reboot device
4 open tool and connect your device via usb cable (WATCH OUT CAREFULLY FOR ANY POP UP WINDOW ON YOUR PHONE YOU MUST ALLOW PERMISSION TO CONNECT DEVICE WITH TOOL.
5 inside tool click on port/adb and select your device.
6 choose your correct model N910P of you have Note 4 sprint.
6 click UNLOCK TAB in tool and wait until your device will reboot automatically.
thats it.
After reboot hopefully you have permanently unlocked device.
If your device successfully unlocked then dial ##3424# and select mtp+adb back to normal.
The guy is showing in video all the stuff that this tool can do so dont go to download mode or recovery or anything because that's for removing frp lock and other stuff.
Let me know if it worked for you.
By the way if you are on latest QI5 firmware i am not 100% sure this tool will work because QI5 has latest bootloader/modem and it's not easy to unlock.
If this tool did not work for you let me know i have workaround.
Good luck
Trex888 said:
Follow these steps exactly
Before you begin you must have samsung usb drivers installed in your windows pc.
1 download cdma yemen tool that i mentioned in my earlier replies.
2 put your phone in adb mode by dialing ##3424# and choose adb+dm (very important)
3 reboot device
4 open tool and connect your device via usb cable (WATCH OUT CAREFULLY FOR ANY POP UP WINDOW ON YOUR PHONE YOU MUST ALLOW PERMISSION TO CONNECT DEVICE WITH TOOL.
5 inside tool click on port/adb and select your device.
6 choose your correct model N910P of you have Note 4 sprint.
6 click UNLOCK TAB in tool and wait until your device will reboot automatically.
thats it.
After reboot hopefully you have permanently unlocked device.
If your device successfully unlocked then dial ##3424# and select mtp+adb back to normal.
The guy is showing in video all the stuff that this tool can do so dont go to download mode or recovery or anything because that's for removing frp lock and other stuff.
Let me know if it worked for you.
By the way if you are on latest QI5 firmware i am not 100% sure this tool will work because QI5 has latest bootloader/modem and it's not easy to unlock.
If this tool did not work for you let me know i have workaround.
Good luck
Click to expand...
Click to collapse
I am on QI5, and I didn't see a adb+dm option. I did see a DM + MODEM + ADM option under QUALCOMM USB SETTING (see attached screenshot), so I selected that.
The tool says Unlock Done With out Root... but it doesn't appear that the phone was indeed unlocked.
What's the workaround you have?
Aloupha said:
I am on QI5, and I didn't see a adb+dm option. I did see a DM + MODEM + ADM option under QUALCOMM USB SETTING (see attached screenshot), so I selected that.
The tool says Unlock Done With out Root... but it doesn't appear that the phone was indeed unlocked.
What's the workaround you have?
Click to expand...
Click to collapse
Yes DM+MODEM+ADM i was meaning.
The workaround i have is you have to flash Twrp RECOVERY and have to flash "ENG ROM" DONT FLASH ENG BOOTLOADER OR BASEBAND YOU WILL END UP UNKNOWN BASEBAND AND NULL IMEI.
Flash the rom from twrp and Also you have to flash supersu.zip to get full root with eng rom.
after that you have to use tool "Z3X SAMSUNG TOOLS PRO v27 or higher"
I cant share links here on xda for z3x because its heavily paid tool but if you search on youtube "z3x pro cracked" you will get 100s of videos with links to download.
HERE IS THE LINK FOR ENG ROM BY @freeza thanks to him.
https://forum.xda-developers.com/no...leakmm-sm-n910p-touchwiz-marshmallow-t3327350
After flashing eng rom the rom will take 35 minutes to boot so be patient and wait and also make sure battery is fully charged.
After that enable DM+MODEM+ADM as i mentioned earlier and you can unlock from z3x domestic use for american sim or unlock for international sim use.
Once phone is unlocked you must have to flash QI5 stock firmware via odin and do factory reset from stock recovery and dont worry the unlocking will stick permanently.
I personally did this method on QI5 ON my own device and it worked just fine.
I REPEAT DO NOT FLASH ENG BOOTLOADER OR MODEM OTHERWISE YOU WILL SCREW YOUR DEVICE COMPLETELY.
Cant explain more you got the idea i guess...
Good luck.
Trex888 said:
Yes DM+MODEM+ADM i was meaning.
The workaround i have is you have to flash Twrp RECOVERY and have to flash "ENG ROM" DONT FLASH ENG BOOTLOADER OR BASEBAND YOU WILL END UP UNKNOWN BASEBAND AND NULL IMEI.
Flash the rom from twrp and Also you have to flash supersu.zip to get full root with eng rom.
after that you have to use tool "Z3X SAMSUNG TOOLS PRO v27 or higher"
I cant share links here on xda for z3x because its heavily paid tool but if you search on youtube "z3x pro cracked" you will get 100s of videos with links to download.
HERE IS THE LINK FOR ENG ROM BY @freeza thanks to him.
https://forum.xda-developers.com/no...leakmm-sm-n910p-touchwiz-marshmallow-t3327350
After flashing eng rom the rom will take 35 minutes to boot so be patient and wait and also make sure battery is fully charged.
After that enable DM+MODEM+ADM as i mentioned earlier and you can unlock from z3x domestic use for american sim or unlock for international sim use.
Once phone is unlocked you must have to flash QI5 stock firmware via odin and do factory reset from stock recovery and dont worry the unlocking will stick permanently.
I personally did this method on QI5 ON my own device and it worked just fine.
I REPEAT DO NOT FLASH ENG BOOTLOADER OR MODEM OTHERWISE YOU WILL SCREW YOUR DEVICE COMPLETELY.
Cant explain more you got the idea i guess...
Good luck.
Click to expand...
Click to collapse
The URL for the ROM is dead. Do you by any chance have alternate URL?
Aloupha said:
The URL for the ROM is dead. Do you by any chance have alternate URL?
Click to expand...
Click to collapse
Here
https://mega.nz/#!vQ9VDJIS!Gv85h3Y3K44ym9BlRvNvJEfkiXHfO__AbJHElZycUnY
Btw try first the cdma yemen tool to.unlock with this rom with root. Maybe it can work.
It appears that I am not able to install TWRP... I install it via Odin from AP, and the install is successful. But when I try to boot into recovery, I get the stock recovery....
I tried TWRP 3.1.1 and 3.2.3... same thing. What am I not doing?
Aloupha said:
It appears that I am not able to install TWRP... I install it via Odin from AP, and the install is successful. But when I try to boot into recovery, I get the stock recovery....
I tried TWRP 3.1.1 and 3.2.3... same thing. What am I not doing?
Click to expand...
Click to collapse
Open odin and uncheck auto reboot in odin options
Choose AP and flash twrp
After Odin shows pass remove battery
Insert battery and Boot straight into twrp by volume up+home+ power
If your phone reboots after flashing twrp the system overwrites the stock recovery over twrp thats why you are losing twrp so do not reboot system after flashing twrp.
Once you booted into twrp then if will stick permanently and stock recovery will never show up.
If i was helpful then consider hit thumbs up on my replies.
Thanks! It took a while with multiple flashes, but I think it is fully unlocked now. I am able to put a Verizon SIM card in it and get no sim card error message.
Aloupha said:
Thanks! It took a while with multiple flashes, but I think it is fully unlocked now. I am able to put a Verizon SIM card in it and get no sim card error message.
Click to expand...
Click to collapse
Put sim card in phone then
Try dial ##72786# and press yes
Phone should reboot then you should get reception and.no sim massage won't show up.
Usure if anyone still using this. But I just got my phone unlocc using it on crikket/att. Unsure why you got a 7 wait but I was able to make phones and use internet immediately after I unlocc the phone. The only problem I'm facing is being able to use 4g o the phone.
Zaiaku said:
Usure if anyone still using this. But I just got my phone unlocc using it on crikket/att. Unsure why you got a 7 wait but I was able to make phones and use internet immediately after I unlocc the phone. The only problem I'm facing is being able to use 4g o the phone.
Click to expand...
Click to collapse
You won't get 4g/lte because n910p sprint note 4 is CDMA model and you need GSM model for 4g on at&t/cricket.
I would like to thank everyone for there support for this most awesome but difficult phone. I have an unlocked US LG V30+ phone which an error in cross flashing accidently caused my phone to loose everything I needed to use LGUP. Does anyone know of an exe rom to flash on this phone to regain download option or a full restore to start fresh to do the rooting the right way? I know some mobile devices have exe for full restore but haven't found one for this phone yet.
Thanks again and I hope for a possible positive answer.
mcarden2006 said:
I would like to thank everyone for there support for this most awesome but difficult phone. I have an unlocked US LG V30+ phone which an error in cross flashing accidently caused my phone to loose everything I needed to use LGUP. Does anyone know of an exe rom to flash on this phone to regain download option or a full restore to start fresh to do the rooting the right way? I know some mobile devices have exe for full restore but haven't found one for this phone yet.
Thanks again and I hope for a possible positive answer.
Click to expand...
Click to collapse
Your bootloader is NOT relocked unless you flashed fastboot command to re-lock it.
Your bootloader is still unlocked.
ChazzMatt said:
Your bootloader is NOT relocked unless you flashed fastboot command to re-lock it.
Your bootloader is still unlocked.
Click to expand...
Click to collapse
It's locked.
mcarden2006 said:
It's locked.
Click to expand...
Click to collapse
Then start over to unlock bootloader https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193