I am in China and a VPN user. I turn on VPN from time to time for updates and other web browsing etc.
I received an OTA update yesterday and updated it. But today I received the exact same update. I have learned that many people using Nexus 6 had their phones stuck at reboot after two same updates. Is Nexus 6P the same case?
Many people suggest me to unlock OEM and BL so that I don't have to worry about "stuck at reboot" issues because of OTA. Is it necessary to unlock BL?
If I only leave the OEM unlocked, is it still possible to flash it when it bricks?
Sorry for poor English and thanks in advance!
I don't know about unlock OEM. I think it's common to unlock boot loader (this will ERASE your phone) and flash custom recovery. If you are not sure about this, read this very nice guide.
On a different note, I bought the 6p to use with Fi in the States and am currently in China. But when I bought a Liantong (unicom?) SIM, I can't make calls although internet and sms are fine. And the phone can't recognize the number.
PS. It's interesting to see 'sorry for the poor English.' I'm Chinese too! And happy to see you here
Not one but two Chinese friendlies? Nice
Just back up all your data first and unlock the bootloader. After that you might want to flash the latest factory image via fastboot to stop worrying about this month's OTA. And before every OTA you can take nandroid backups in a custom recovery just in case.
Or better - just use a ROM other than stock
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Related
Just for the purpose of tracking the rolling out process in the north America region, let's try collecting some date information when you receive the rollout. The process of this upgrade could become a helpful guideline for future upgrade events in the region! Models L04 and L14 might be involved. Let's also comment on your state, wireless service provider, if you are in the beta group and when you got the phone to see if anything is correlated. Please take a minute to fill out the form:https://docs.google.com/spreadsheets/d/1XULbGwxpO0s_RH9EzbvWjLP48MNCz7vkolbT0TiMf7s/edit?usp=sharing
Thank you!
Now, on the official Honor_USA social account, https://twitter.com/Honor_USA, N is coming on Feb 11th. Period.
Update: from Rox_honor, it's officially released on Feb 10th in the US. Some people have had this update already.
To force the update, you can check the method posted on Page 2, #16: https://forum.xda-developers.com/showpost.php?p=70992090&postcount=16.
Reserve for updating statistics, if possible. Again, the Google Spreadsheet to fill out is https://docs.google.com/spreadsheets/d/1XULbGwxpO0s_RH9EzbvWjLP48MNCz7vkolbT0TiMf7s/edit?usp=sharing
Feel free to add more columns if you think they are helpful.
So far it seems that only T-Mobile users are getting the update. Just tried to update my Mom's phone, we are on Cricket (AT&T) and there was no update for her. Tried putting it on airplane and restarting but still nothing. I'll probably try again tomorrow.
chris23445 said:
So far it seems that only T-Mobile users are getting the update. Just tried to update my Mom's phone, we are on Cricket (AT&T) and there was no update for her. Tried putting it on airplane and restarting but still nothing. I'll probably try again tomorrow.
Click to expand...
Click to collapse
There is one entry reporting received the update while on Straight Talk. We need to have more data in order to figure out the rollout sequence. GOOD LUCK!
i purchased the Unlocked Honor 8 from US (amazon). But I'm an indian user and I'm using it with an indian carrier . will i get the update as the other north american devices or do i have to wait longer
Did not get the update (FRD - L04)
But I forgot whether or not the L04 is international or US (i live in the US though)
yeah i havent gotten it either still says no updates available
I haven't received the update either on L04. I read on the other thread that it rolls out in small batches.
Edit: Here's the post: https://forum.xda-developers.com/showpost.php?p=70964112&postcount=392
Nothing on L04 AT&T yet. Purchased from NewEgg and first activated in December.
Got it 3 weeks ago. L04 from b&h.
Bought it unlocked at Frys a week ago and received the update yesterday. I just want to caution all rooted and unlocked users! I received the update yesterday and upgraded it like a fool. I cant get into twrp recovery and the stock recovery seems to be broken. I even installed a newer twrp thru fastboot but im still not able to go into recovery. Im looking through all the forums but no one seems to have this problems yet. Im still waiting on some help if anyone has a solution. So please be aware before updating. Hopefully Im the only one with this problem.
yomomsbigpimp said:
Bought it unlocked at Frys a week ago and received the update yesterday. I just want to caution all rooted and unlocked users! I received the update yesterday and upgraded it like a fool. I cant get into twrp recovery and the stock recovery seems to be broken. I even installed a newer twrp thru fastboot but im still not able to go into recovery. Im looking through all the forums but no one seems to have this problems yet. Im still waiting on some help if anyone has a solution. So please be aware before updating. Hopefully Im the only one with this problem.
Click to expand...
Click to collapse
Ahh, I was an idiot and had the same thing.
What happened is that I was rooted, and installed via Charles app, and it bugged out.
The reason for that is that TWRP can't install the stock ROM.
You need to get into fastboot, and reflash the stock recovery, and use it to dload the emui 4.1 file. Make sure you get the full package version.
After that it will be all wiped. You might run into a few errors but let the recovery do its thing.
You'll eventually be able to boot into the OS and then run the update normally.
I want to root my honor 8 on nougat, but I'm waiting for a patch from Huawei first because of all the bugs, just because of this.
Also I don't think rooting the honour 8 on nougat works that we'll yet, hopefully someone comes up with a method that doesn't suck so hard.
Hopefully they'll do it quickly.
Do you mind pointing me to the right direction to find those files? stock recovery and the 4.1.
Ive seen the rollback files... is that what you're talking about?
yomomsbigpimp said:
Do you mind pointing me to the right direction to find those files? stock recovery and the 4.1.
Ive seen the rollback files... is that what you're talking about?
Click to expand...
Click to collapse
I used the firmware finder tool for it. You can get it for Windows. It's somewhere around the forum, but you can probably Google it.
Once you get the full package you can extract the recovery.img from it.
Unlocked FRD-L04 bought from Amazon. Living in Argentina. Got update yesterday. Really happy with it.
Folks, if you are impatient, you can use the Firmware Finder to send the Firmware B360 (I am using the Jan 3 one) to your Updater for a full package update. More information can be found at https://forum.xda-developers.com/honor-8/how-to/news-huawei-firmware-finder-team-mt-t3550882
A few notes here from my personal experience:
1. Once you set up the proxy from the Finder's proxy app which should be downloaded after you enabled the "send firmware to updater" (check notification afterward), you then click on the latest firmware # and "send firmware to updater".
2. On the Setting/Updater, click the menu and use "Download full update package", which should direct you to a 2.27Gb package (not the 1.28Gb package, or you will not be able to login!) and click on the "Quick update" button. You may need to wait for a while to see this option. Up to now, you may not be able to download anything yet.
3. Go back to the wifi setting and turn on proxy setting to "None" again and reconnect with the wifi network. Now you should pause the Updater and then resume it. You should now be able to download the full package and install it.
4. After all the update process, it could be helpful to charge your phone without the screen turning on. This is told to be useful to optimize the battery performance immediately after the update. The phone might be slow in a couple of hours as optimizations are going on in the background. But everything will become normal afterward
Good luck!
bought L04 from newegg using it in Pakistan no update for me as of yet
This is all bulls*it. Same update we got in january, and by the way, it's buggy.
L04 here, bought from Amazon about a month ago. Running on T-Mobile US. Still no update yet.
Is there any way to change the white notification background? I prefer the old color scheme, Mich easier on the eyes at night.
Sent from my BTV-W09 using Tapatalk
Edit: Received update on US single SIM L04 on Straight Talk, ATT towers.
hi everybody, got this phone from my wife but I have been with Nexus for so long so I am a little bit behind the scene. Could anyone answer my questions? I don't see too many people here though.
I have unlocked the phone and installed TWRP, I think I have accidentally agreed to install the TWRP app suggested by TWRP but I don't have a system image backup, so it means I can never go back to OTA upgrade? now the boot loader say
*** software status: modified ***
seems HTC is not releasing factory image for the phone? I can't find it anywhere except this
https://forum.xda-developers.com/u-ultra/development/ruu-htc-ultra-unlocked-1-09-617-12-t3563948
I am not sure how many different hardware versions are there? and they are taking the same ROM? I am using a asia dual sim ver
at first the official TWRP doesn't boot, and I installed this one. but this TWRP ask me for a disk mount password, while I don't have any. I was busy and so I have put down the phone for 2 weeks. I installed the offical TWRP again yesterday and it worked. so...
https://forum.xda-developers.com/u-ultra/development/recovery-twrp-touch-recovery-t3558540
after installing super su the system boot up screen has a red text saying "This build is for development purposes only do not distribute outside of HTC without HTC's permission..." I think it come from supersu? is it expected?
The red text at boot is normal, I believe it's because of the unlocked boot loader.
Hey there,
There seems to be 2 hardware variants. U-1u (Dual Sim) and U-1h (single sim). not sure on interoperability of FW at present.
@mobilevil which sofware number are you running. Can be found in settings > about > sotware information, or from download mode. Asking as there can be found an official RUU for x.xx.617.x devices. If you're on US unlocked that'd be a possibility to return to full stock and receive OTA.
5m4r7ph0n36uru said:
@mobilevil which sofware number are you running. Can be found in settings > about > sotware information, or from download mode. Asking as there can be found an official RUU for x.xx.617.x devices. If you're on US unlocked that'd be a possibility to return to full stock and receive OTA.
Click to expand...
Click to collapse
Hi I am using 1.09.708.12. I did some OTA until it reported no update before rooting.
it is an unlocked dual sim ver and I bought it here in HK.
it is not very comfortable for me to have no official firmware image ready in hand.
sephstyler said:
Hey there,
There seems to be 2 hardware variants. U-1u (Dual Sim) and U-1h (single sim). not sure on interoperability of FW at present.
Click to expand...
Click to collapse
yes looking back I flashed an recovery without checking for hardware variants, I wasn't careful enough!
Hi guys,
I got a Pixel replacement for my Nexus 6P, love the phone but missed the larger screen so selling it and bought second hand Pixel XL with 2 year warranty from CeX.
I noticed when it booted it said something about not running the initial Firmware. I asked the shop as was sold as the "unlocked" version. They told me was ee but genuine firmware that unlocked the phone and will function no differently and receive all updates without delay.
Having set up the phone, it's still running 7.1 and not detecting anything newer. Plus security patches are 05/10/16. This seems like a problem.
Do I need to return it?
EDIT: just started WhatsApp which told me I have a custom ROM which child cause issues. I bought the pixel to have native android.
Many thanks,
Max
Just flash the latest firmware
Sent from my Le X526 using Tapatalk
Thanks for the reply. But will I have to do this for every update and also to get security patches?
Just realised I'm in the wing sub forum. Can I ask to have it move?
maxcovergold said:
Thanks for the reply. But will I have to do this for every update and also to get security patches?
Just realised I'm in the wing sub forum. Can I ask to have it move?
Click to expand...
Click to collapse
No, you shouldn't have to flash every update once you are on official images. Just flash the stock Google images and you should be good to go. https://developers.google.com/android/images
calripkenturner said:
No, you shouldn't have to flash every update once you are on official images. Just flash the stock Google images and you should be good to go. https://developers.google.com/android/images
Click to expand...
Click to collapse
I noticed in the FAQ about meeting through boot loader unlocked and not relocking it. Presumably it must have been unlocked to change the original Firmware, but I don't get that message "Your device software can't be checked for corruption. Please lock the bootloader".
Is this going to be a problem in fishing the firmware? Sorry, I bought the Pixel as I really have no idea about the things, want exciting this.
The sign is just shown that your bootloader is unlocked.
VERIZON UNLOCKED BOOTLOADER ONLY.
Yes you can unlock these things as long as they have never hit the network on Verizon )... EVER... (with a different CARRIER sim) I watched guy at Best Buy do it with a PIXEL and Pixel I guess the true issue is, you never know how or when they would be started especially on a refurb --- etc... Good Luck on that one...
First thread ever but the support scarce for VZW users (Specifically)and ROMs are scarce in generally. WE ARE SCARED TO DEATH to get the bootloader relocked... I've been flashing since the originally G1 and usually just keep my mouth shut stay humble and learn from every thread. I can't really find a lot of info on the VZW version and really the fear of locking the bootloader after trying so hard to get an nde64x ver on 7.1.0 to unlock was quite the endeavor in itself. I just wanted to pass along some info. Ask questions. If your an expert I'm sure this is pointless, but I just answered all of this for a friend that just switched to the Evil Red.
1. YOU CAN Flash the google updates (Not the ota but full system img using the flash all.bat)
DOWNLOAD THE FACTORY IMAGE NOT THE OTA (Google --- Factory IMG, Marlin)
- Download which ever from 7.1.0 to 8.1.0 unzip (I use 7zip but your windows programs can do the same
- Install your Fastboot/Adb and drop the EXTRACTED in your platform tools folder ... NOT the whole folder... but the items within the folder, into Platform tools (Should be 6 items including the flash all.bat) IT WILL NOT RELOCK YOUR BOOTLOADER BUT WILL WIPE YOUR DEVICE UNLESS YOU GO IN TO MOVE THE -W SCRIPT
2. 7.1.2 roms aren't working well with the A B Slot issues recovery... I was losing my mind trying to get things to flash and finally come to the conclusion... TWRP-3.1.1-0-fastboot-marling.img and .zip are the only recovery I can install to get roms to flash... If I Fastboot or flash the -1 img (twrp 3.1.1-1) or the 3.2.1-0-marlin.img I have to flash back to stock to get roms flasheable again.
- Working TWRP Nougat twrp-3.1.1-0
Flash Away At that point... If you get stuck like me and install 3.1.1-1 or the Other 3.2.1-0 I had to return to stock because of the A-B partition issues and get back to 3.1.1.0 to flash roms and Kernels.
3. Oreo 8.1.0 works with the flash-all bat (Google FACTORY image). The Oreo version will NOT relock your bootloader!!!
- TWRP works on 3.2.1-0.
- Magisk 14.5 and 14.6 work on Oreo...
- Super Su SR5 works with SU Hide 1.09
- Sound mods are eluding me on Oreo but Weta 9 Pixel is working with MANUAL MOVES--- Use at your own risk...
Right now I am on a VZW device running Carbon (LOS Based) with a Modded Google Cam (GCMOD cam )Viper4Andriod working, Franco Kernel --- ((A Lot harder than I thought on LOS to get some of the normal things working))
Ask questions if you want I'll answer what I can. Or I'll ask question of someone else to try to get an answer... Happy flashing...
So if I have a VZW pixl XL on 8.0.0 that HAS been used on vzw then Im out of luck is what Im gathering?
LeoTheRomRasta said:
So if I have a VZW pixl XL on 8.0.0 that HAS been used on vzw then Im out of luck is what Im gathering?
Click to expand...
Click to collapse
Most likely, if you didn't unlock the bootloader with depixel8, back on 7.1
Sunshine team has no plans to work on unlocking newer versions, although, jcase said if someone could get temp root, he would provide an unlock...
So we're screwed. ?
Mikkey81 said:
VERIZON UNLOCKED BOOTLOADER ONLY.
Yes you can unlock these things as long as they have never hit the network on Verizon )... EVER... (with a different CARRIER sim) I watched guy at Best Buy do it with a PIXEL and Pixel I guess the true issue is, you never know how or when they would be started especially on a refurb --- etc... Good Luck on
1. YOU CAN Flash the google updates (Not the ota but full system img using the flash all.bat)
DOWNLOAD THE FACTORY IMAGE NOT THE OTA (Google --- Factory IMG, Marlin)
- Download which ever from 7.1.0 to 8.1.0 unzip (I use 7zip but your windows programs can do the same
2. 7.1.2 roms aren't working well with the A B Slot issues recovery... I was losing my mind trying to get things to flash and finally come to the conclusion...
3. Oreo 8.1.0 works with the flash-all bat (Google FACTORY image). The Oreo version will NOT relock your bootloader!!!
Click to expand...
Click to collapse
So can you not flash.all.bat 7.1 image and unlock bootloader if it's vzw pixel XL?
Bryanx86 said:
So can you not flash.all.bat 7.1 image and unlock bootloader if it's vzw pixel XL?
Click to expand...
Click to collapse
No you can't, because you can't flash until after you are unlocked.
I returned mine to Google and sweet talked my way into the one I have now. Still Verizon, but it was rolled back to 7.1.0.... Well and blue (my original was black). I'm not sure I could've kept the phone without actually being able to flash roms/kernels/themes. No matter who you are or what you do, the developers around android building are just remarkable at finding and fixing those little stutters and issues that drive us all nuts as well as adding those little goodies that make them fun and unique.
This was actually an argument I was having with the gentleman at Best Buy telling me the phones are all the same with the Pixel 2 a month or so ago. After a bit of discussion he also said I could immediately unlock these devices even on Verizon. I called him out and he proved it, but HAD to use an AT&T sim as the start up. Once VZW is booted past the 7.1.0 version, that it is unlockable... its over... unless someone else can find another unlocking method to downgrade without OEM unlock or a bootloader unlock method I don't know what to say. Personally I would've rolled back to the 6p or gone to the 2 and had the guy at Best Buy help me out with a sim.
This thread is so noob... Makes me cringe.
stebomurkn420 said:
This thread is so noob... Makes me cringe.
Click to expand...
Click to collapse
Come on man... Gotta help the cause... Everyone wants options and themes... Thats why we dont have IPhones.
Verizon users dont stand a chance at catching up or learning assuming they ever had a Pixel xl on NDE63P If they want to unlock, they need to start backing up to the 6P.... which is actually still a comparable device to newer phones at a couple years old.... and then they cant even go to the store to set it up... LOL. Sooooooo many posts from Verizon Users asking about whether they can update stock or via Google images and noone answers, well, mostly because their in the wrong thread.
And yes I realize I answered the last question asked, in the original post. I still have a little patience in my old age...
NO you can not flash down to 7.1.0 because you cant run the Google img through Fastboot, without being unlocked and there is NOWAY currently to unlock, past the original build version... I believe the last unlockable was NDE63X (dont quote me on that) Sorry guys. You CAN HOWEVER flashall.bat if you are ALREADY unlocked and you will stay bootloader unlocked.
stebomurkn420 said:
This thread is so noob... Makes me cringe.
Click to expand...
Click to collapse
Come on man... Gotta help the cause... Everyone wants options and themes... Thats why we dont have IPhones.
Verizon users dont stand a chance at catching up or learning assuming they ever had a Pixel xl on NDE63P If they want to unlock, they need to start backing up to the 6P.... which is actually still a comparable device to newer phones at a couple years old.... and then they cant even go to the store to set it up... LOL. Sooooooo many posts from Verizon Users asking about whether they can update stock or via Google images and noone answers, well, mostly because their in the wrong thread.
And yes I realize I answered the last question asked,...well most in the original post. I still have a little patience in my old age...
NO you can not flash down to 7.1.0 because you cant run the Google img through Fastboot, without being unlocked and there is NOWAY currently to unlock, past the original build version... I believe the last unlockable was NDE63X (dont quote me on that) Sorry guys. You CAN HOWEVER flashall.bat if you are ALREADY unlocked and you will stay bootloader unlocked.
I played with my P8Lite and I managed to f#ck the rom, so I decided that anyway is time to upgrade (I'm planning to go on AOSPA from here https://forum.xda-developers.com/p8lite/development/rom-t3649258 ).
Currently installed: Android 5.0.1 ALE-L211C432B190
What I did:
- downloaded and installed via dload method (b895_update.zip and B896_update.zip)
- now, in fastboot it says Phone Locked. Before, when it was running on previous rom, it was unlocked (i unlocked it).
Problem is that I can't seem to find the website where I can request a new code... the links I found here on xda seem to lead to a broken page.
This is rather urgent, so I'd appreciate any help.
Thanks a lot.
EDIT
For whoever has similar issue:
I contacted HUAWEI Support from here: https://consumer.huawei.com/en/contact-us/
To be safe, I wrote an email and used their Phone Support service. Service was surprisingly great and I got my unlocking number in less than 3 hours since I made my request.
Could you write what did you say to them?
And email address
Thanks
Urkel99 said:
Could you write what did you say to them?
And email address
Thanks
Click to expand...
Click to collapse
Forget that, that was in April and now they will not provide the unlock code anymore.
To unlock the ALE-L21 you will need to downgrade to android 5.0.0 and then try to root it in order to get the unlock code.
how to root after downgrade