Related
Im returning my Gnex as I want it on Sim Free. 500mb data is just not enough.
How do I go about relocking the bootloader and unrooting the phone?
Im on OS X and I rooted and unlocked it with Pauls Superboot
For the moment, you don't.
Can't you just remove the Superuser apk's and then run "fastboot oem lock" (or relock not sure)!
I have never tried this and don't have a device so better wait for someone knowledgeable to post!
Check the Nexus S forums, should be in Dev section on how to re-lock bootloader. It's either relock or lock or re-lock. As for Superuser, download Titanium backup and use it to remove it.
fastboot lock/relock should not work unless it's an engineering device/some exploit is used.
Not sure about removing root, but I can confirm that the following command works fine:
fastboot oem lock
wilskywalker said:
Not sure about removing root, but I can confirm that the following command works fine:
fastboot oem lock
Click to expand...
Click to collapse
Cheers. I thought that might work. Now to unroot it and remove the evidence..
Sent from my Galaxy Nexus using Tapatalk
Evostance said:
Cheers. I thought that might work. Now to unroot it and remove the evidence..
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I would think a factory reset should return you to stock, if not, I'm sure someone will have the original boot.img and you can flash that via fastboot. Then factory reset again afterwards to be on the safe side. Finally fastboot oem lock and you're ready to go buddy!
Does fastboot oem lock remove the unlocked padlock image on boot?
Yes
Sent from my Galaxy Nexus using xda premium
Here's a fairly simple fix to a lingering issue that affected the VZW m9. The fix came about during a discussion with the repair efforts @beaups made on one of the many phones that either end up without service or dead in his hands. Guess you could say this was a lemons to lemonade moment. The key to this was the realization that unlike the m8, the stock recovery on the m9 forward NO LONGER resets the golden nv radion settings. This process will do just that....
Remove volte from account. (If already enabled).
Then latest ruu and factory reset
Run this fastboot commands while booted to the white bootloader screen. For the HTC 10 remove the _ from the modem name.
fastboot erase modem_st1
fastboot erase modem_st2
Then reboot and try volte activation.
Thanks for this, will be testing out once i have the chance to go through the process.
Hey gang-
Just wanted to drop a note that i'm moving on. As such, I have requested my threads to be closed as I won't be around to support them much anymore. Any download links (if applicable) will also be removed shortly as well.
Thanks and peace out.
@dottat thanks for reopening the thread and I know you don't offer much support but could you shed some light on the details on how to remove Volte from your account and if you can flash custom ruu vs going back to stock and flashing stock ruu with stock recovery.
Sent using Tapatalk
I did the steps and I get "We encountered a problem activating Advanced Calling 1.0. Please try again later." Any ideas @dottat?
EDIT: Went to my account and enabled it on VZW. Rebooted my device and it was enabled on my device. Awesome!
Flyhalf205 said:
I did the steps and I get "We encountered a problem activating Advanced Calling 1.0. Please try again later." Any ideas @dottat?
EDIT: Went to my account and enabled it on VZW. Rebooted my device and it was enabled on my device. Awesome!
Click to expand...
Click to collapse
How did you deactivate it? Did you flash custom ruu or stock
Sent using Tapatalk
Tommydorns said:
How did you deactivate it? Did you flash custom ruu or stock
Sent using Tapatalk
Click to expand...
Click to collapse
I deactivated using the MyVerizon app. Once loaded up just turn deactivate the feature.
Flyhalf205 said:
I deactivated using the MyVerizon app. Once loaded up just turn deactivate the feature.
Click to expand...
Click to collapse
OK. Thank you what about the ruu which one did you flash? Are you using the new venom rom
Sent using Tapatalk
Tommydorns said:
@dottat thanks for reopening the thread and I know you don't offer much support but could you shed some light on the details on how to remove Volte from your account and if you can flash custom ruu vs going back to stock and flashing stock ruu with stock recovery.
Sent using Tapatalk
Click to expand...
Click to collapse
The basic premise of this fix has nothing to do with stock recovery. It's actually about doing what stock recovery USED to do for us. It used to reset nv radio info by wiping the modems during a factory reset. It no longer does so manually wiping them does the same thing. You probably could do it without RUU'ing as long as you know you are on vzw firmware/radios only.
Tommydorns said:
OK. Thank you what about the ruu which one did you flash? Are you using the new venom rom
Sent using Tapatalk
Click to expand...
Click to collapse
I used the only one that is available right now. I use my own stock rom.
dottat said:
The basic premise of this fix has nothing to do with stock recovery. It's actually about doing what stock recovery USED to do for us. It used to reset nv radio info by wiping the modems during a factory reset. It no longer does so manually wiping them does the same thing. You probably could do it without RUU'ing as long as you know you are on vzw firmware/radios only.
Click to expand...
Click to collapse
Thank you for the clarification. I thought I had to go back to stock rom, that's why I thought stock recovery. So as long as I have Verizon firmware / radios I can those fast boot flash those commands on Viper 5.0 after removing HD voice from my plan than reactive it after the commands ...
Sent using Tapatalk
Tommydorns said:
Thank you for the clarification. I thought I had to go back to stock rom, that's why I thought stock recovery. So as long as I have Verizon firmware / radios I can those fast boot flash those commands on Viper 5.0 after removing HD voice from my plan than reactive it after the commands ...
Sent using Tapatalk
Click to expand...
Click to collapse
Can't hurt it...
dottat said:
Can't hurt it...
Click to expand...
Click to collapse
OK... After setting up adb and fastboot, deactivating HD voice, putting the phone in Download Mode, making sure fastboot works by testing the reboot command. I tried those commands and it's basically saying that "erase" is not a valid command for modem_st1 and modem_st2 in CMD. Rebooted and reactivated HD voice on plan and phone and trying and it's saying I don't have a Verizon SIM on the phone, (It was saying this before) so I reboot to get data working again. I'm still on Viper 5.0. I did flash the Marshmellow RUU before flashing 4.3 back in February. Could I have lost a radio or something. @hallstevenson did you ever try it and get it to work?
Sent using Tapatalk
Tommydorns said:
OK... After setting up adb and fastboot, deactivating HD voice, putting the phone in Download Mode, making sure fastboot works by testing the reboot command. I tried those commands and it's basically saying that "erase" is not a valid command for modem_st1 and modem_st2 in CMD. Rebooted and reactivated HD voice on plan and phone and trying and it's saying I don't have a Verizon SIM on the phone, (It was saying this before) so I reboot to get data working again. I'm still on Viper 5.0. I did flash the Marshmellow RUU before flashing 4.3 back in February. Could I have lost a radio or something. @hallstevenson did you ever try it and get it to work?
Sent using Tapatalk
Click to expand...
Click to collapse
Take away the _ on the modem name
Sent from my HTC6545LVW using Tapatalk
dottat said:
Take away the _ on the modem name
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Thank you for the help.. It's keeps telling me failure, erase st1 is not supported. It will also say partition table does not exist. Ive verified I do have the corrected radio and firmware. I've tried both commands with modemst1 and modem_st1 with the same failure message in CMD.
Sent using Tapatalk
Tommydorns said:
Thank you for the help.. It's keeps telling me failure, erase st1 is not supported. It will also say partition table does not exist. Ive verified I do have the corrected radio and firmware. I've tried both commands with modemst1 and modem_st1 with the same failure message in CMD.
Sent using Tapatalk
Click to expand...
Click to collapse
In bootloader or download mode?
Sent from my HTC6545LVW using Tapatalk
Both. It doesn't have a fastboot where it says fastboot mode like on previous devices so I take it you use download mode. So I tried it in both. fastboot reboot command works in both modes.
Sent using Tapatalk
Tommydorns said:
Both. It doesn't have a fastboot where it says fastboot mode like on previous devices so I take it you use download mode. So I tried it in both. fastboot reboot command works in both modes.
Sent using Tapatalk
Click to expand...
Click to collapse
You are doing it wrong.
Sent from my HTC6545LVW using Tapatalk
Oh Ok, what am I doing wrong? I would love to get this to work. Thank you for your help.
Sent using Tapatalk
dottat said:
You are doing it wrong.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
OK, these are my steps, USB debugging enabled on Dev Options. Disabled HD Voice from My Verizon go into bootloader hook phone to PC type in CMD Those commands it says FAILED (remote: Partition modest 2 erase not supported) I've also typed in fastboot oem rebootRUU which it takes me to a blank screen HTC logo on it and gives me a warning then I typed those commands still same Failed message in CMD. Is there something I'm missing. Haven't had anybody come out and say they were successful. Only thing I haven't done it go all to stock RUU bit I have the latest radios and firmware so I don't know
Sent using Tapatalk
Hi guys
Noob here, but with a somewhat decent understanding of flashing and I'm kinda riddled by my current situation.
The current state of my phone is:
Locked bootloader.
Access to TWRP (2.8). Access to MTP and install function within TWRP.
OEM unlocking NOT allowed (since I can't boot into the OS).
So the logical thing to do (and as req'ed in dozens of threads with the same problem) would be to flash a custom ROM via TWRP's Install function, boot into it, enable OEM unlocking, unlock the bootloader and do whatever I want from there.
Except ... that all the ROMs I flash are stuck in bootloop. They go through the flashing process, TWRP shows success and then ... an endless android (or custom) loop when I reboot. I tried flashing PureNexus, Cataclysm and Chroma.
Any idea on what might be going wrong here (I thought of the vendor.img I have on right now being a wrong one, but I have no idea how to flash the good one without access to the vendor partition) ?
Any help would be appreciated, I saw that I could go through the LG flashtool/TOT unbricking method but I don't have i. a PC (I'm on a Mac) or ii. an original Nexus USB cable so that would put me back a few days.
Cheers
You can't flash a custom ROM with a locked bootloader....
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
You need to flash all the original stock images via ADB and restart from there
TW1ST3D1NS4N3 said:
You can't flash a custom ROM with a locked bootloader....
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
You need to flash all the original stock images via ADB and restart from there
Click to expand...
Click to collapse
Yes, you can in recovery ...
Apparently not. Let me rephrase. You cannot flash a custom ROM with your bootloader locked and your phone work properly.... reflash all stock images through ADB. Take the advice or don't.
How did you get in this sh!tuation? Did you OEM lock with TWRP installed?
Anyway, the TOT method is most likely the only way to get it going again. I wouldn't waste my time doing anything else. Ask a friend/family member to borrow a computer with windows on it.
PiousInquisitor said:
How did you get in this sh!tuation? Did you OEM lock with TWRP installed?
Anyway, the TOT method is most likely the only way to get it going again. I wouldn't waste my time doing anything else. Ask a friend/family member to borrow a computer with windows on it.
Click to expand...
Click to collapse
Not sure how I ended up here. :silly:
Is it true you absolutely need original Nexus USB cable for it to work ?
chafouin said:
Not sure how I ended up here. :silly:
Is it true you absolutely need original Nexus USB cable for it to work ?
Click to expand...
Click to collapse
No. Likely any USB A to C will work.
Sent from my DROID RAZR HD using Tapatalk
TW1ST3D1NS4N3 said:
Apparently not. Let me rephrase. You cannot flash a custom ROM with your bootloader locked and your phone work properly.... reflash all stock images through ADB. Take the advice or don't.
Click to expand...
Click to collapse
I'm thankful for any help, sorry if I was dissmisive. I'm not aware of flashing through ADB, just sideloading.
I can flash via fastboot, but can't right now because of my locked bootloader.
Presently I can sideload via ADB in recovery (which amounts to the same as flashing from recovery if I understand correctly ?) but any other flashing/thinkering via fastboot/ADB is verboten because my bootloader is locked.
If you're thinking of something else I'd be glad if you could detail your thinkings and the steps I'd need to make
@chafouin you just reminded me that Google is posting full OTAs. At least for the Android N developer previews. So theoretically you could factory reset from recovery and sideload an OTA. OTAs don't require an unlocked bootloader.
Sent from my DROID RAZR HD using Tapatalk
Just download the latest Rom from google site and run flashall file. Simple.
Sent from my Nexus 5X using Tapatalk
milan187 said:
Just download the latest Rom from google site and run flashall file. Simple.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
How do you propose he do that with a locked bootloader?
Sent from my DROID RAZR HD using Tapatalk
PiousInquisitor said:
How do you propose he do that with a locked bootloader?
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
The stock rom? Why is that a problem? Put the device in fastboot and load. Locked bootloader does not allow custom roms. It allows stock.
Sent from my Nexus 5X using Tapatalk
milan187 said:
The stock rom? Why is that a problem? Put the device in fastboot and load. Locked bootloader does not allow custom roms. It allows stock.
Click to expand...
Click to collapse
In my experience *on the 5x* locked bootloader doesn't allow you to flash factory images.
I haven't tested with latest bootloader, but that has been he case with past bootloaders.
Other manufacturers and phone models handle things differently.
You can however now flash stock using the FULL OTA provided on the same factory image site. In that case you would use adb sideload, not fastboot.
sfhub said:
In my experience *on the 5x* locked bootloader doesn't allow you to flash factory images.
I haven't tested with latest bootloader, but that has been he case with past bootloaders.
Other manufacturers and phone models handle things differently.
You can however now flash stock using the FULL OTA provided on the same factory image site. In that case you would use adb sideload, not fastboot.
Click to expand...
Click to collapse
Hmm I flashed mine without unlocking bootloader...
Sent from my Nexus 5X using Tapatalk
chafouin said:
Hi guys
Noob here, but with a somewhat decent understanding of flashing and I'm kinda riddled by my current situation.
The current state of my phone is:
Locked bootloader.
Access to TWRP (2.8). Access to MTP and install function within TWRP.
OEM unlocking NOT allowed (since I can't boot into the OS).
So the logical thing to do (and as req'ed in dozens of threads with the same problem) would be to flash a custom ROM via TWRP's Install function, boot into it, enable OEM unlocking, unlock the bootloader and do whatever I want from there.
Except ... that all the ROMs I flash are stuck in bootloop. They go through the flashing process, TWRP shows success and then ... an endless android (or custom) loop when I reboot. I tried flashing PureNexus, Cataclysm and Chroma.
Any idea on what might be going wrong here (I thought of the vendor.img I have on right now being a wrong one, but I have no idea how to flash the good one without access to the vendor partition) ?
Any help would be appreciated, I saw that I could go through the LG flashtool/TOT unbricking method but I don't have i. a PC (I'm on a Mac) or ii. an original Nexus USB cable so that would put me back a few days.
Cheers
Click to expand...
Click to collapse
Have you tried factory reset from TWRP?
If I were you I wouldn't try to flash to stock unless as last resort. Locked bootloader with TWRP installed is better diagnostic situation that locked bootloader with stock recovery installed. If you try to flash to stock it is too easy to overwrite your TWRP with stock recovery (it happens behind the scenes)
That is ok, if you are out of options, but I would exhaust all other options first.
milan187 said:
The stock rom? Why is that a problem? Put the device in fastboot and load. Locked bootloader does not allow custom roms. It allows stock.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You cannot flash the factory images with a locked bootloader. Google it. Look at Google's own documentation.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
You cannot flash the factory images with a locked bootloader. Google it. Look at Google's own documentation.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Sorry, my mistake. Mine must have been unlocked. This is my first Nexus so I'm used to the fact that factory images can be loaded with locked bootloader.
Sent from my Nexus 5X using Tapatalk
milan187 said:
Sorry, my mistake. Mine must have been unlocked. This is my first Nexus so I'm used to the fact that factory images can be loaded with locked bootloader.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
On what phone? I've never heard of that.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
On what phone? I've never heard of that.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've done it recently on LG G4 and BlackBerry PRIV where I used flashall command.
Neither has a possibility for bootloader unlock.
Sent from my Nexus 5X using Tapatalk
I've had other phones that allow flash if things are signed (which factory images are on those phones).
I unenrolled from the Android beta program yesterday but they still haven't sent an OTA to rollback to N. Can I use wugz to manually do it?
Sent from my Pixel XL using XDA-Developers Legacy app
ucpro said:
I unenrolled from the Android beta program yesterday but they still haven't sent an OTA to rollback to N. Can I use wugz to manually do it?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Have you tried just flashing the latest N factory image or are you trying to retain data and such?
I'd wipe data just to be safe
Sent from my Pixel XL using XDA-Developers Legacy app
Jammol said:
Have you tried just flashing the latest N factory image or are you trying to retain data and such?
Click to expand...
Click to collapse
On Verizon you cannot flash the latest public image. The bootloader is too old coming from Android O
fresnored said:
On Verizon you cannot flash the latest public image. The bootloader is too old coming from Android O
Click to expand...
Click to collapse
What?
I have an unlocked pixel. I just wanna make sure nothing will mess up if I try to flash an image through wugz
Sent from my Pixel XL using XDA-Developers Legacy app
ucpro said:
I have an unlocked pixel. I just wanna make sure nothing will mess up if I try to flash an image through wugz
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I guess wugz is a toolkit right? I'm not sure why you'd need to use anything other than the bootloader menu to flash a factory image. Extract the image you want, in bl menu (on the computer) just type flash-all if you're on Windows, walk away when it starts and come back in 10 minutes. Done.
bobby janow said:
I guess wugz is a toolkit right? I'm not sure why you'd need to use anything other than the bootloader menu to flash a factory image. Extract the image you want, in bl menu (on the computer) just type flash-all if you're on Windows, walk away when it starts and come back in 10 minutes. Done.
Click to expand...
Click to collapse
That's what I was thinking. And the fact that a full wipe is desired makes it even easier.
Yes wugz is a root toolkit but it also let's you restore your phone with whatever version of Android you want, and also downloads the image for you. I haven't tried doing it through the bootloader
Sent from my Pixel XL using XDA-Developers Legacy app
ucpro said:
Yes wugz is a root toolkit but it also let's you restore your phone with whatever version of Android you want, and also downloads the image for you. I haven't tried doing it through the bootloader
Click to expand...
Click to collapse
Are you familiar with flashing Google factory images? If not, @CZ Eddie has a nice tutorial in the guides sub-forum.
I do that through ADB right?
Sent from my Pixel XL using XDA-Developers Legacy app
ucpro said:
I do that through ADB right?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, you do it while in the bootloader menu from the computer. You just need to make sure your device is recognized in bootloader mode on the computer with the command fastboot devices. It should show up. Then flash to your hearts content. Just download and extract the correct image to the correct folder on the computer.
Ok I'll give it a shot
Sent from my Pixel XL using XDA-Developers Legacy app
i'm not having any luck with adb. It doesn't show my device in fastboot OR recovery. When the phone is booted up, adb works fine. Can I just put the image zip on the phone and install through revovery?
ucpro said:
i'm not having any luck with adb. It doesn't show my device in fastboot OR recovery. When the phone is booted up, adb works fine. Can I just put the image zip on the phone and install through revovery?
Click to expand...
Click to collapse
No I think you should properly learn how to use fastboot and adb before continuing any further.
What fastboot version are you currently using.
What output do you get when you type fastboot devices with your device in the bl menu. Let's figure out you're fastboot issues first and then worry about flashing the image(which will be the easy part).
toknitup420 said:
No I think you should properly learn how to use fastboot and adb before continuing any further.
What fastboot version are you currently using.
What output do you get when you type fastboot devices with your device in the bl menu. Let's figure out you're fastboot issues first and then worry about flashing the image(which will be the easy part).
Click to expand...
Click to collapse
Wise words. Not replying to the OP so hopefully he reads down a bit. It looks like his drivers are not working, i.e. the fastboot ones since he can adb. If he's on Windows then device manager should show an exclamation mark or unknown device. There is a fastboot installation, let me take a look see if I can find it. Ok here ya go. https://www.androidusbdrivers.com/google-pixel-usb-drivers/ I actually didn't need to do that exact procedure but I've been fastbooting for some time.
To the OP. You need to get 'fastboot devices' command to show your device when connected via usb to your computer and in bootloader mode. Once it sees the device the rest is child's play.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
ucpro said:
i'm not having any luck with adb. It doesn't show my device in fastboot OR recovery. When the phone is booted up, adb works fine. Can I just put the image zip on the phone and install through recovery?
Click to expand...
Click to collapse
See above.
bobby janow said:
Wise words. Not replying to the OP so hopefully he reads down a bit. It looks like his drivers are not working, i.e. the fastboot ones since he can adb. If he's on Windows then device manager should show an exclamation mark or unknown device. There is a fastboot installation, let me take a look see if I can find it. Ok here ya go. https://www.androidusbdrivers.com/google-pixel-usb-drivers/ I actually didn't need to do that exact procedure but I've been fastbooting for some time.
To the OP. You need to get 'fastboot devices' command to show your device when connected via usb to your computer and in bootloader mode. Once it sees the device the rest is child's play.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
See above.
Click to expand...
Click to collapse
I can get the phone to show on the computer in adb when the phone is booted up, but it won't show while in fastboot. I use the same command 'adb devices' when the phone is booted up and also in fastboot. I looked through my device manager and there's no exclamation points anywhere on both computers that I've tried
ucpro said:
I can get the phone to show on the computer in adb when the phone is booted up, but it won't show while in fastboot. I use the same command 'adb devices' when the phone is booted up and also in fastboot. I looked through my device manager and there's no exclamation points anywhere on both computers that I've tried
Click to expand...
Click to collapse
You need to type "fastboot devices" when in the bootloader.
Ok I'll give it a shot later tonight
Hi just got the pixel 2 xl. Came with 8.1 updated to 9 now I'm getting each security update. Can I just sideload the latest ota and save a whole lot of time?
No. You'll have to go through them all unless you unlock your bootloader and flash the June factory image.
Sent from my Pixel 2 XL using XDA Labs
MrMeeseeks said:
No. You'll have to go through them all unless you unlock your bootloader and flash the June factory image.
Click to expand...
Click to collapse
Ah unlocking the bootloader is no big deal. Better than sitting through 6 more security updates. Thanks for the info.
mojorisin7178 said:
Ah unlocking the bootloader is no big deal. Better than sitting through 6 more security updates. Thanks for the info.
Click to expand...
Click to collapse
Just remember not to relock the bootloader unless you are 100% positive the phone is 100% stock. Personally, if I had a need to relock (which I can't think of a single reason why I would) I would flash a full factory image using the flash-all.bat file with the -w still in there to allow it to do a complete wipe off the phone. Just my personal paranoia but these threads are littered with the wreckage of uninformed locking of bootloaders...
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
Just remember not to relock the bootloader unless you are 100% positive the phone is 100% stock. Personally, if I had a need to relock (which I can't think of a single reason why I would) I would flash a full factory image using the flash-all.bat file with the -w still in there to allow it to do a complete wipe off the phone. Just my personal paranoia but these threads are littered with the wreckage of uninformed locking of bootloaders...
Click to expand...
Click to collapse
That's good advice. Thank you
mojorisin7178 said:
That's good advice. Thank you
Click to expand...
Click to collapse
I'd add to that to flash both slots with a full factory wipe before relocking.