Related
I was one of the folks who got pushed the 20110509 build (came down this morning). Now, I have no dock at all. If I try to boot the machine with the dock attached, it stays stuck on the boot screen for minutes. If I boot without it and attach it, nothing happens for about a minute, then I get a battery icon with a question mark on it in the info window...that is it. It still is not registered with the system.
What...the...hell?
Were you rooted when you tried applying the new OTA ?
Negative. I've not rooted yet.
Sounds like you need to factory reset.
US version?
Yes, US version. Stuntdouble, is there no way to roll back an update? As in, reapply an older firmware file (20110423) that I have?
meatlocker said:
Yes, US version. Stuntdouble, is there no way to roll back an update? As in, reapply an older firmware file (20110423) that I have?
Click to expand...
Click to collapse
No I don't think so. Unless you root and re-flash with one of the roms from the dev section. Although now I've said that I'm not sure you can root from this new version yet.
Is it at least worth trying grabbing the correct downloadable firmware file from the Asus website and seeing if it will apply it ?
Yeah but only if a factory reset doesnt restore the unit to working with the dock first. I'm not a betting man but I reckon that will fix it.
Unfortunately, it didn't...I still have the same firmware (20110509) that I did before the wipe. I think the problem lies there, so I am going to need to figure out how to flash a prior firmware.
Thanks for the assistance thus far, guys.
I didnt expect it to wipe the firmware update but I did expect it to fix the connection problem. Good job I didnt bet. Anyways sorry you're having the problem. Probably a good idea to chat with those clever folks in the dev section to get it sorted though.
Thanks for the help. I was able to roll back the firmware of the device, but the dock issue remains. I am assuming that the dock itself has some kind of firmware, and that it is what got hosed.
Seams ro be plenty of people that are happy with the beta firmware. Try it one more time
Looks like the firmware push was a one-shot deal. I am not getting it offered to me again when I check for updates. As far as the dock goes, the power light is not even coming on when plugged in anymore. Friggin' weird.
meatlocker said:
Looks like the firmware push was a one-shot deal. I am not getting it offered to me again when I check for updates. As far as the dock goes, the power light is not even coming on when plugged in anymore. Friggin' weird.
Click to expand...
Click to collapse
Makes me scared to do the update that I requested from him. Looks like you were the one unlucky one of the batch according to the other dock update thread. Sucks!
This was a BETA firmware update so yeah once you download it it thats it.
Theres no real reason to discus it here any further, you need to contact the Asus dev thats been working with us on this and he'll work with you to get your dock working again. They did this beta release to make sure it worked before going with a full release. You signed up for a beta unverified release, that means there could be issues.
As you can see in the topics, most of us have had no issues. so just go talk to the asus dev and i'm sure he'll work with you to repair everything.
Already PM'd him. Will update with a response.
meatlocker said:
Already PM'd him. Will update with a response.
Click to expand...
Click to collapse
the fact he plugging it in has no light on sounds to me the dock is broken. factory reset wont help because that resets the tablet only. seem like a particular case here tho. i bet if you try a different dock itll work just fine. best of luck you find a fix soon.
mine installed the beta tablet firmware, then as soon as it booted it updated the dock firmware
did yours update the dock firmware on next reboot?
also... this may sound dumb, but does the dock have any battery life? Unplug your tablet from it, and plug the charger into it. See if the LED lights turn on...
No, it didn't. I got no notification at all about the dock getting updated (or needing to be updated). They were connected when I got the update, the unit restarted, and no more dock. If I try to restart with the dock in place, it just hangs on the second Asus boot logo. 2 seconds after I undock, I end up on the login screen.
I've spoken to Asus this morning, run through the normal wipe steps, and now waiting on a senior tech call. I doubt there is much that they can do, unless there is a magic key combo or other backdoor to refire the dock. It looks like I'm going to be RMA'ing back to NewEgg.
It's interesting that everyone else who has done this update has said that there is a 'part 2' to the update, which updates the dock. So the dock itself has firmware, this pretty much confirms.
I just wondering as still haven't!
I never got 1.47, I'm still on 1.28. I'm not sure why.
My DS is an unbranded unlocked UK model.
We are certainly not the only people not to get 1.47.
At first I was glad that I did not get 1.47, but now I notice that (so far) only people with 1.47 seem to be getting the recent upgrade.
Least am not the only one! HTC support seems to think I would need to send my phone away for repair to have it updated!
podycust said:
Least am not the only one! HTC support seems to think I would need to send my phone away for repair to have it updated!
Click to expand...
Click to collapse
Seriously. All HTC seem to say is any update news will appear first on Twitter or Facebook, yet when anyone has questioned them on there they deny any knowledge of the update even with proof
The only thing they use social networking for is product spamming and corporate shindig promoting!!
Got a small update months ago which installed an updater, but never got 1.47. Still on 1.28. Unbranded, unrooted.
Interested to learn what HTC told you about returning it...
Yes I got those same updates months ago too! This is what they said after first saying 1.28 was the latest and then me saying I know about some with 1.47
Thank you for your reply regarding your Desire S.
The case there is an update available and you cannot receive it through 'OTA', the device may need to be sent for repair. then your device gets updated to the latest version.
Please confirm the following information in order to be able to book the device for repair:
From which address you wish the collection to happen
On which day you wish the collection to happen (please allow 48 hours’ notice)
The Serial Number of your device. (Serial Number can be found underneath the battery.) I will then book and confirm this via Email and provide further repair instructions:
We can arrange for UPS to collect your device from an address (Mainland UK only) that is convenient for you. UPS can collect on Monday through Friday from 1pm to 5pm. There is no UPS service on Weekends and Public Holidays.
Click to expand...
Click to collapse
Do have in your applications (settings> manage applications> all) an install called Updater version 2.3?
I think - not sure - that this is what was installed by the small update? Or is it for the Market? Terribly tempted to uninstall it and see what happens, eg if it updates again, but to 1.47. Or perhaps just try clear data.
Unfortunately to ignorant to know the risk if any...
Yes I and this what small update was it just updates the FOTA program which updates the phone firmware
podycust said:
Yes I and this what small update was it just updates the FOTA program which updates the phone firmware
Click to expand...
Click to collapse
Say again please?
yes it did install updater version 2.3. if you uninstall it you will be asked to install it again!
DON'T INSTALL 1.47!
Please! If you're looking to depress yourself, google "desire s late sms", look at the hundreds of pages of results, from users all over the world with the same problem.
You lucky ones who are still on 1.28 havent suffered the misery of the problem with 1.47 and the Desire S. Just imagine how much fun could be had, every time you're connected to a mobile data network (GPRS, 3G or HSDPA), knowing that there's a better than 50/50 chance all your 2G functions will stop working. Calls will go straight to voicemail, texts will fail to arrive for hours on end... And then randomly, you'll get a dozen messages at once, from people wondering why you've ignored them all afternoon...
Seriously, stick with 1.28 for now, wait for the next update.
We will need to have 1.47 before we can get 2.10!
fasty said:
I never got 1.47, I'm still on 1.28. I'm not sure why.
My DS is an unbranded unlocked UK model.
We are certainly not the only people not to get 1.47.
At first I was glad that I did not get 1.47, but now I notice that (so far) only people with 1.47 seem to be getting the recent upgrade.
Click to expand...
Click to collapse
can you use wireshark to analyze what the update sever's response is?
as when I've done that it replys {"time_msec":"1317992280856","stats_ok":true,"reason":"FOTACANCEL_NO_MATCH_RULE_FOR_CID","intent":[{"action":"android.server.checkin.FOTA_CANCEL"}]}
as mine is also an unbranded unlocked uk model
podycust said:
can you use wireshark to analyze what the update sever's response is?
as when I've done that it replys {"time_msec":"1317992280856","stats_ok":true,"reason":"FOTACANCEL_NO_MATCH_RULE_FOR_CID","intent":[{"action":"android.server.checkin.FOTA_CANCEL"}]}
as mine is also an unbranded unlocked uk model
Click to expand...
Click to collapse
I'd prefer not to install wireshark right now, but I'm certain that I would get the same response.
There are plenty of other people in the same situation. I'm guessing that HTC may have aborted deployment of 1.47 because they noticed that it caused so many issues.
I assume that the "no match rule for CID" simply means that there are no updates available for our particular software version at the moment.
I've just factory reset my DS in the hope of fixing another issue, and after doing so it politely updated the version of it's FOTA loader but nothing else new.
Starting deployment of the sense 3.0 version to a few users without any explanation seems a bit dumb of HTC unless they are simply beta testing.
I could understand them prioritising those who have already loaded 1.47 as clearly this is causing them the most issues. We just need to hope that they don't forget those if us who are still on 1.28
- Steve
had your phone been rooted before you get it?
helicopterpro said:
had your phone been rooted before you get it?
Click to expand...
Click to collapse
Nope, I don't think so. My phone was new, carrier unlocked "sim-free" version from an authorised HTC retailer in the UK. I was previously using an Orange SIM in it, although recently switched to Three. (Have tried to get update when connected to both)
Prior to making this thread, I'm active in this thread, talking about my update situation.
------------------------------------------
UPDATE: This is how you bypass the activation screen! Big thanks to @henser for figuring it out!
------------------------------------------
Here's my situation (which seems to fit others in the same situation so it's not just me) : My wife and have Moto Gs (hers an XT1028 wifi-only, mine an XT1031 wifi-only), and hers is "locked by Verizon and cannot be activated" (basically meaning it's never been scanned by a VZW cashier). She received the 5.1 OTA, and updated. Everything went smoothly, and she decided she wanted a fresh start, so she factory reset the device.
Bad move.
Apparently, the old bypass methods for Moto G's activation screen are now patched and no longer work in LP. This means that because VZW has "locked the device" and it "cannot be activated", she is ultimately stuck at the Setup Wizard / Activation screen with nothing to do but wait until someone figures out the new method.
Traditionally, a person might think of something else to do like unlock the bootloader and root it, but the XT1028's bootloader cannot be unlocked.
Did you try pulling down the notifications bar. Just try to get the navigation buttons back then press home or recent apps. That might be able to help!
jakeh9777 said:
Did you try pulling down the notifications bar. Just try to get the navigation buttons back then press home or recent apps. That might be able to help!
Click to expand...
Click to collapse
That method has been patched as well. To my experience, every previous bypass has been patched. I know of 5, and have extensively searched for more.
DamianHelixTV said:
That method has been patched as well. To my experience, every previous bypass has been patched. I know of 5, and have extensively searched for more.
Click to expand...
Click to collapse
Ok I would like to help out more and try but I don't want to reset my device right now. Just try all methods even older ones that are found on other devices too. Just let everyone know when you found one and I will just search the Internet for awensers too.
happened to me aswell i did factory reset, may i know if i can rollback to 4.4.4 ??
henser said:
happened to me aswell i did factory reset, may i know if i can rollback to 4.4.4 ??
Click to expand...
Click to collapse
Doesn't seem to be a way to downgrade, other than getting Motorola to give a free replacement Moto G and it just happen to not be on LP.
DamianHelixTV said:
Doesn't seem to be a way to downgrade, other than getting Motorola to give a free replacement Moto G and it just happen to not be on LP.
Click to expand...
Click to collapse
can you tell me where is the link to chat with motorola, thank you
henser said:
can you tell me where is the link to chat with motorola, thank you
Click to expand...
Click to collapse
This should be it: (link)
i have given these 2 options but unfortunately none of the options work for me
The first option is called Advance Exchange: This require for you to provide a credit card to which we place a hold for $100, now this program includes a premium fee for $24.99 (amount that will not be refundable), in regards to allow us to send you the replacement device to you first, and you have up to 5 days to return the defective one to Motorola, once received the defective device, the hold will be released. The shipping label you will receive along with the shipping instructions will expire in 5 days.
Erick: The second option is called Return and Exchange: On this scenario, you must send the defective device first, once received we process the replacement and send it to you. In this case, it takes 2 Business days for us to receive your device and as soon as we receive this unit it takes 3 - 5 Business days in order to be delivered to you. The shipping label you will receive along with the shipping instructions will expire in 3 days.
henser said:
i have given these 2 options but unfortunately none of the options work for me
The first option is called Advance Exchange: This require for you to provide a credit card to which we place a hold for $100, now this program includes a premium fee for $24.99 (amount that will not be refundable), in regards to allow us to send you the replacement device to you first, and you have up to 5 days to return the defective one to Motorola, once received the defective device, the hold will be released. The shipping label you will receive along with the shipping instructions will expire in 5 days.
Erick: The second option is called Return and Exchange: On this scenario, you must send the defective device first, once received we process the replacement and send it to you. In this case, it takes 2 Business days for us to receive your device and as soon as we receive this unit it takes 3 - 5 Business days in order to be delivered to you. The shipping label you will receive along with the shipping instructions will expire in 3 days.
Click to expand...
Click to collapse
I chose the 2nd option. Though... I didn't know the label expired. Crap. Gotta get a new label.
yes i was tryng to get to the setting, i made a wipe data reset. and a window popped up. asking me if i want to get roaming but gave me a global number i tapped into it and i could go to add as an contact. and got into the dial number is there a way to dial a number and go to the settings tab ? i could activate or deactivate airplane mode and activate the bluetooth but i couldn't turn on the wifi.
edit:
also i could enter to file explorer but i cant select home or the other buttons and my pc detect the phone but doesn't show any files
Try dialing *228 then select option 1
Can I just BLOCK the upgrade to lollipop?
My MOTXT1028NPP works just fine for what I need.
I Don't have service, WIFI only.
Every time I turn it on, it says it's gonna upgrade to lollipop. Only option have is to delay until later the same day.
I don't want ANY upgrade. It works just fine for what I need.
It appears from this thread that the upgrade will prevent me using the device without service and prevent installing a custom rom???
Maybe only if I factory reset?
What if I need a factory reset for some other purpose?
Googling suggests that some people have experienced slowdowns from the upgrade that were fixed by a factory reset.
I considered the possibility that I might be able to install a custom ROM before it updates,
but those all seem to have issues.
Is there away to just PREVENT, PERMANENTLY, any and all upgrades, including this one??
spamme0 said:
Can I just BLOCK the upgrade to lollipop?
My MOTXT1028NPP works just fine for what I need.
I Don't have service, WIFI only.
Every time I turn it on, it says it's gonna upgrade to lollipop. Only option have is to delay until later the same day.
I don't want ANY upgrade. It works just fine for what I need.
It appears from this thread that the upgrade will prevent me using the device without service and prevent installing a custom rom???
Maybe only if I factory reset?
What if I need a factory reset for some other purpose?
Googling suggests that some people have experienced slowdowns from the upgrade that were fixed by a factory reset.
I considered the possibility that I might be able to install a custom ROM before it updates,
but those all seem to have issues.
Is there away to just PREVENT, PERMANENTLY, any and all upgrades, including this one??
Click to expand...
Click to collapse
On the contrary, we've already figured out a bypass for the activation but that's only needed if you plan on factory resetting.
In any case, you said you don't want to update. I think you can disable the OTA app, that would make the update notification not happen again until you want to in the future.
Also, unless you're one of those people who have an unlocked bootloader and a custom recovery on the XT1028 (some people do who got the device early) you can't flash any ROMs.
DamianHelixTV said:
On the contrary, we've already figured out a bypass for the activation but that's only needed if you plan on factory resetting.
In any case, you said you don't want to update. I think you can disable the OTA app, that would make the update notification not happen again until you want to in the future.
Also, unless you're one of those people who have an unlocked bootloader and a custom recovery on the XT1028 (some people do who got the device early) you can't flash any ROMs.
Click to expand...
Click to collapse
Have you seen this on youtube
watch?v=fiXZwX_Wvx8&feature=youtu.be
I have found it on reddit
/r/MotoG/comments/3tbyq0/1st_gen_moto_g_on_lp_new_activation_bypass/
Hey all,
I'm thinking of buying a Mate 7 and switching over from my Moto X Pure. Mainly for the size, metal body, and the battery. Right now I can get it for ~$330 on Amazon. The only thing that's held me back is the software. I've read the stock software is very annoying with constant notifications about apps using up too much RAM/battery. But all these reviews were from the phone's release, I haven't been able to find much information since it's been updated to Marshmallow. I typically like very light ROMs like CM but I see there hasn't been a whole lot of development for this phone other than the KangVIP ROM which seems to have a lot of issues. So I guess my question is how do you all like the stock Marshmallow ROM and is it still good on battery life?
Also I've seen a lot of threads about how to downgrade the software to earlier versions of Android, is this just to install an earlier version of Cyanogenmod? I've not been able to find a "why" in all the threads I've seen on the subject. I've found plenty of Chinese phones that are ~6" with a big battery and metal body but LTE bands are always an issue. This is the only phone I've come across that seems to have everything, other than my concerns about the software. I'm also thinking of holding out and seeing if the Asus Zenfone 3 and the LeTV Max Pro end up having U.S. LTE bands.
Anyway, any thoughts or opinions would be greatly appreciated!
It's getting old now, still a really nice phone but I'd be looking at newer devices at this point. People regress to earlier versions of Android as the MM beta releases often dissapoint. I stuck with the latest release of Lollipop as I have some limited functionality with Xposed, got ViPER4Android working etc, it's smooth and stable. Battery is great. It's hard to describe just how much freedom that allows you compared to other devices. My Oppo Find 7 is a nice phone too, but it just doesn't last long enough and being used to the Mate 7, that annoys me greatly. I do find that the oppo at 5.5" is better to handle and fits a pocket easier. That extra half inch really is noticeable on the Mate. It is one device that does feel a little special though. Once it's optimised and personalised, it's gorgeous.
As for ROMs, not going to happen any time soon. I'm happy with stock, rooted and modded. Doesn't worry me apart from limiting lifespan, but if development did take off, I would be happy.
Huawei just don't understand the international market yet and if they did, and fostered good relations and supported development, they would be able to become #1 I think, but at this point their thinking is still very Chinese.
RobboW said:
It's getting old now, still a really nice phone but I'd be looking at newer devices at this point. People regress to earlier versions of Android as the MM beta releases often dissapoint. I stuck with the latest release of Lollipop as I have some limited functionality with Xposed, got ViPER4Android working etc, it's smooth and stable. Battery is great. It's hard to describe just how much freedom that allows you compared to other devices. My Oppo Find 7 is a nice phone too, but it just doesn't last long enough and being used to the Mate 7, that annoys me greatly. I do find that the oppo at 5.5" is better to handle and fits a pocket easier. That extra half inch really is noticeable on the Mate. It is one device that does feel a little special though. Once it's optimised and personalised, it's gorgeous.
As for ROMs, not going to happen any time soon. I'm happy with stock, rooted and modded. Doesn't worry me apart from limiting lifespan, but if development did take off, I would be happy.
Huawei just don't understand the international market yet and if they did, and fostered good relations and supported development, they would be able to become #1 I think, but at this point their thinking is still very Chinese.
Click to expand...
Click to collapse
Thanks for the quick reply RobboW! I've always had phones that had a lot of development so I've kind of taken it for granted. A couple years ago I wouldn't have even considered a phone without a lot of development but my ROM addiction has really subsided and I only recently put a custom ROM on my Moto X. Honestly I don't do much customization anymore, the thing that made me apprehensive about the Mate 7 was all the "battery saving" shenanigans. If there's some way to disable those while still keeping good battery life (which definitely should be possibly with the 4100 mAh battery) then I'll be happy with the ROM, provided there's no lag. I don't do any kind of gaming or anything, just browsing the web, videos, texts, and emails, but I can't stand any kind of lag.
Thanks again for your help, it's been a grueling process trying to find a phone that meets all my criteria for a reasonable price. The Mate 7's hardware hits it perfectly, so if I can live with the software I still think it's a good deal.
It sounds like your user case is much like mine then. The Mate 7 (get 32Gb version and insert a 128Gb uSD) should serve you well. Update it from kitkat to lollipop for UI smoothness, unlock bootloader, install TWRP recovery, root and do a little debloat, although there's really not much bloat, install Viper if sound is your thing. You will need a different launcher and icon pack to get away from Huawei launcher which is terrible.
For the notifications, it has a notification manager so you can customise that to your liking. Mine doesn't bombard me with warnings. The battery is awesome, just go to power saving settings, ignore the savings and set it to normal. It still easily goes a day with heavy use.
My son liked mine and wanted to update his galaxy S4 so got a Mate 7 32Gb and I did all these things to his. He has wifi and BT on all day, facebook messenger always on etc and it never has a battery problem. He is still gobsmacked by it. Says it's better in every way to the S4 other than maybe the lack of ir blaster (which he doesn't care about) and amoled screen in the S4 but the Mate 7 screen is really nice anyway. I actually like the IPS panel better than amoled as I think amoled is gharish, too colourful, just not realistic and the IPS seems much nicer, more realistic for photos and video. It's actually a warmish tint, unlike my oppo which has a very stark, cold tint and is harder on my eyes.
You can adjust the screen and I set it to it's coldest but it's still warmer than the oppo.
I've been toying with the idea to go back to using the Mate 7 as my daily phone instead of the oppo. I was going to use the Mate 7 as a tool, like a small tablet because it will be the database and interface (BT) between an electrical test tag machine and a label printer. The camera is really good at macro focus and reads barcodes very well.
I didn't want to talk it up to someone expecting a 6P and lot's of custom roms, but for the price they can be bought for now, and your user case, it will make a great daily driver. Just be very sure it works on the correct bands you need there in the US. It works great here in Australia.
Edit: I'm having an issue with my Oppo where sometimes I can't view an email when others work ok. The Mate 7 doesn't have the issue and I've been going through settings looking for differences as the two phones are set up almost the same. Cannot find the problem so I have my SIM in the Mate again (Titanium Backup is so handy for transfering sms and call data) and will try to get a custom ROM in the Oppo.
The Mate works great. No desire for a ROM in that unless I update to MM when/if I can get a stable final release that is originally OTA.
Well I went ahead and bit the bullet and I'm going for it. I'll probably need to be pointed in the right direction once it arrives as far as which ROM to install and how I go about downgrading it if I need to. Thanks again for your help! I'm excited to check it out.
@RobboW has said pretty much all there is that's worth mentioning about the device. If you're after stellar battery life and a solid daily driver you can't go wrong, but don't expect the flexibility of devices that are more open to customization.
I've updated to the official MM release and have yet to encounter any of the issues people complained about in the beta releases. While the LP release is fantastic (and Viper actually works on it, which I miss), the MM build offers even better responsiveness and an overall better-rounded software experience, although that's not saying I wouldn't flash something entirely different in a heartbeat (if only I could....).
The camera is also not very great. On paper it's decent, but photos almost always come out blurry (as there's no OIS) and washed out. A but of tinkering on Snapseed can make a big difference though, but don't expect anything too great.
If you already bought it I'd suggest that you immediately install a 3rd party launcher of your choice to avoid the stock launcher (which really is horrendous), and then root if that's your sort of thing.
Enjoy!
Scruffykid said:
The camera is also not very great. On paper it's decent, but photos almost always come out blurry (as there's no OIS) and washed out. A but of tinkering on Snapseed can make a big difference though, but don't expect anything too great.
Enjoy!
Click to expand...
Click to collapse
Scruffy, set the saturation in the camera app settings a notch higher. You can also set the brightness down a little if needed. I actually find the camera pretty good. It's not a flagship camera but it's also not a cheap one.
I've got my SIM back in my Oppo today, got OmniROM set up pretty nice now. So much better than ColorOS from Oppo. The B331 LP Mate 7 ROM is quite nice for a stock ROM IMO and I'm still happy to keep it. If the Oppo is stable on OmniROM, maybe I'll look at updating the Mate 7 to MM, but not if I can't have Xposed and ViPER4Android......
I'm on Marshmallow on the Oppo now and it's a PIA with some things. File explorers have issues with access, notifications are more intrusive, but it is a nice OS other than that. I actually found Lollipop easier to use.
---------- Post added at 10:54 AM ---------- Previous post was at 10:47 AM ----------
Prozart said:
Well I went ahead and bit the bullet and I'm going for it. I'll probably need to be pointed in the right direction once it arrives as far as which ROM to install and how I go about downgrading it if I need to. Thanks again for your help! I'm excited to check it out.
Click to expand...
Click to collapse
It will ship with Kitkat so you boot and see which firmware version it's on and what OTA update it wants to install when it goes online, but don't install it straight away, come back to the forum with the information and then the correct update tree can be looked at.
Don't leave it on Kitkat, IMO, you either use B331 Lollipop or a Marshmallow ROM. Nothing earlier. Some of the MM ROMS do need an earlier Lollipop version to update from, but sometimes you can flash the ROM anyway, as long as the phone is compatible with it.
RobboW said:
Scruffy, set the saturation in the camera app settings a notch higher. You can also set the brightness down a little if needed. I actually find the camera pretty good. It's not a flagship camera but it's also not a cheap one.
Click to expand...
Click to collapse
I can't seem to find the settings you're mentioning in my camera settings. Perhaps it was removed on the MM builds? Anyway I think simply installing 3rd party camera software should make a big difference. As you and I both said, most of what's wrong with the camera is software.
Haven't tried MM on my Mate 7 so couldn't speculate, but from Google Play, give Open Camera a try, it's free. See if pics match the viewing angle you expected.
For a paid app, Camera FV-5 is very good. It's supposed to mimmick a DSLR.
Edit:
Just installed Open Camera (by Mark Harmon) on both phones. Works well. Two things I like are the availability of grid lines and a level indicator. Makes quite a difference when doing landscape photography. I live in a seaside town and getting horizon level is so important with shots including ocean. If it had panorama mode I'd be a happy chappy!
I haven't been bothered with camera apps on my Mate 7 as it has a good camera on KK and LP and I had no need to look for better. The Oppo Find 7 is another matter. Oppo camera was good with ColorOS, but now on OmniROM, I needed to look at camera apps, but had already found the others with my previous phone as it was a THL W200 and stock software was pretty crap.
RobboW said:
It will ship with Kitkat so you boot and see which firmware version it's on and what OTA update it wants to install when it goes online, but don't install it straight away, come back to the forum with the information and then the correct update tree can be looked at.
Don't leave it on Kitkat, IMO, you either use B331 Lollipop or a Marshmallow ROM. Nothing earlier. Some of the MM ROMS do need an earlier Lollipop version to update from, but sometimes you can flash the ROM anyway, as long as the phone is compatible with it.
Click to expand...
Click to collapse
Alright so it arrived today with KK 4.4.2 build number 120SP04. I went to the updater and it said no updates are available. I don't have a SIM card in it so I don't know if that makes a difference. I didn't realize it didn't have a nano sim slot so I'll have to go to my carrier to get a micro. In the mean time, what are my upgrade paths to a good Lollipop or Marshmallow? I'm in North America and on the main page I only saw update packages for India, Europe, and China I believe. Would I just go with the European ones?
Prozart said:
Alright so it arrived today with KK 4.4.2 build number 120SP04. I went to the updater and it said no updates are available. I don't have a SIM card in it so I don't know if that makes a difference. I didn't realize it didn't have a nano sim slot so I'll have to go to my carrier to get a micro. In the mean time, what are my upgrade paths to a good Lollipop or Marshmallow? I'm in North America and on the main page I only saw update packages for India, Europe, and China I believe. Would I just go with the European ones?
Click to expand...
Click to collapse
Will you be using an SD card? Slot 2 takes either an SD or a nano SIM, not both at once though.
That's the same ROM my phone came on. It's the standard international ROM for a non carrier locked TL10 goldie.
It will update to B130 OTA
From B130 I flashed mine to B331 Lollipop (newest lollipop). Just a download of ROM and place in dload folder and point the updater to it, then it does it from within the OS. It won't go past B130 on an OTA.
If you want MM, that needs to be loked at as there are stacks of vesions. I'm inclined to think if it can be flashed up to MM from B331 it's reasonably new. That's my aim. I won't go to an older LP to get up to a buggy old beta MM.
Here's the download link where I got my stable Lollipop.
http://www.carbontesla.com/2016/01/download-ascend-mate-7-full-b331-lollipop-firmware-europe/
It seems to me that Huawei are still slowly releasing updates so I would rather sit on a stable LP and wait for the last MM rather than join the unhappy bunch of early flashers who have bugs or bricks.
B331 LP works well and can get some limited use of Xposed and full use of Viper4android.
You need to keep stock recovery to flash an update but unlocked bootloader is fine, so I'd look to unlock the bootloader after it gets B130 update.
It will have a choppy UI on KitKat, it's normal. Lollipop fixes that.
I reckon you'll last maybe 5 minutes trying to use the Huawei launcher. Don't fight that, just install another, lol. Have to go into settings and choose default launcher in the app management section.
RobboW said:
Will you be using an SD card? Slot 2 takes either an SD or a nano SIM, not both at once though.
That's the same ROM my phone came on. It's the standard international ROM for a non carrier locked TL10 goldie.
It will update to B130 OTA
From B130 I flashed mine to B331 Lollipop (newest lollipop). Just a download of ROM and place in dload folder and point the updater to it, then it does it from within the OS. It won't go past B130 on an OTA.
If you want MM, that needs to be loked at as there are stacks of vesions. I'm inclined to think if it can be flashed up to MM from B331 it's reasonably new. That's my aim. I won't go to an older LP to get up to a buggy old beta MM.
Here's the download link where I got my stable Lollipop.
http://www.carbontesla.com/2016/01/download-ascend-mate-7-full-b331-lollipop-firmware-europe/
It seems to me that Huawei are still slowly releasing updates so I would rather sit on a stable LP and wait for the last MM rather than join the unhappy bunch of early flashers who have bugs or bricks.
B331 LP works well and can get some limited use of Xposed and full use of Viper4android.
You need to keep stock recovery to flash an update but unlocked bootloader is fine, so I'd look to unlock the bootloader after it gets B130 update.
It will have a choppy UI on KitKat, it's normal. Lollipop fixes that.
I reckon you'll last maybe 5 minutes trying to use the Huawei launcher. Don't fight that, just install another, lol. Have to go into settings and choose default launcher in the app management section.
Click to expand...
Click to collapse
Awesome, thanks for your help! Since its saying "no updates available" should I manually update it to B130 and then to the link you provided for B331?
And yeah I've already got a launcher I've been using and like, I'm already sick of the stock launcher, lol. Also, strangely, the play store force closes after a few seconds of opening. I'm not too worried about it as I'll very soon be flashing different firmware, but still strange. Also, this is the MT7 L09 version, should I still update B130>B331?
And as far as Marshmallow is concerned I'm inclined to take your path with a stable Lollipop until they get MM all worked out.
Prozart said:
Awesome, thanks for your help! Since its saying "no updates available" should I manually update it to B130 and then to the link you provided for B331?
And yeah I've already got a launcher I've been using and like, I'm already sick of the stock launcher, lol. Also, strangely, the play store force closes after a few seconds of opening. I'm not too worried about it as I'll very soon be flashing different firmware, but still strange. Also, this is the MT7 L09 version, should I still update B130>B331?
And as far as Marshmallow is concerned I'm inclined to take your path with a stable Lollipop until they get MM all worked out.
Click to expand...
Click to collapse
L09, well that changes everything. You can go to B522 MM on that already. Update to B331, see how you like it. You can update to B522 from there anyway.
Google Play FC will be it trying to update itself whilst you're using it.
Check your ROM matches the number of the update. There are update notes included with it. If it doesn't match, it will fail to flash once most of the way through it. This is the CUST folder and is ROM specific for different areas of the world. It's where most naive users brick their phone.
For instance, mine is C900B331 and the original would have been C900B120SP04
That C900 is most important.
What many don't realise is that the number of the ROM doesn't always mean newer. It could be for a different region and that region has a different sequence of ROM designations.
RobboW said:
L09, well that changes everything. You can go to B522 MM on that already. Update to B331, see how you like it. You can update to B522 from there anyway.
Google Play FC will be it trying to update itself whilst you're using it.
Check your ROM matches the number of the update. There are update notes included with it. If it doesn't match, it will fail to flash once most of the way through it. This is the CUST folder and is ROM specific for different areas of the world. It's where most naive users brick their phone.
For instance, mine is C900B331 and the original would have been C900B120SP04
That C900 is most important.
What many don't realise is that the number of the ROM doesn't always mean newer. It could be for a different region and that region has a different sequence of ROM designations.
Click to expand...
Click to collapse
Thanks to you I successfully updated to B331. I got my launcher installed and now I just need to change the DPI as everything is huge, lol. So now I need to unlock bootloader and root it. But so far everything is smooth, no problems yet.
Edit: Quick question. I went into the APN settings and accidentally clicked on preferred network type. Before I went in there it was set to LTE (and I was successfully connected to LTE) but that wasn't an option to click on when I went into the settings. It's only showing me these three and so I'm not getting LTE anymore. Any ideas?
Check dual card settings for default 4G slot.
Edit: Why am I suggesting that for an L09, lol.
Have you done anything to upset the settings for APN?
Have a look in power saving settings to see if anything there cuts it back to 3G to save juice.
4G really sucks battery compared to 3G.
RobboW said:
Check dual card settings for default 4G slot.
Edit: Why am I suggesting that for an L09, lol.
Have you done anything to upset the settings for APN?
Have a look in power saving settings to see if anything there cuts it back to 3G to save juice.
4G really sucks battery compared to 3G.
Click to expand...
Click to collapse
I can't find anything i n the power settings regarding network modes, I believe the only thing I've changed is putting the power plan on Normal and turning off Power-intensive prompt.
Also on the keyboard, the keys aren't vibrating. I went into the keyboard settings and made sure it was turned on. Also tried toggling it off and on with no success. Are there any other vibration settings hidden somewhere that I'm missing?
I wonder if a factory reset is in order. Just to count out any leftovers. I do wonder though, if there is something funny about the bands the carriers allow to work in the US. I often see comments from US XDA members about bands. Like the US is really different than the rest of the world or something.
RobboW said:
I wonder if a factory reset is in order. Just to count out any leftovers. I do wonder though, if there is something funny about the bands the carriers allow to work in the US. I often see comments from US XDA members about bands. Like the US is really different than the rest of the world or something.
Click to expand...
Click to collapse
Yeah I may try that when I get home tonight. I need to unlock bootloader and root anyway so that'll wipe it. It's just so weird cause I had LTE up until the point when I went into settings and clicked on WDCMA or whatever and now there's no option to get back to LTE. It's also not connecting via bluetooth to my car. It had no problems connecting to my Moto 360, I don't know what would be different about my car. But it's not detecting it at all. Perhaps a factory reset would help solve that.
I spent about an hour last night reading up on unlocking the bootloader. I tried emailing Huawei and they directed me to log in to my Huawei account and I'd be able to get the code after 14 days. Is there any other way to do this? I mean I can survive a couple weeks without root, but it's not optimal, lol.
Don't root it yet and don't flash recovery.
Unlock the bootloader first. Read the following thread where I show the trick for getting your code easy and free.
http://forum.xda-developers.com/mate-7/general/bootloader-unlock-longer-anymore-t3296725
I've put mine back to stock B331 as much as possible tonight and flashed stock recovery then dirty flashed B331 back over it. About to factory reset it then attempt flashing Marshmallow.
Edit:
Reset went ok.
Edit:
Started the update, got to 96% and failed (CUST FAIL) and rebooted, sat on the start screen for quite a while and then booted. It's on C900B522 Marshmallow but I'm not sure what impact the cust fail has, but it seems to run fine. The dual card management settings are there so it is running as the TL10 that it is, although in settings it's calling itself a JAZZ.
RobboW said:
Don't root it yet and don't flash recovery.
Unlock the bootloader first. Read the following thread where I show the trick for getting your code easy and free.
http://forum.xda-developers.com/mate-7/general/bootloader-unlock-longer-anymore-t3296725
I've put mine back to stock B331 as much as possible tonight and flashed stock recovery then dirty flashed B331 back over it. About to factory reset it then attempt flashing Marshmallow.
Edit:
Reset went ok.
Edit:
Started the update, got to 96% and failed (CUST FAIL) and rebooted, sat on the start screen for quite a while and then booted. It's on C900B522 Marshmallow but I'm not sure what impact the cust fail has, but it seems to run fine. The dual card management settings are there so it is running as the TL10 that it is, although in settings it's calling itself a JAZZ.
Click to expand...
Click to collapse
I upgraded to 522 and so far it seems to be working well. Having some problems with Google Play Services (says it needs to update but the option isn't available in the play store) but otherwise seems great. Got LTE back and I've connected via Bluetooth to my car. I'm thinking about upgrading to 560 tonight. So I'm trying to follow your instructions on unlocking the bootloader but I don't understand where I need to go to type in the IMEI. I went to the website and logged in but then it takes me to this page (which doesn't seem to have an English version) and I have no idea where to go from there.
Hello XDA!
First of all, long time lurker, but infrequent poster here. My phone is an Asus ROG Phone 5s Pro running stock and non-beta software and is not rooted. I am reaching out to see if anyone on here who has more technical savvy than me (which is probably most of y'all) can help me figure out how to reinstall a fresh factory image on my Asus ROG Phone 5s Pro or can offer any other possible solutions for my issue.
The reason I am wanting to do this is because I recently installed a software update from Asus that seems to have a persistent issue that is a pretty major problem to me. The issue is that whenever I reboot the phone and plug in headphones and audio plays, but it stutters and BLASTS out of the headphones (multiple sources tried, even happens with system notification sounds). This only happens with wired headphones and never with Bluetooth. I had this happen to me once for less than a half a second and my ears were persistently ringing for about 3+ hours after this and I am certain that it damaged my hearing to a small degree. Because of this I no longer trust to use any headphones with the phone and this is a huge bummer because I use wired headphones A LOT.
I have tried to factory reset the phone several times already and the issue persists through without any restoring of anything during setup (in fact it won't recognize the backup that it created the day before the factory reset), but the issue is still present. I contacted Asus customer support (for which lets just say I have strong feelings on) and explained the issue and they want me to RMA the phone for a hardware issue.
I really do not wish to do this as this means I will have to either switch phones a few times which is always incredibly time consuming or be without a phone for an estimated period of up to 10 days if I do the RMA. I also disagree that this is a hardware issue because of two things: 1) if it were a hardware issue then I would think that the problem would be constant and not happen just once after each reboot and I would think that doing something in the software, i.e. a reboot, wouldn't consistently recreate the problem. Thus I am trying to find a way to "restore" the operating system of this device to see if I can solve what I believe to be a software issue that shouldn't require any RMA.
I have seen that posts that linked official files from Asus before, such as the "AsusUnlock_1.0.0.7_210127_fulldpi.apk" found in the OP of the "Install any custom ROM on ROG Phone 5 / 5s (GSI)" thread here in this very forum. Is anyone aware of any officially sourced files for stock software/firmware for this phone and a process through which I could reinstall it?
I am also open to thoughts and other possible options to consider.
Also I will give bonus points to anyone who can help me figure out how to fix the issue where my Google backup by this very same phone won't restore its own Google backup when going through the setup and can help me restore it. It does recognize a different Google backup for a tablet that is set up for my child to use, so it is not an issue with the restore being completely broken.
Thanks in advance for anyone willing to try and lend a hand.
Hi, here you can find stock firmwares make sure you got for right region.
ROG Phone 5s Pro | Gaming Phones｜ROG - Republic of Gamers｜ROG Global
Fueled for winning by the latest Qualcomm® Snapdragon® 888+ 5G mobile platform, ROG Phone 5s Pro launches your mobile gaming experience into the next dimension. With an unbelievably responsive 360 Hz native touch-sampling rate, the 144 Hz / 1 ms display brings you the smoothest ever viewing...
rog.asus.com
Yeah, just for additional info for anyone who finds this. I've also been working with ASUS customer support. I was given two links on flashing official firmware:
Unofficial guide on flashing - https://www.asus.com/support/FAQ/1009748/
Official firmware images - https://rog.asus.com/phones/rog-phone-5s-pro-model/helpdesk_bios (same as previous comment above; thanks Teddy)
When I asked why my version is newer than any they currently have listed on the site I was told that it "could be a preview release given directly by Google" (I doubt this as this appeared as an official OTA by Asus that had very specific patch notes to this phone in it) and that because my version is newer than any listed on their site would result in trouble if I tried to flash the newest version listed, but an older firmware than what is currently installed and that I should still just RMA my phone.
For reference my current firmware is RKQ1.210303.002.WW_Phone-18.1220.2201.186 and the latest firmware listed on their site at the time of this writing is WW-18.1220.2111.164.
Great phone (aside from the hearing damage), but utterly useless support.
Still open to thoughts and ideas though if anyone still has any.
You can "downgrade" your firmware by doing a RAW flash directly to version you need OR to any lower version and then install the official ASUS version you want manually. Also need to disable OTA updates to avoid being updated to the latest automatically.
Having the device checked for hardware issues is probably the best idea however.
Andrologic said:
You can "downgrade" your firmware by doing a RAW flash directly to version you need OR to any lower version and then install the official ASUS version you want manually. Also need to disable OTA updates to avoid being updated to the latest automatically.
Having the device checked for hardware issues is probably the best idea however.
Click to expand...
Click to collapse
Could you provide more info on this "downgrade" via "a RAW flash"? Is there a guide or something that will give more info about this?
I think I might be screwed though for the RMA. Customer service says apparently its a Taiwan version and cannot be serviced in the USA and has to be sent to via Taiwan RMA and the page they gave me seems to indicate there are no service centers for ROG Phones; see https://www.asus.com/support/service-center/taiwan#.
Short rant is that I literally spent hours and I mean HOURS (if not possibly days) of my time with Asus customer service and searching online trying to find a US version with US warranty and ultimately getting nowhere and deciding to go with the one I have now. Four months in to a $1700 phone and basically I am stuck with a dangerous headphone jack and no option to fix it other than maybe what you mentioned, Andrologic.
Today has not been kind.
ChrisMills83 said:
Could you provide more info on this "downgrade" via "a RAW flash"? Is there a guide or something that will give more info about this?
I think I might be screwed though for the RMA. Customer service says apparently its a Taiwan version and cannot be serviced in the USA and has to be sent to via Taiwan RMA and the page they gave me seems to indicate there are no service centers for ROG Phones; see https://www.asus.com/support/service-center/taiwan#.
Short rant is that I literally spent hours and I mean HOURS (if not possibly days) of my time with Asus customer service and searching online trying to find a US version with US warranty and ultimately getting nowhere and deciding to go with the one I have now. Four months in to a $1700 phone and basically I am stuck with a dangerous headphone jack and no option to fix it other than maybe what you mentioned, Andrologic.
Today has not been kind.
Click to expand...
Click to collapse
There are links to download RAW images along with guides in the help thread pinned to the top of this forum. You should find what you need there. The RAW's come include flash scripts that does it all for you.
Just curious for opinions while this thread is still going:
Does anyone lean towards my issue being a hardware problem or something else (and if you could be specific and suggest something for me to try about it)?
The reason why I ask is because I personally feel like this is an issue with when the headphone jack initializes output or something because it only ever blasts audio after a reboot and I any audio plays. After it stops and plays again the levels seems to return to normal. I can also reliably make this happen the same way every single time. Finally (and somewhat conspiratorially), the update I installed just before this started to happen had patch notes that included "optimized audio parameters."
My appreciation in advance for any thoughts and insights.