The official version of Android L B322 is now available for public download.
http://consumer.huawei.com/us/support/downloads/index.htm
Instructions for upgrade can be found here - http://consumer.huawei.com/us/support/manuals/index.htm
Feedback can be left on Huawei Device USA forums - https://community.gethuawei.com/support/f/2
wimbet said:
The official version of Android L B322 is now available for public download.
http://consumer.huawei.com/us/support/downloads/index.htm
Instructions for upgrade can be found here - http://consumer.huawei.com/us/support/manuals/index.htm
Feedback can be left on Huawei Device USA forums - https://community.gethuawei.com/support/f/2
Click to expand...
Click to collapse
Cool, and congrates Wimbet (Taylor ?) so now we finally have a public release again!! flashing it now...
Edit:
Boot to stock recovery doesn't flashing, need to: (copied from above instructions)
1) Copy the dload folder to the root directory of the MICRO SD card.
2) Make sure your handset is power off... then Press the VOLUME UP and VOLUME DOWN keys and POWER key to power on the phone(picture1) , when the HUAWEI logo is showed , release the POWER key and keep pressing the VOLUME UP and VOLUME DOWN keys(picture 2) until your phone is entered the Software Upgrade Mode.
Have they released the kernal source too ?
@xordos, would you mind testing whether the LCD dpi can be lowered in this new build?
medwatt said:
Have they released the kernal source too ?
@xordos, would you mind testing whether the LCD dpi can be lowered in this new build?
Click to expand...
Click to collapse
lol, this is the first thing I am going to test...
Edit,
Tested, lower dpi has same problem as B320/B321, tried set dpi to 284, cannot see soft button and status bar, and phone is not usable except the home screen.
wimbet said:
The official version of Android L B322 is now available for public download.
http://consumer.huawei.com/us/support/downloads/index.htm
Instructions for upgrade can be found here - http://consumer.huawei.com/us/support/manuals/index.htm
Feedback can be left on Huawei Device USA forums - https://community.gethuawei.com/support/f/2
Click to expand...
Click to collapse
Is this going out to all phones. Or is this just forpeople that want to download and install?
xordos said:
lol, this is the first thing I am going to test...
Click to expand...
Click to collapse
Thanks. I have resolutely stayed away from Lollipop simply because of this. Even though I have a ominous feeling that it won't work, it's worth to give it a try !
medwatt said:
Thanks. I have resolutely stayed away from Lollipop simply because of this. Even though I have a ominous feeling that it won't work, it's worth to give it a try !
Click to expand...
Click to collapse
Not kernel release yet. I am checking hourly.
---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------
medwatt said:
Thanks. I have resolutely stayed away from Lollipop simply because of this. Even though I have a ominous feeling that it won't work, it's worth to give it a try !
Click to expand...
Click to collapse
https://community.gethuawei.com/developers/w/huawei-developers/40.huawei-mate2-mt2-l03
If you wish to look..lol
Moody66 said:
Not kernel release yet. I am checking hourly.
Click to expand...
Click to collapse
Given the way Huawei works, you might need to check a lot .
I have the update showing up in my phone. If I unroot and run the updater, will that be enough to make it work without wiping my phone? I screwed up the last update by not unrooting first, and could only get it done by adding the update to the dload folder and wiping/restoring my stuff. I don't want that again.
neocortex08 said:
I have the update showing up in my phone. If I unroot and run the updater, will that be enough to make it work without wiping my phone? I screwed up the last update by not unrooting first, and could only get it done by adding the update to the dload folder and wiping/restoring my stuff. I don't want that again.
Click to expand...
Click to collapse
As long as you haven't messed with system stuff. Yes. Unroot and stock recovery. If you have changed something system wise.... Unknown.
medwatt said:
Given the way Huawei works, you might need to check a lot .
Click to expand...
Click to collapse
Huawei Mate2 kernel source code
https://community.gethuawei.com/developers/w/huawei-developers/40.huawei-mate2-mt2-l03
---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------
I'm still going to stick with PAC MAN ROM at the moment. That ROM is killing it on this phone.
http://forum.xda-developers.com/asc...mr1-beta-2-t3186673/post62667019#post62667019
Moody66 said:
As long as you haven't messed with system stuff. Yes. Unroot and stock recovery. If you have changed something system wise.... Unknown.
Click to expand...
Click to collapse
- Clicked "Unroot" in SuperSU.
- Extracted the Recovery.img from the B321 update and flashed it (TWRP is no longer there when I boot into recovery)
- Clicked download and update in the updater software. Clicked "Install" and accepted the prompt.
- Phone boots into the updater and it fails at 26%.
Any ideas why it fails? I am definitely on B321, so I thought I flashed the right recovery and unrooted. I don't think I changed any system files.
neocortex08 said:
- Clicked "Unroot" in SuperSU.
- Extracted the Recovery.img from the B321 update and flashed it (TWRP is no longer there when I boot into recovery)
- Clicked download and update in the updater software. Clicked "Install" and accepted the prompt.
- Phone boots into the updater and it fails at 26%.
Any ideas why it fails? I am definitely on B321, so I thought I flashed the right recovery and unrooted. I don't think I changed any system files.
Click to expand...
Click to collapse
It should tell you why it failed. Immediately after the failure.
Here. that is with exactly one hour screen on time and uploading a 1 gig file the entire time. @medwatt
medwatt said:
Have they released the kernal source too ?
@xordos, would you mind testing whether the LCD dpi can be lowered in this new build?
Click to expand...
Click to collapse
medwatt said:
Thanks. I have resolutely stayed away from Lollipop simply because of this. Even though I have a ominous feeling that it won't work, it's worth to give it a try !
Click to expand...
Click to collapse
Screen time.
Moody66 said:
It should tell you why it failed. Immediately after the failure.
Click to expand...
Click to collapse
Big exclamation point, "Software install failed" underneath, "press powerkey to confirm".
Pressed power button to restart.
Phone reboots to what looks like an updater screen for less than half a second then reboots again.
Boots into the phone fine but still I'm on B321.
Notification screen says ""System update failed last time".
No other notification or information other than that the update is now gone but available to be downloaded again.
neocortex08 said:
Big exclamation point, "Software install failed" underneath, "press powerkey to confirm".
Pressed power button to restart.
Phone reboots to what looks like an updater screen for less than half a second then reboots again.
Boots into the phone fine but still on B321.
Notification screen says ""System update failed last time".
No other notification or information other than that the update is now gone but available to be downloaded again.
Click to expand...
Click to collapse
Ugh. Sounds like you need to do fill install of the update. Hard to tell without it being more specific.
Full update.
https://drive.google.com/file/d/0B97V_YadJs2baHJSTGJDbkI0clE/view?usp=docslist_api. As usual.. Extract to external sd card on dload folder and three button startup.
In case anyone like me who can't bear the phone with gargantuan text, icon etc and would like to change the lcd dpi, don't bother then because the screen will be unusable if you change the lcd value. Just a heads up ! Since I can't stand the phone this way, I'm heading of to try PAC rom ! So long, Huawei and your sh*tty but nice looking EMUI.
@medwatt you will love the PAC rom and updates bi weekly right now. Next build will include new camera app and call record.
superbass311 said:
@medwatt you will love the PAC rom and updates bi weekly right now. Next build will include new camera app and call record.
Click to expand...
Click to collapse
Let's hope so. Everything seems so large that someone looking into your phone might think you're blind ! Does the PAC ROM have the CM theme engine ?
Related
JUST to let everyone know, i've recieved notification for the update, i've got 3 choices reject, defer, and ok. so which should i choose.?????
???
lucky duck
if it were me, i would accept and try the exploit. but its not a guarantee that it would work
EDIT:
I just got the OTA, i am downloading now... i dont mind being a guinea pig
Aldo101t said:
JUST to let everyone know, i've recieved notification for the update, i've got 3 choices reject, defer, and ok. so which should i choose.?????
???
Click to expand...
Click to collapse
I just got the update. I think I'm going to do it and see if it works.
icedragon59 said:
i just got the update. I think i'm going to do it and see if it works.
Click to expand...
Click to collapse
good luck to all
For future reference, you can download it and then choose not to install it. It can be downloaded over Wi-Fi, or uses background mobile data but doesn't display the icon.
EDIT:
It took 11 minutes to install, and now I'm Android 4.0.4 and Sense 4.1. I can't find how to change the Recent Apps button to a Menu button. I'm slightly upset about that.
Now on to attempting root!
IceDragon59 said:
For future reference, you can download it and then choose not to install it. It can be downloaded over Wi-Fi, or uses background mobile data but doesn't display the icon.
Click to expand...
Click to collapse
Is that the "Defer" option, or "Yes", then choose to not install?
Once it downloads I would expect a constant nag to install until you do.
junkmail9 said:
Is that the "Defer" option, or "Yes", then choose to not install?
Once it downloads I would expect a constant nag to install until you do.
Click to expand...
Click to collapse
First "OK" to download update, then "Defer" to not install it once it has downloaded. And yeah, you'll probably get constant nags.
IceDragon59 said:
For future reference, you can download it and then choose not to install it. It can be downloaded over Wi-Fi, or uses background mobile data but doesn't display the icon.
EDIT:
It took 11 minutes to install, and now I'm Android 4.0.4 and Sense 4.1. I can't find how to change the Recent Apps button to a Menu button. I'm slightly upset about that.
Now on to attempting root!
Click to expand...
Click to collapse
I believe the Menu button change is the 3-button Mod that you can install once rooted.
Good luck on the root attempt! Please let us know how it goes.
so can we not use this exploit unless we have downloaded the newest update?
IceDragon59 said:
For future reference, you can download it and then choose not to install it. It can be downloaded over Wi-Fi, or uses background mobile data but doesn't display the icon.
EDIT:
It took 11 minutes to install, and now I'm Android 4.0.4 and Sense 4.1. I can't find how to change the Recent Apps button to a Menu button. I'm slightly upset about that.
Now on to attempting root!
Click to expand...
Click to collapse
Unlike the sense 4.1 updates for one series and EVO LTE, ours does not bring the key remappingoption to settings...those updates changed display & gestures to display, gestures, & buttons...and the option is in there for those users
Got the update but unlike others, mine just downloaded and installed without asking me permission! I was in my car and needed to make a call too! Argh. But at least it seems to have installed OK.
Any idea if this update is available for download on VZW's website somewhere? I am having trouble with the OTA update.
I got the update too...no notice, it just d/l'd and installed without options. What's the new icon in the status bar (left of the wifi)?
Caught mine just before it installed the update and yanked my battery. Every time I boot it back up it tries to install the update. Any ideas on how to get it to clear the update? Don't want to update til we know more about what this might mean for the possibility of S-OFF or root with the current h-boot.
it downloaded mine and i defered it, but where does it download to, i can't find it.
Aldo101t said:
it downloaded mine and i defered it, but where does it download to, i can't find it.
Click to expand...
Click to collapse
Probably /cache or /cache/fota
You can't get there without root.
junkmail9 said:
Probably /cache or /cache/fota
You can't get there without root.
Click to expand...
Click to collapse
that figures
junkmail9 said:
Probably /cache or /cache/fota
You can't get there without root.
Click to expand...
Click to collapse
I'm rooted and it says error flashing zip. *confused*
SOB it keeps trying to install even after i defered it, WTF
I TRIED DEFERING AGAIN i got unfortunatly htcdm has stopped????????????
Its mandatory right
I just received a Android update in my notification menu. I am rooted and running a custom recovery (twrp). I know I cannot accept the update but I can't swipe it away. Anyone know how I can get the update removed from my notification menu?
Have you tried long pressing on the notification and disabling notifications?
I froze system update in ti backup I didn't have a pending update but I would try that
Is that file under. Com in tb?
jreink01 said:
Is that file under. Com in tb?
Click to expand...
Click to collapse
Here you go
kennwoodkenn said:
Here you go
Click to expand...
Click to collapse
Thanks for the thumbnail. I did find it in TB and froze it but I'm still getting the update notification in my notification pull down.
Did you restart the phone after
that may work
Don't know if this will work or not, but on the Galaxy S3 the way to stop getting nagged about an OTA was to edit build.prop and replace all references to the old ROM with the new one. So you could try making a backup of build.prop, then edit all references to ZV4 and change them to ZV6. Save the file, make sure permissions are set to rw-, r--, r-- (0644), and reboot.
I would strongly suggest making a nandroid backup first.
Here's how I have been doing it:
1. Download Autorun Manager
2. In settings under advanced enable view services
3. Go to Google Services Framework and disable update...see below.
At your own risk if you decide to try it, of course.
Sent from my LGLS990 using XDA Free mobile app
This is the recommended way. http://forum.xda-developers.com/showthread.php?p=57182591
If the update has already downloaded. Disabling the OTA still wont get rid the the notification. Easy way to get rid of it is long press it and go to app info. This will take you to Google Play Services. Simply uncheck show notifications and the system update in the pull down notifications will go away.
Just a temporary fix to get it out of the way. I reccommend just downloading a ZV6 rooted rom.
engine95 said:
This is the recommended way. http://forum.xda-developers.com/showthread.php?p=57182591
Click to expand...
Click to collapse
guys I mistakenly installed this update and now my phone is stuck in twrp where can I go to delete it or am I s.o.l please help
You will need to use LG Flash tool if you are stuck in TWRP.
LG Flash Tool How to Thread
A youtube video that might help
https://www.youtube.com/watch?v=1WgXuxDbmbc
im0rtalz said:
You will need to use LG Flash tool if you are stuck in TWRP.
LG Flash Tool How to Thread
A youtube video that might help
https://www.youtube.com/watch?v=1WgXuxDbmbc
Click to expand...
Click to collapse
thanks for this I'll have to wait until I'm near a computer or back home right now I'm vacationing in Florida
Try this first before doing the LG Flash
[Fix] Stuck in Custom Recovery
Thanks to acparker posts
randyrampage609 said:
thanks for this I'll have to wait until I'm near a computer or back home right now I'm vacationing in Florida
Click to expand...
Click to collapse
Downside: No Phone.
Upside: Nice weather!
From folks here in Chicago - no sympathy! :silly:
Good luck with the phone!
FractalSphere said:
Downside: No Phone.
Upside: Nice weather!
From folks here in Chicago - no sympathy! :silly:
Good luck with the phone!
Click to expand...
Click to collapse
Alls good now used a two command terminal combo from another thread that I'm trying to find
Sent from my LGLS990 using Tapatalk
---------- Post added at 11:15 PM ---------- Previous post was at 11:12 PM ----------
randyrampage609 said:
Alls good now used a two command terminal combo from another thread that I'm trying to find
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2916085
Without having to use a computer and lg flash tool
Sent from my LGLS990 using Tapatalk
Lucky you. Good find. Glad you got it sorted. Now you can relax.
I have a question that I wanted to ask before I go any further. I bought a G3 last week, rooted it and installed twrp recovery, and have done multiple backups.. Had a hardware defect so I had to exchange my phone for another new one. I received a system update just now so I was going to accept the OTA update since its not rooted, completely stock. My questions are will I be able to root and instally twrp after this update and once I install all my apps, and if rooting and installing twrp is successful, can I restore my backup that I did on my other phone, even though its a different phone? Its from the same carrier and same model phone. Thanks for your feedback.
jreink01 said:
I have a question that I wanted to ask before I go any further. I bought a G3 last week, rooted it and installed twrp recovery, and have done multiple backups.. Had a hardware defect so I had to exchange my phone for another new one. I received a system update just now so I was going to accept the OTA update since its not rooted, completely stock. My questions are will I be able to root and instally twrp after this update and once I install all my apps, and if rooting and installing twrp is successful, can I restore my backup that I did on my other phone, even though its a different phone? Its from the same carrier and same model phone. Thanks for your feedback.
Click to expand...
Click to collapse
Don't take OTA. Root it and TWRP it. Then flash STOCK ROM ZV6 Deodexed or Odexed, then you'll be up to date and keep root with TWRP.
I just got the 5.1 OTA. It feels a little faster so far. Although, my 5ghz WiFi router doesn't work right anymore. It will only connect at 2.4 GHz.
fzurita said:
I just got the 5.1 OTA. It feels a little faster so far. Although, my 5ghz WiFi router doesn't work right anymore. It will only connect at 2.4 GHz.
Click to expand...
Click to collapse
I think it is a bug From Google, the same was with 4.4.3, WLAN bugs and more, i think in next update it will be fixed
the-cortana-project said:
I think it is a bug From Google, the same was with 4.4.3, WLAN bugs and more, i think in next update it will be fixed
Click to expand...
Click to collapse
This has to be a new bug. It used to work fine in 4.4.4 and 5.0.
fzurita said:
This has to be a new bug. It used to work fine in 4.4.4 and 5.0.
Click to expand...
Click to collapse
Is there any other issues?
theinspector said:
Is there any other issues?
Click to expand...
Click to collapse
Not that I have seen so far. The camera seems about the same as before. The Wi-Fi bug is kind of annoying though since it limits how fast I can transfer files around.
if only we could have a port for non GPe Z Ultra :victory:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
MrSewerPickle said:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
Click to expand...
Click to collapse
you tried to flash OTA with unlocked bootloader? ...if so ...lol :silly:
@scrubber @blueether @egzthunder1
Just received the 5.1 update as well...
Looks like several bugs have been addressed... Seems quicker/less laggy.
Nice that they fixed the charging info on the lock screen that always said the wrong thing when NOT charging...that always bugged the hell out of me for some reason.
Will check back tonight after a day of use.
---------- Post added at 09:27 AM ---------- Previous post was at 09:24 AM ----------
MrSewerPickle said:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
Click to expand...
Click to collapse
SÜPERUSER said:
you tried to flash OTA with unlocked bootloader? ...if so ...lol :silly:
Click to expand...
Click to collapse
Oops! ?
I know, shame on me. I should never attempt to install an update that shouldn't have anything whatsoever to do with my boot loader being locked or unlocked.
Actually, I should probably start paying Google to collect my personal data and ask them each time I install apps as well.
Care to explain exactly in detail why a OTA would failed on a unlocked boot loader? And why it would affect a factory boot loader at that? And why the 5.0 update didn't give a damn (as it should) about if the boot loader was locked or not?
MrSewerPickle said:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
Click to expand...
Click to collapse
Experienced the same issue here.
Didn't work on my GPE either. Had to reboot twice before getting the phone to work. Went into settings to manually look for an update and now it says my phone is up to date even though it is still 5.0.
fosselman said:
Didn't work on my GPE either. Had to reboot twice before getting the phone to work. Went into settings to manually look for an update and now it says my phone is up to date even though it is still 5.0.
Click to expand...
Click to collapse
Same here. Went to install the update and it failed. Rebooted and now system update is showing that my phone is up to date. Guess I'll have to sideload the ota once someone publishes the link.
Mugenmundo said:
Experienced the same issue here.
Click to expand...
Click to collapse
draiko913 said:
Same here. Went to install the update and it failed. Rebooted and now system update is showing that my phone is up to date. Guess I'll have to sideload the ota once someone publishes the link.
Click to expand...
Click to collapse
I just got another notification saying it downloaded it again and is ready to install. Gonna wait til I get off work to install it.
Is anyone able to grab the OTA link and post it?
If someone is running the 5.1 GPE on their ZU-gpe, can you share the build.prop from it please?
I received my update today too. So far so good.
You can do the :
- App Settings -> Clear Data (on Google Framework services)
- Dial *#*#2432546#*#*
- Settings - > About -> System Update
It may even prompt you to download again before you get to the System Update screen.
Saatvik Shukla said:
If someone is running the 5.1 GPE on their ZU-gpe, can you share the build.prop from it please?
Click to expand...
Click to collapse
Here you go
Installing now...
having a problem reinstalling TWRP. I followed all the commands and here is a copy of what Happens when I flash
C:\Users\Robert\Desktop\files\TWRP_for_mate2\TWRP_for_mate2>fastboot flash recovery twrp.img
target reported max download size of 804257792 bytes
sending 'recovery' (14382 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 0.797s
but when I try to boot into it it starts up the stock recovery. Any suggestions on how to install TWRP and make it stick or how to gain root because I mainly use TWRP for root.
I also get this screen sometimes when trying to boot into boot loader. The phone doesn't seem to vibrate like it does when it boots normally or loads recovery and boot loader.
http://imgur.com/IQlBmP1
The usb is connected but I haven't tried to send anything to the phone or told anything other than to reboot system when it boots into stock recovery. If I leave it , it just sits there doing nothing so I rebooted and it boots just fine. Should I try to reflash stock recovery and then flash TWRP?
Found a way to at least let the phone get using TWRP without apparently being able to boot into it for some reason. Don't know if you can backup and restore backups using this method but at least its a temporary workaround. I found it at this site https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/. below is the guide copied from the site.
Prerequisites
•An unlocked bootloader – It is just a command away on Nexus devices. Google will give you very useful links depending on your device type.
•ADB with Fastboot – Check out this link: http://www.jailbreakeye.com/android/install-adb-fastboot
•A custom recovery image – TWRP or CWM (check the Download recovery or Download touch recovery columns)
Guide
1.Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
2.Launch terminal (or command prompt on Windows).
3.Navigate to the directory where you have placed the ADB, Fastboot and .img file together.
4.Shut down your phone and reboot into boot loader. For nexus devices, simply hold volume down + power to start up the phone.
5.Connect your phone to your computer.
6.On terminal (or command prompt) window, write fastboot boot <img file name>, e.g. fastboot boot twrp.img.
7.Your phone will restart and will boot into the recovery mode.
That’s it. As simple as it can get!
Hopefully this will help out those who are having trouble getting into TWRP after updating to B321.
what new on the b321 updated
dizwikedcbr said:
what new on the b321 updated
Click to expand...
Click to collapse
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Which launcher?
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Which launcher are you using?
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
same happened with me. did the b321 ota and got stuck on boot screen. had to go back to b309 and now cant get back to b320.
How long did you let it run. It can take a good while on first boot...
I let it sit there so long i had forgotten about it all together. so at least 10-15 min on huawei splash screen. not the emul loading screen. i dont think a 30-40mb upgrade should take longer that it takes to load a complete image
---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------
And when i search for updates now I get nothing... stuck on b309 i guess.
Moody66 said:
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
Click to expand...
Click to collapse
My phone is stock. Nothing added and no root. The issues are apparent and have been reported by other users, so the issues I have posted are NOT user error. A number of them have been confirmed as being fixed in the next release. 321 won't be the next release to the general public.
Confirmed fix in next release? Who is running the "next release"?
The b321 ota might be a good thing, but it's new enough that I am wary. I just upgraded to b320 less than a week ago and still haven't gotten everything situated on the phone. I've had some issues with Nova Prime launcher on power up. I have one question, er maybe two. What improvements if any make this new update a good choice and will I once again have to reload everything back onto my phone?
Moody66 said:
How long did you let it run. It can take a good while on first boot...
Click to expand...
Click to collapse
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
gale2000 said:
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
Click to expand...
Click to collapse
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Davinci50 said:
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Click to expand...
Click to collapse
Yes, I was rooted. Thanks for your help.
Harris.S.Newman said:
Which launcher are you using?
Click to expand...
Click to collapse
I am using Nova but Apex also stuck after reboot.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
Sorry for your headaches. I have had no issues but I am using a clean install with no root or other magical add-ons.
TheIgster said:
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Click to expand...
Click to collapse
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Moody66 said:
Confirmed fix in next release? Who is running the "next release"?
Click to expand...
Click to collapse
Confirmed on the Huawei website I've been posting on as well.
kimtyson said:
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Click to expand...
Click to collapse
Notifications were working fine on JB. There are issues since the update that need to be addressed. EMUI had it working just fine prior to the update to L.
There are no LED notifications for some notifications at times and I have yet to get a notification via the LED for Facebook. With and without a third party app.
The APN issues are documented and reported by other users. It is being fixed in the next release.
My install, yes, was not clean, but only an upgrade from 309. I have never had root. Yes, of course, you and Moody are experts and the rest of us are idiots. You both sure like to insinuate that in your posts. It's a little tiresome, but if it makes you feel better, I guess feel free.
Just got an update on my watch and, as always, pulled the update.zip for you guys!
If you're having troubles installing this ZIP please refer to this post here: http://forum.xda-developers.com/showpost.php?p=67403296&postcount=19
----------
Quick Install "Guide" if it's still failing for you:
1) Install TWRP from THIS THREAD HERE
2) Reboot into fastboot mode by turning the watch off and on again and while the black screen shows up constantly swipe from the left upper corner to the lower right corner.
3) Flash the TWRP provided above and reboot into recovery, then push the unpacked TWRP backup into "/sdcard/TWRP/BACKUPS/xxxxxxxxxxx/" (to get the last folder simply make a backup of only your boot partition first, it's the fastest)
4) Restore the backup provided IN THIS POST HERE onto your watch via the in 1 flashed TWRP
1) MUCH EASIER: Flash these instead the TWRP way, far far easier!
2) Let the OTA update install automatically
----------
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
>> OneDrive <<
EpicLPer said:
Just got an update on my watch and, as always, pulled the update.zip for you guys!
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
Click to expand...
Click to collapse
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
Code:
Unable to statfs '/system/.'.
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
kokesh said:
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
Click to expand...
Click to collapse
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Xmaster24 said:
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Click to expand...
Click to collapse
Thank you. Your recovery mounts /system, but I am still getting the same error.
kokesh said:
Thank you. Your recovery mounts /system, but I am still getting the same error.
Click to expand...
Click to collapse
yeah it can't write to it, you have to use the stock recovery for that. You are able to write to it but you must first format the partition as writable and then flash your system image/ backup. I'm getting the usual "old keys" error of TWRP not error you mentioned, just means The TWRP is too old base
---------- Post added at 11:13 AM ---------- Previous post was at 11:02 AM ----------
Those anyone have a link to the 6.0.1 stock recovery?
Those anyone have a link to the 6.0.1 stock recovery?
Click to expand...
Click to collapse
Isn't it possible to get it from the 6.0.1 OTA?
kokesh said:
Isn't it possible to get it from the 6.0.1 OTA?
Click to expand...
Click to collapse
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Xmaster24 said:
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Click to expand...
Click to collapse
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Xmaster24 said:
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Click to expand...
Click to collapse
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
EpicLPer said:
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
Click to expand...
Click to collapse
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that. I don't think the 6.0.1 source has been released yet so I don't think a recovery could be built with a 6.0.1 base of the lg g watch.
Xmaster24 said:
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that.
Click to expand...
Click to collapse
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
EpicLPer said:
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
Click to expand...
Click to collapse
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
xmaster24 said:
it's not worth it, just flash the stock boot.img once i upload it, waiting for the art cache to build now
Click to expand...
Click to collapse
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Xmaster24 said:
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Click to expand...
Click to collapse
You mean the new OTA kernel or the 6.X kernels?
EpicLPer said:
You mean the new OTA kernel or the 6.X kernels?
Click to expand...
Click to collapse
the stock kernel and nvm it was just AIDA64 glitching out, actually thought more than one core was in use The upside it thought the reboot button is back! don't know why they ever removed it but collio
Xmaster24 said:
nvm it was just AIDA64 glitching out, actually thought more than one core was in use ;-(
Click to expand...
Click to collapse
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
EpicLPer said:
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
Click to expand...
Click to collapse
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Tried, didn't work. My guess is that it didn't handle squash FS. I was left with dead Android guy on the screen
For everyone to enjoy HERE is the stock kernel, @EpicLPer add this to the op to save everyone some trouble. NOTE: you have to boot to system once before the stock recovery is restored. Also it is a twrp backup so you have to adb push it to /sdcard/TWRP/BACKUPS/ to use it. If someone could just get the boot.img raw that would be great, I was too lazy to do it lel.
Xmaster24 said:
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
Click to expand...
Click to collapse
Actually... mine's running pretty well, no lag, no freezing animations, apps take 1 second to open and scrolling is smooth too.
Either I have some leftovers of an old kernel (which I don't think, or, hope) or I'm having a magic LG Watch