Develop Bugs

Issue with upgrading my verizon galaxy nexus to 4.0.4. Need Help!!!!

For some reason my phone downloads the upgrade...and on clicking restart and install...it stays at Google logo...
it is stock unrooted. the phone never has been rooted and has always been stock.
any help/pointers folks??
Sent from my Galaxy Nexus using XDA
Sent from my Galaxy Nexus using XDA

afma_afma said:
For some reason my phone downloads the upgrade...and on clicking restart and install...it stays at Google logo...
it is stock unrooted. the phone never has been rooted and has always been stock.
any help/pointers folks??
Sent from my Galaxy Nexus using XDA
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Not sure what the issue could be if your device has always been stock.
The only thing I can suggest is re-flash the stock images (see here). That way you will know for sure that everything is OK, and the update will install automatically.

efrant said:
Not sure what the issue could be if your device has always been stock.
The only thing I can suggest is re-flash the stock images (see here). That way you will know for sure that everything is OK, and the update will install automatically.
Click to expand...
Click to collapse
thank you for the suggestion....I am going to wait and see if there are other easier methods...if not ..I will try yours ...
Sent from my Galaxy Nexus using XDA

efrant said:
Not sure what the issue could be if your device has always been stock.
The only thing I can suggest is re-flash the stock images (see here). That way you will know for sure that everything is OK, and the update will install automatically.
Click to expand...
Click to collapse
also one more question....I feel the issue is with recovery...can't I just flash the recovery img alone?
Sent from my Galaxy Nexus using XDA

afma_afma said:
also one more question....I feel the issue is with recovery...can't I just flash the recovery img alone?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Yes you can!
Sent from my Galaxy Nexus using Tapatalk 2

so here are the steps I came up with after I went through the thread you has posted..
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader.
5) Flash the recovery partition: fastboot flash recovery recovery.img
6) Reboot: fastboot reboot
does this sound right?
Sent from my Galaxy Nexus using XDA

afma_afma said:
so here are the steps I came up with after I went through the thread you has posted..
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader.
5) Flash the recovery partition: fastboot flash recovery recovery.img
6) Reboot: fastboot reboot
does this sound right?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Is your bootloader locked or unlocked?
If it is unlocked, you can skip your step 2.
If it is locked, then it will wipe everything anyway, so might as well flash the other images just to be 100% sure you are stock.
Make sure that all the images are from the mysid ICL53F factory file.

efrant said:
Is your bootloader locked or unlocked?
If it is unlocked, you can skip your step 2.
If it is locked, then it will wipe everything anyway, so might as well flash the other images just to be 100% sure you are stock.
Make sure that all the images are from the mysid ICL53F factory file.
Click to expand...
Click to collapse
My boot loader is locked and am already 100% stock...somehow the stock recovery is corrupted ..and I have never rooted this phone..never did any mods...
this is why I want to just try and reinstall the stock recovery alone...if that does not fix my issue then I will install everything...I will keep you posted...thank you.
Sent from my Galaxy Nexus using XDA

efrant said:
Is your bootloader locked or unlocked?
If it is unlocked, you can skip your step 2.
If it is locked, then it will wipe everything anyway, so might as well flash the other images just to be 100% sure you are stock.
Make sure that all the images are from the mysid ICL53F factory file.
Click to expand...
Click to collapse
reflashing the stock recovery fixed the issue. thank you much.
Sent from my Galaxy Nexus using XDA

ota update issue

Hi guys I'm trying to get my nexus updated to JB. I am on 4.0.4 rooted using the toolkit. I have flashed stock recovery back to the phone using toolkit. I'm getting the attached error. Any ideas anyone?
Thanks

step 1) STOP USING A TOOLKIT!
step 2) http://forum.xda-developers.com/showthread.php?t=1626895

corkie1 said:
Hi guys I'm trying to get my nexus updated to JB. I am on 4.0.4 rooted using the toolkit. I have flashed stock recovery back to the phone using toolkit. I'm getting the attached error. Any ideas anyone?
Thanks
Click to expand...
Click to collapse
Well first of all, I definitely don't recommend you using toolkit. Using it has higher chance of bricking your phone.
It seems like you might have to boot into the clockworkmod recovery and from there, flash the zip. It's faster than the way and also doesn't give you those kind of headache
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Hi guys when I say toolkit its the specific gnex toolkit. I thought this was a well received method for rooting - no?

Are you sure you flashed the right stock recovery for your phone?

Ya definitely flashed right stock recovery. It's very easy using the toolkit.

corkie1 said:
Ya definitely flashed right stock recovery. It's very easy using the toolkit.
Click to expand...
Click to collapse
so is fastboot
fastboot flash recovery nameofrecovery.img

I've used the toolkits and fastboot on 3 different gnex's and not had problems either way. If you fastboot incorrectly as well it's possible to brick your phone right?

wisniphi said:
I've used the toolkits and fastboot on 3 different gnex's and not had problems either way. If you fastboot incorrectly as well it's possible to brick your phone right?
Click to expand...
Click to collapse
well yeah if you fastboot the wrong recovery, but if you typo the command, it errors and wont flash it.

The OTA failed not because of your recovery but because of /system/usr/keylayout/generic.kl not being stock or missing.
You can either find that file and push it back and then run the OTA hoping that's the only file you modified.
Or flash the stock JB image following the link Zepius posted in the 2nd post.

I used this thread to help me update to JB when the OTA wasn't showing up for me (I was impatient).

wisniphi said:
[snip]
If you fastboot incorrectly as well it's possible to brick your phone right?
Click to expand...
Click to collapse
Nope. Odin yes. Fastboot no.
OP: And as El Daddy said you (or one of your root apps) prob changed something related to your keyboard, so you need to replace that file with the stock one.
Sent from my Galaxy Nexus using Tapatalk 2

I can't agree more! This is literally the third straight post I've read with an issue that started with 'I'm rooted using X toolkit...'
Sent from my Galaxy Nexus using xda app-developers app

El Daddy said:
The OTA failed not because of your recovery but because of /system/usr/keylayout/generic.kl not being stock or missing.
You can either find that file and push it back and then run the OTA hoping that's the only file you modified.
Or flash the stock JB image following the link Zepius posted in the 2nd post.
Click to expand...
Click to collapse
Hiya - thanks - I browsed to the location and found a generic.kl.bac file - renamed this rebooted and the OTA went through no problems

Returning to stock using a Mac.

Can someone please let me know how to do this. i have search everywhere and no one says anything. they only provide a link but it does not provide step by step nor links to do this. my Gnex is unlocked but not rooted. I would like to go back to stock so that i can update to JB. Thank you in advance.

colomob said:
Can someone please let me know how to do this. i have search everywhere and no one says anything. they only provide a link but it does not provide step by step nor links to do this. my Gnex is unlocked but not rooted. I would like to go back to stock so that i can update to JB. Thank you in advance.
Click to expand...
Click to collapse
Well if you're only unlocked, and not rooted, have custom recovery/ROM or anything, you are completely stock. Just unlocked bootloader... OTA has nothing to do with unlocking bootloader. Also root doesn't stop OTAs. Just FYI... Only flashing custom ROM, custom kernel or custom recovery or a change to a system partition stops the OTA.

kyokeun1234 said:
Well if you're only unlocked, and not rooted, have custom recovery/ROM or anything, you are completely stock. Just unlocked bootloader... OTA has nothing to do with unlocking bootloader. Also root doesn't stop OTAs. Just FYI... Only flashing custom ROM, custom kernel or custom recovery or a change to a system partition stops the OTA.
Click to expand...
Click to collapse
and thats where my problem comes. i cant find a stock rom. im on a custom rom.

colomob said:
and thats where my problem comes. i cant find a stock rom. im on a custom rom.
Click to expand...
Click to collapse
Ohhh ok... But you're not rooted? Strange...
Anyways, here is the link. Whenever efrant tells you to either "fastboot" or "adb", just put ./ in front of it. That's the command for Mac and Linus

kyokeun1234 said:
Ohhh ok... But you're not rooted? Strange...
Anyways, here is the link. Whenever efrant tells you to either "fastboot" or "adb", just put ./ in front of it. That's the command for Mac and Linus
Click to expand...
Click to collapse
i found that way but im an idiot i guess. i read it and re read it and i dont understand it.. :/
any way someone can simplify that and post it here?

colomob said:
i found that way but im an idiot i guess. i read it and re read it and i dont understand it.. :/
any way someone can simplify that and post it here?
Click to expand...
Click to collapse
what are the parts you dont understand?
that will guide you through flashing an official google factory image. you on gsm? yakju or takju, your choice. cdma? only vzw gnex is supported.
Sent from my i9250

bk201doesntexist said:
what are the parts you dont understand?
that will guide you through flashing an official google factory image. you on gsm? yakju or takju, your choice. cdma? only vzw gnex is supported.
Sent from my i9250
Click to expand...
Click to collapse
Im on sprint..

anyways i believe i have everything that the guide asks to have, including the ADB and fastboot for mac. i downloaded the update that he asks to get. i have boot.img, bootloader.img,radio-cdma.img, radio-lte.img, recovery.img and system.img....
or anyone have the stock Rom i can flash and ether flash the update or get it OTA???

colomob said:
anyways i believe i have everything that the guide asks to have, including the ADB and fastboot for mac. i downloaded the update that he asks to get. i have boot.img, bootloader.img,radio-cdma.img, radio-lte.img, recovery.img and system.img....
or anyone have the stock Rom i can flash and ether flash the update or get it OTA???
Click to expand...
Click to collapse
Yes you can use that guide for toroplus (i.e., Sprint) devices as well if you have the images. But since you don't have the userdata image (and therefore you skip that step), you may need to boot CWM and wipe /data and /cache, but only if you experience a bootloop.

So in recovery I have to flash each image? That's the part I don't get.
Sent from my Galaxy Nexus using xda app-developers app

colomob said:
So in recovery I have to flash each image? That's the part I don't get.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You cannot flash image files on any recoveries. You need to do those in fastboot mode using command prompt.

colomob said:
So in recovery I have to flash each image? That's the part I don't get.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's not at all what I said.
Follow the guide. But for the userdata image (which you don't have), boot into recovery and wipe data.

I finally did it!! If anyone needs help let me know. PM me.
Sent from my Nexus 7 using xda app-developers app

[HOW-TO] Guide to Debloated, S-OFF'd, Rooted HTC One with Wireless Tether Support

I'm writing this short little post to give an idea of a good starting point for the HTC One as it stands right now. There are a lot of threads and they get out-of-date quickly (just as this one will). I just picked-up my new HTC One on Tuesday of last week from a Verizon store. This just gives a fresh idea of what can be done to get started on it.
Obviously you're running these instructions at your own risk. I'm not responsible for you bricking or otherwise damaging your phone. Doing these things may (will) void your warranty and may prevent you from being able to return your phone. Run these things at your own risk.
AN IMPORTANT PUBLIC SERVICE MESSAGE: When you get your phone out-of-the-box, it's probably going to offer you an OTA update. I recommend that you do not accept an OTAs as this usually makes this process even harder than it has to be. Verizon hates having us enjoy our devices!
First, let me describe my goals here:
Unlock the bootloader and obtain S-OFF
Install a custom recovery (CWM)
Install a "cleaned-up" stock ROM (debloated but still a stock experience)
Get wireless tether working without jumping through tons of hoops.
I'll go through the list and just describe what I did:
Unlock the bootloader and obtain S-OFF
This was fairly straightforward. Rumrunner has an excellent package that does this very easily. I checked my phone's ROM version and saw that I was running 1.10.605.15. I grabbed the Rumrunner package from here for that level.
In looking over the requirements for Rumrunner, it wanted 32-bit Linux and I run 64-bit. The easiest way to solve this problem for me was to just boot to a Xubuntu 12.10 32-bit ISO that I had on my system. If you have it burned, just boot to it. If you don't (like me), use grub2 (if you have it) and boot the ISO directly. Either way, get yourself into a live environment.
Once the ISO was booted, I got it on the network and installed adb and fastboot from the Ubuntu repositories (after I did apt-get update, of course). Connect the phone via USB and enable USB debugging:
Go to Settings -> About -> Software Information -> More
Tap the Build number field 7 times
Back up to the Settings screen again and you'll now see Developer options
Enable USB Debugging under the developer options
Verify that you can see the device on your system using adb (this should result in a device being listed by serial number):
Code:
sudo adb devices
Follow these instructions for executing Rumrunner. It worked perfectly as described. Once complete, the phone was unlocked and S-OFF with a stock ROM.
Keep the live environment up as it will just make life easier to do the next steps.
Install a custom recovery (CWM)
I pretty much always use CWM if I can. I saw that there were no issues with doing that on this phone (like there are on other phones like the Rezound). I grabbed version 6.0.4.7 of CWM (non-touch) for the HTC One from here. If I recall correctly, the device is booted back into the stock ROM at this point. Make sure your device is still connected USB and has USB debugging enabled.
Reboot into the bootloader from the command prompt:
Code:
sudo adb reboot bootloader
Once the phone comes up, it should be at the Fastboot screen (it should actually show Fastboot USB). Verify that you can see your phone with fastboot (should get your device serial number again):
Code:
sudo fastboot devices
Now you can flash CWM recovery using this command from the directory where you stored the CWM file you downloaded (such as the one I provided a link to):
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.7-m7vzw.img
After the flash is successful, reboot back into the bootloader:
Code:
sudo fastboot reboot-bootloader
Now you can choose BOOTLOADER and then RECOVERY to get access to CWM. If you really want to, you can take a backup of the stock ROM at this point. I did not because I thought it was a waste of space. I just booted back into the stock ROM and disabled USB debugging so I could stick a real ROM on the system.
Install a "cleaned-up" stock ROM (debloated but still a stock experience)
I really wanted to give this HTC Sense 5.0 a run. I've used Sense before and it wasn't awful. This seemed less annoying than previous versions (plus, there are some nice camera features which are important to me). For that reason, I selected the stock 2.10.605.1 rooted, deodexed, debloated ROM from this thread. I also opted to do the firmware upgrade at the same time, so I grabbed the firmware for the 2.10.605.1 as well.
The instructions in this thread are easy to follow so just use those. Just a note though: Flash the firmware and ROM at the same time if you're going to do firmware at all. Instructions are in the second post on that thread.
Once the ROM was up, I did my typical setup of accounts and such. The last thing I needed was Wireless Tether support.
Get wireless tether working without jumping through tons of hoops.
I don't particularly care how I get wireless tethering (infrastructure mode) as long as it works on my phone reliably. I first tried the stock tethering as this sometimes works because the authors of "stock" ROMs sneak hacks into their ROMs. It did not work. I then tried messing around with the WiFi Tether TrevE Mod that I saw recommend a few times but this didn't pan out on the 2.10.605.1 ROM (I temporarily went to 1.10.605.15 and it worked; I went back to 2.10.605.1 when someone recommended the solution below):
http://forum.xda-developers.com/showthread.php?t=2576548
I flashed this package onto my system and, without a problem, built-in wireless tether started working. I've seen no problems.

Getting my one today. I guess I will give this a go tonight. Thanks. Anything else to look for? Thanks.
Sent from my HTC Rezound.

Rumrunner worked perfectly fine for me on Ubuntu 12.1 64 bit both times I ran it. I would try it first before downloading s 32 bit distro if 64 bit is already installed.
Sent from my HTC6500LVW using Tapatalk

I have 2.10.605.1 on this phone out of the box and dont see a Rumrunner for it. Does that mean I am just going to have to sit tight and wait?

onthehole said:
I have 2.10.605.1 on this phone out of the box and dont see a Rumrunner for it. Does that mean I am just going to have to sit tight and wait?
Click to expand...
Click to collapse
It is firewater now. Go to firewater-soff.com
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
It is firewater now. Go to firewater-soff.com
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Thanks.

No problem.
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
No problem.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
may not have time to do this today. Can I just keep pushing the ota off? I delayed it already but will it prompt me before trying to install?

onthehole said:
may not have time to do this today. Can I just keep pushing the ota off? I delayed it already but will it prompt me before trying to install?
Click to expand...
Click to collapse
Yeah just keep delaying it. If you take it you're screwed. 4.4.2 can't be unlocked and rooted at the moment.
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
Yeah just keep delaying it. If you take it you're screwed. 4.4.2 can't be unlocked and rooted at the moment.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
thanks. Looks like firewater uses some sort of temp root method? I will look into it. Firewater does s-off and root, correct?
And unlocks bootloader?

onthehole said:
thanks. Looks like firewater uses some sort of temp root method? I will look into it. Firewater does s-off and root, correct?
And unlocks bootloader?
Click to expand...
Click to collapse
It does unlock and s off. You will have to get a recovery and flash super user in recovery but that isn't until after you're unlocked and s off.
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
It does unlock and s off. You will have to get a recovery and flash super user in recovery but that isn't until after you're unlocked and s off.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So just flash TWRP or Clockwork, then go back in and flash super user. Thank you.
edit: I realized I am in the wrong forum asking these questions.

onthehole said:
So just flash TWRP or Clockwork, then go back in and flash super user. Thank you.
edit: I realized I am in the wrong forum asking these questions.
Click to expand...
Click to collapse
Yeah. Make sure you use cwm version 6.0.4.6 not .7 or twrp 2.6.3.4.
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
Yeah. Make sure you use cwm version 6.0.4.6 not .7 or twrp 2.6.3.4.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
will do. thanks.

onthehole said:
will do. thanks.
Click to expand...
Click to collapse
Hello:
I just gained S-OFF on stock 4.3 out of the box.
If I want to go to Stock/Rooted I am guessing I should take the OTA, then Clockwork or TWRP and SSU? Thanks.

onthehole said:
Hello:
I just gained S-OFF on stock 4.3 out of the box.
If I want to go to Stock/Rooted I am guessing I should take the OTA, then Clockwork or TWRP and SSU? Thanks.
Click to expand...
Click to collapse
Do not take the ota. Just flash the firmware in Santod's stock ROM thread and then flash the stock ROM from the ota.
Sent from my One using Tapatalk

disconnecktie said:
Do not take the ota. Just flash the firmware in Santod's stock ROM thread and then flash the stock ROM from the ota.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I was already S-Off and actually good to go. Took the OTA, flashed SuperSU after Clockwork and I am banging. Root/Soff, nailed it. Thank you for your help.

onthehole said:
I was already S-Off and actually good to go. Took the OTA, flashed SuperSU after Clockwork and I am banging. Root/Soff, nailed it. Thank you for your help.
Click to expand...
Click to collapse
The only reason I don't suggest taking ota is because sometimes the results can be less than desired.
Sent from my One using Tapatalk

disconnecktie said:
The only reason I don't suggest taking ota is because sometimes the results can be less than desired.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
understood. I will flash fresh if things aren't up to par.

Riddled by my (soft) bricked N5X ...

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).