Related
Hi, I was using rooted n9005 with fahadali s5 custom rom. All working excellent.
Last evening I installed this program http://forum.xda-developers.com/gal...-galaxy-sensors-temperature-humidity-t2828815 (I am not sure is this problem). Installation was not normal (it said it is installed although was not)
After some time I noticed that auto rotation, temp sensors, proximity, auto brightness- nothing is working...
I reinstalled totally with odin, full wipe- still nothing...
Is phone killed or there is some solution, I do not know what to try else more then normal odin reinstall...
help...
ivanox1972 said:
Hi, I was using rooted n9005 with fahadali s5 custom rom. All working excellent.
Last evening I installed this program http://forum.xda-developers.com/gal...-galaxy-sensors-temperature-humidity-t2828815 (I am not sure is this problem). Installation was not normal (it said it is installed although was not)
After some time I noticed that auto rotation, temp sensors, proximity, auto brightness- nothing is working...
I reinstalled totally with odin, full wipe- still nothing...
Is phone killed or there is some solution, I do not know what to try else more then normal odin reinstall...
help...
Click to expand...
Click to collapse
Need your version of rom modem bootloader. Maximum info
No fonctionnally backup????
ivanox1972 said:
Hi, I was using rooted n9005 with fahadali s5 custom rom. All working excellent.
Last evening I installed this program http://forum.xda-developers.com/gal...-galaxy-sensors-temperature-humidity-t2828815 (I am not sure is this problem). Installation was not normal (it said it is installed although was not)
After some time I noticed that auto rotation, temp sensors, proximity, auto brightness- nothing is working...
I reinstalled totally with odin, full wipe- still nothing...
Is phone killed or there is some solution, I do not know what to try else more then normal odin reinstall...
help...
Click to expand...
Click to collapse
i replied in the app thread, you had a previous version installed right? it was installation or update? and, if i can suggest you, have you tried hw test for sensors? ( *#0*# )
Thanks, friends I was so busy last evening on job.
I am afraid it is hardware damage http://forum.xda-developers.com/showthread.php?t=2428732
I hope I will not be forced to change logic board (then almost no sense), I do NOT have warranty.
@rayman95- I want make one last software attempt: please tell me what wipes/ formats to do and I will install your v13 slim.
@ale32thebest- I do not say your app killed it. It is fact that I noticed errors just after unsuccessful try to install your app. My last hope is
that it locked some system calls (maybe I am wrong). Remember, I was using fahadali s5 rom and plays store sees my phone as s5. Do you have any suggestion to try something about that
thanks again.
in recovery go to monts and storage and format system, data, cache, data and /data media + factory reset and wipe cache+dalvik
then reboot recovery and flash a rom
@rayman95 First, how to back dpi to stock in your rom 13
NOT WORKING
I have different behaviour when try *#0*# last 2 days on different roms and kernels for sensor hub test
mostly I got
FAIL and MCU Firm Version : AT0113122000 | Bin Firm Version : AT0199999
few times I got (but again go to fail)
PASS and MCU Firm Version : AT0113122000 | Bin Firm Version : AT0199999
after last install (v13 and all formats) I even can not execute*#0*# (nothing happens)
ivanox1972 said:
@rayman95 First, how to back dpi to stock in your rom 13
NOT WORKING
I have different behaviour when try *#0*# last 2 days on different roms and kernels for sensor hub test
mostly I got
FAIL and MCU Firm Version : AT0113122000 | Bin Firm Version : AT0199999
few times I got (but again go to fail)
PASS and MCU Firm Version : AT0113122000 | Bin Firm Version : AT0199999
after last install (v13 and all formats) I even can not execute*#0*# (nothing happens)
Click to expand...
Click to collapse
It smell not good.... modify build.prop with root explorer and reboot
You think it is killed. Do I must change whole motherboard or maybe only som chip?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Have the same problem.none of the sensor works tryed flashing still no use.just wanna know is this the problem of Cert file/qcn file or hardware?
Same problem!
I have the problem here. I've tryed everything: full wipe, custom rom, return to stock, downgrade, upgrade, etc.
I believe it's a hardware problem, I've bought both note 3 (mine and my wife's ) at the same time, but suddenly all sensors stop working. No root, nothing. I restore factory configuration many times, trying everything, including format and jump all account registration and don't installing nothing after format. Useless. Every time, after a few minutes, all sensors stop again.
---------- Post added at 10:01 AM ---------- Previous post was at 09:44 AM ----------
Only mine have the problem, my wife's working perfectly.
Both phones without root. I only rooted after The problem appear and try everything.
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Having problem flashing MM?
Use this method:
Reboot to twrp
2. Full wipe (data, internal card, system, cache, delvik cache, format data) All zip move to external card for a clean flash
3. Flash V2 zip - robalm's thread
4. Flash boot zip - autoprime's thread
5. Flash https://mega.nz/#!gxtwVBwZ!41S8Woy2y...HhK4gcGooK7OIo permissive zip (most important part don't forget to flash this)
6. Flash betasupersu 2.52 https://mega.nz/#!F8E02RyC!XeJhx4QZH...bVd14ccRYHbNKg ( no other version worked only this version worked)
7. Flash sharpening mod 3.5 and reboot system
To me this method works 100%
I've tried on 5 of my friend's G3 and all without fail!
4G ,Titanium and ext card works flawlessly
Reserved
Singaporean user here, so far it's been fantastic on stock marshmallow. With 21c modem there's no problem when it comes to connectivity (I'm on Singtel and I get 4G just like on Lollipop). Battery life much better than lollipop (average about 3.5-4h SOT compared to 2.5-3h on lollipop).
Here's a features review I did for the new stock MM
oceangreen said:
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Click to expand...
Click to collapse
Sorry to ask but really all International Model D855 got MM update or only Poland ? Please confirm.
OTA in Poland for D855 only
krk2krk said:
Sorry to ask but really all International Model D855 got MM update or only Poland ? Please confirm.
Click to expand...
Click to collapse
currently only Poland has update via OTA or LG PC Suite. However, there are zip files and KDZ files available that you can flash on any D855.
oceangreen said:
Having problem flashing MM?
5. Flash https://mega.nz/#!gxtwVBwZ!41S8Woy2y...HhK4gcGooK7OIo permissive zip (most important part don't forget to flash this)
6. Flash betasupersu 2.52 https://mega.nz/#!F8E02RyC!XeJhx4QZH...bVd14ccRYHbNKg ( no other version worked only this version worked)
7. Flash sharpening mod 3.5 and reboot system
Click to expand...
Click to collapse
Hi oceangreen,
Saw this thread late. Black screen, Red & Blue LED flashing problem after following autoprime's thread.
Some questions:
Step 5 - autoprime didn't have this! However, your Megasync link requires decryption key? Can u provide?
Step 6 - Is this the same as autoprime's SuperSU 2.52?
Step 7 - Is this the correct link to the sharpening mod 3.5 (http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648)? autoprime did not provide this! If I have no issues with the sharpening issue, can I skip this?
Thks in advance.
Is this still MM if use 21c modem ?
Preter said:
Hi oceangreen,
Saw this thread late. Black screen, Red & Blue LED flashing problem after following autoprime's thread.
Some questions:
Step 5 - autoprime didn't have this! However, your Megasync link requires decryption key? Can u provide?
Step 6 - Is this the same as autoprime's SuperSU 2.52?
Step 7 - Is this the correct link to the sharpening mod 3.5 (http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648)? autoprime did not provide this! If I have no issues with the sharpening issue, can I skip this?
Thks in advance.
Click to expand...
Click to collapse
This thread really need updating - or at least a sticky note to say that the better thread to use is http://forum.xda-developers.com/lg-g3/development/stock-t2961073/page252
Answer to some of my own questions:
Here are the mega links without requiring key
https://mega.nz/#!gwFhDAIb!ElPjTOntE...nGotozKUyypoAU
https://mega.nz/#!M5tkgDoR!eWGHs5O29...7uP6fiW-8pOwbw
you don't need sharpening mod if you use v2.52 see http://forum.xda-developers.com/lg-g...ables-t3282012. with this method it's simple & root sticks
The SuperSU 2.52 is the same based on the hash files.
fOxunO said:
Is this still MM if use 21c modem ?
Click to expand...
Click to collapse
yes, modem only affects cellular and things like that. The rom is still MM
Does it have volte with sg telco
Followed the flashing guide to the letter - this V2 rom is great - but for only about 3 days.
After around the 3 day mark, the error message will flash "SIM card removed The mobile network will be unavailable until you restart with a valid SIM card inserted."
The phone will reboot within 10 seconds (even if you go to airplane mode immediately). It rebooted repeatedly first time it happened.
Did a complete nuke wipe, flashed again. Same thing - at the 3 day mark - the Singtel SIM will show the same error and reboot. After that, SIM not usable at all. All telco signals (Singtel) will be gone. No phone, SMS, let alone data of any sort.
Think it is the problem with the modem.
http://forum.xda-developers.com/lg-g3/development/stock-t2961073
(Download v2 (modem from v21c) -> https://mega.nz/#!OIlwGLKS!LlcNIImHK...EzSt_ikHlWj3yY)
Tried flashing 21A, 21B, autoprime's hybrid modem. Doesn't work. Anybody else encountered similar problems?
Flashed on TWRP 2.8.7 from Stock Kit Kat 4.4.2.
Preter said:
Followed the flashing guide to the letter - this V2 rom is great - but for only about 3 days.
After around the 3 day mark, the error message will flash "SIM card removed The mobile network will be unavailable until you restart with a valid SIM card inserted."
The phone will reboot within 10 seconds (even if you go to airplane mode immediately). It rebooted repeatedly first time it happened.
Did a complete nuke wipe, flashed again. Same thing - at the 3 day mark - the Singtel SIM will show the same error and reboot. After that, SIM not usable at all. All telco signals (Singtel) will be gone. No phone, SMS, let alone data of any sort.
Think it is the problem with the modem.
http://forum.xda-developers.com/lg-g3/development/stock-t2961073
(Download v2 (modem from v21c) -> https://mega.nz/#!OIlwGLKS!LlcNIImHK...EzSt_ikHlWj3yY)
Tried flashing 21A, 21B, autoprime's hybrid modem. Doesn't work. Anybody else encountered similar problems?
Flashed on TWRP 2.8.7 from Stock Kit Kat 4.4.2.
Click to expand...
Click to collapse
I have the same problem as you. except, I did not do the update and it happened out of the blue today. Been restarting my phone and if I am lucky, sometimes I get connected to the network for about an hour before the error comes on again.
matthewmax09 said:
I have the same problem as you. except, I did not do the update and it happened out of the blue today. Been restarting my phone and if I am lucky, sometimes I get connected to the network for about an hour before the error comes on again.
Click to expand...
Click to collapse
Hi Matthew,
Saw your PM. Just to confirm that you have the same problem.
Error message - "The mobile network will be unavailable until you restart with a valid SIM card inserted"
- Bar counts up to 100% before phone reboots automatically
This is apparently a very serious problem with Android going back a few years and a few Android OS versions (KK I believe). It happens with various phone models ranging from:
LG G4
https://www.reddit.com/r/lgg4/comments/43p26p/sim_card_removed/
Nexus - Google doesn't give a F*CK
http://androidforums.com/threads/sim-card-problems.467384/
Motorola, Nexus, Samsung Galaxy etc.
https://code.google.com/p/android/issues/detail?id=66964
Google apparently doesn't give a rat's ass about it. As such it is very difficult to pin-point the problem. I have flashed & re-flashed robalm's V2 ROM at least 4 times, each time with a complete (nuke) wipe of everything including the Internal SD card. It definitely happens on the default modem (21C supposedly) that comes with it. Different modems have not helped. If you find one that works, let me know.
It cannot be a SIM card problem. Cos I've never ever taken it out since the day I got the phone. Once the problem happened, I've tried re-seating it, wiping the electrical contacts with microfibre cloth etc. Singtel shop customer service checked all the APN and network settings and confirmed it is correct, asked me to try the SIM card in other phones. Done that, nothing wrong with the SIM..
Googling further, some folks discovered that it is due to Google Apps (Play Store, Maps, G+, Gmail, Play Books/Games/Movies/Music/Services etc. etc.), which are system apps (as part of the ROM package), causing the problem after they are updated via Google Play Store. Don't we all update apps to the latest version, no?
I tried uninstalling all the updates for all of them (Settings>>Apps>>) and replacing them with the factory updates that came with the ROM. I usually freeze all the crap money sucking subscription based or in-app purchasing Google Apps that I don't use anyway. However, whether frozen or not, it still happens. Although not freezing any of them does seem more likely to cause the problem to become even more severe - like going into constant reboots as opposed to intermittent ones. When that happens, you have to go to airplane mode BEFORE the countdown completes and reboot happens. At least when it restarts, it won't hunt for the missing cellular signal and triggering another reboot. This then allows you to freeze the suckers more agressively.
It worked for a few days - I thought I had narrowed the problem down to Google Play Store, Play Framework and Play Services. But yesterday or so it has come back again with a vengeance. Freezing Google Play Store does not help by the way - besides what's the point if you can't use Play Store?
Problem is, disabling the auto-update functions on Google Play Store using:
(Play Store>>Settings>>General>>Auto-update apps>>check "Do not auto-update apps")
doesn't stop Google Play Store and Google Play services from auto-updating themselves! F*ck Google! You cannot prevent it no matter what.
Worse, everytime it auto-updates itself (or if you uninstall updates) - note that it will switch to the default setting of "Auto-update apps over Wi-Fi only" again. So you have to be fast in going to Settings in Google Play each time you reboot and open Play Store.
Some netizens have suggested ADB command line means to cripple the auto-updating. But to me that is not the freaking point. It's about trying to isolate and find the problem.
You end up uninstalling updates for Play Store several times a day but when you find that the cellular signal is gone (no bars), you realise that it has sneakily updated to 6.0.5.
But even when I uninstall all updates for Play Store. It can still happen. Maybe less frequently.
No cellular signal is bad enough. The worst aspect is the rebooting. I tried restoring my beloved KK 4.4.2 Nandroid backup but apparently I'll have to find a compatible modem again as TWRP 2.8.0 (or my previous version before upgrading to TWRP 2.8.7 for this Marshmallow) didn't manage to back it up (even though I tick everything).
Still doing trial and error to try isolating the problem. The Google apps clue seems the more likely cause, but I can't say I can discern a definite pattern yet.
It could be a bug in Marshmallow 6.0. Maybe 6.1 will solve it. Maybe its the damn Polish ROM/modem.
In the meantime, I can only say - Do not flash this ROM! Without any cellular signal, the phone is not a phone. The constantly rebooting makes it useless!
Preter said:
Hi Matthew,
Saw your PM. Just to confirm that you have the same problem.
Error message - "The mobile network will be unavailable until you restart with a valid SIM card inserted"
- Bar counts up to 100% before phone reboots automatically
This is apparently a very serious problem with Android going back a few years and a few Android OS versions (KK I believe). It happens with various phone models ranging from:
LG G4
https://www.reddit.com/r/lgg4/comments/43p26p/sim_card_removed/
Nexus - Google doesn't give a F*CK
http://androidforums.com/threads/sim-card-problems.467384/
Motorola, Nexus, Samsung Galaxy etc.
https://code.google.com/p/android/issues/detail?id=66964
Google apparently doesn't give a rat's ass about it. As such it is very difficult to pin-point the problem. I have flashed & re-flashed robalm's V2 ROM at least 4 times, each time with a complete (nuke) wipe of everything including the Internal SD card. It definitely happens on the default modem (21C supposedly) that comes with it. Different modems have not helped. If you find one that works, let me know.
It cannot be a SIM card problem. Cos I've never ever taken it out since the day I got the phone. Once the problem happened, I've tried re-seating it, wiping the electrical contacts with microfibre cloth etc. Singtel shop customer service checked all the APN and network settings and confirmed it is correct, asked me to try the SIM card in other phones. Done that, nothing wrong with the SIM..
Googling further, some folks discovered that it is due to Google Apps (Play Store, Maps, G+, Gmail, Play Books/Games/Movies/Music/Services etc. etc.), which are system apps (as part of the ROM package), causing the problem after they are updated via Google Play Store. Don't we all update apps to the latest version, no?
I tried uninstalling all the updates for all of them (Settings>>Apps>>) and replacing them with the factory updates that came with the ROM. I usually freeze all the crap money sucking subscription based or in-app purchasing Google Apps that I don't use anyway. However, whether frozen or not, it still happens. Although not freezing any of them does seem more likely to cause the problem to become even more severe - like going into constant reboots as opposed to intermittent ones. When that happens, you have to go to airplane mode BEFORE the countdown completes and reboot happens. At least when it restarts, it won't hunt for the missing cellular signal and triggering another reboot. This then allows you to freeze the suckers more agressively.
It worked for a few days - I thought I had narrowed the problem down to Google Play Store, Play Framework and Play Services. But yesterday or so it has come back again with a vengeance. Freezing Google Play Store does not help by the way - besides what's the point if you can't use Play Store?
Problem is, disabling the auto-update functions on Google Play Store using:
(Play Store>>Settings>>General>>Auto-update apps>>check "Do not auto-update apps")
doesn't stop Google Play Store and Google Play services from auto-updating themselves! F*ck Google! You cannot prevent it no matter what.
Worse, everytime it auto-updates itself (or if you uninstall updates) - note that it will switch to the default setting of "Auto-update apps over Wi-Fi only" again. So you have to be fast in going to Settings in Google Play each time you reboot and open Play Store.
Some netizens have suggested ADB command line means to cripple the auto-updating. But to me that is not the freaking point. It's about trying to isolate and find the problem.
You end up uninstalling updates for Play Store several times a day but when you find that the cellular signal is gone (no bars), you realise that it has sneakily updated to 6.0.5.
But even when I uninstall all updates for Play Store. It can still happen. Maybe less frequently.
No cellular signal is bad enough. The worst aspect is the rebooting. I tried restoring my beloved KK 4.4.2 Nandroid backup but apparently I'll have to find a compatible modem again as TWRP 2.8.0 (or my previous version before upgrading to TWRP 2.8.7 for this Marshmallow) didn't manage to back it up (even though I tick everything).
Still doing trial and error to try isolating the problem. The Google apps clue seems the more likely cause, but I can't say I can discern a definite pattern yet.
It could be a bug in Marshmallow 6.0. Maybe 6.1 will solve it. Maybe its the damn Polish ROM/modem.
In the meantime, I can only say - Do not flash this ROM! Without any cellular signal, the phone is not a phone. The constantly rebooting makes it useless!
Click to expand...
Click to collapse
Yes! correct. we have the same problem. I don't think it is a glitch on mm 6.0 because i was on lollipop 5.0 when the problem occurred and I have only flashed 5.0 roms and modems. can you try the candySiX rom and see how it fairs in your phone? CandySix Rom thread link
I tried it on my phone and was able to connect to tower until I started installing Whatsapp which cause the sucker to break and reboot. But that was in a span of 15 mins. I read that it could also be a GPS problem so I disabled GPS but the phone was still broken. From my understanding, your trail and error seems to point to the play store updating itself that causes the phone to break correct? so why not cripple it using ADB and as for the updating of apps, it be done manually through sideload. because i don't think that there will be many apps that need to be frequently updated right? and even so if we do not update the app, it does not mean that the app will lose its functionality??
matthewmax09 said:
Yes! correct. we have the same problem. I don't think it is a glitch on mm 6.0 because i was on lollipop 5.0 when the problem occurred and I have only flashed 5.0 roms and modems. can you try the candySiX rom and see how it fairs in your phone? CandySix Rom thread link
I tried it on my phone and was able to connect to tower until I started installing Whatsapp which cause the sucker to break and reboot. But that was in a span of 15 mins. I read that it could also be a GPS problem so I disabled GPS but the phone was still broken. From my understanding, your trail and error seems to point to the play store updating itself that causes the phone to break correct? so why not cripple it using ADB and as for the updating of apps, it be done manually through sideload. because i don't think that there will be many apps that need to be frequently updated right? and even so if we do not update the app, it does not mean that the app will lose its functionality??
Click to expand...
Click to collapse
Dude –punctuation please …
I wish it was that simple. I've used Android Firewall (AFSWall+) to BLOCK all internet connections for Google Play Store and Google Play Services. The sneaky bastards at Google can still somehow update the factory Google Play Store from to 6.0.5! Upon that happening, all cellular network connection WILL DEFINITELY be lost. It may or may not reboot after that.
The problem is definitely related to Google Play (Store & Services). But it is not limited to it. Even when it has not updated itself, the error message can still show up and the phone can still reboot randomly with the error message. That is why I don’t think using ADB to disable updates solves anything.
Google is definitely doing something very intrusive with their Play Store apps – (why should and) how the hell apps (even if system apps) can be allowed to affect the functions of SIM card and cellular network reception to this extent is beyond me. Big brother is really upon us.
Not keen on trying custom ROMs anymore since my S2 days. Especially when stock Marshmallow already cause so many problems. Maybe this needs to be posted in the other international LG G3 threads.
Flash tool crashed
oceangreen said:
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Click to expand...
Click to collapse
Heyy trying to flash MM but lg flash tool 2014 keeps on crashing on win 10. want to retain data so am not using TWRP. What tool are u using and software version?
Good Sharing... thus far my screen not so often give me a blank screen issue after upgrade to MM Global
Hi guys ( @Preter @matthewmax09 )
my friend's SEA device started to giving your "The mobile network will be unavailable until you restart with a valid SIM card inserted" error too.
did you solved this problem? can anyone tell a solution for this?
thanks.
So, it just popped up while my phone was idle, without anyone calling it in here first, YotaPhone finally decided to give us EU users the RU124 firmware! It looks from the changelog to be the exact EU equivalent to its RU counterpart, including YotaTravel, the return of the YotaStore and other stuff. It's been so long that I don't even remember, but I should be fine flashing this and then reflashing SuperSU and Xposed without losing anything, correct?
If you have stock recovery it will install fine. If not you should be able to grab the update zip from /cache and side load. Then reflash what you want.
Sent from my iPhone using Tapatalk
Yep I'm still on the stock recovery (I just boot TWRP every time I need it). Gotcha, then I'm just dumping my Titanium Backup folder onto my PC as a precaution, and then I'll update and report back on SU\Xposed.
Looks like whatever Yota pushed at 117MB was the wrong thing - a failed update attempt and a reboot later, it's now 0.94 GB. Seems like it's the correct size in ftp://fw.ydevices.com/YotaPhone2/Firmwares/EU/ so now it should work.
Update from RU1.1.112 to RU1.1.124 issue
https://r.tapatalk.com/shareLink?ur...share_tid=3436224&share_fid=3793&share_type=t
Sent from my iPhone using Tapatalk
Just as expected the 0.94 GB update file worked, I reflashed SuperSU and Xposed and the phone is working great on 1.124b.
What version were you coming from?
Sent from my iPhone using Tapatalk
EU1.87. I wanted to go to the RU version but never could get a KitKat RU firmware to boot on my device, so I just gave up and went back to the latest EU firmware.
Ah OK that makes sense. Glad you got it working.
Sent from my iPhone using Tapatalk
Go mine today (1.1.44HK)
Updated to EU 1.1.124b with official yotaflasher.
No Su nor any hack.
So far no bug, it's a great device.
Hi there!
I'm waiting for my yotaphone 2 from this new wave from chinese shops. I ordered the International version. Is it safe to flash the EU version firmware over the "international" version?
And please, can anyone provide an alternative downolad link for the yota flasher?
The one from offcial website:
https://yotaphone.com/us-en/ypflasher/
is a corrupted zip file.
Thanks!
Edit:
I could get it from here:
ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/
Seems there's a bug.
Almost each time i try to unlock phone (with power button) from EDP the pin keyboard isn't showing up, i must tap all over the EDP screen, way it's relocking then i can have the keyboard again.
Solved by using gesture instead of pincode
satsuki_yatoshi said:
Solved by using gesture instead of pincode
Click to expand...
Click to collapse
Gutted they removed the Instagram Cover instead of fixing it!
Rarelyamson said:
Gutted they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
Instagram restricted access to its API, so none of 3rd party apps now work properly. Thats why Instagram Cover was removed.
Hello
I deployed this great update a few days ago, and it clearly brings numerous improvements and fixes.
One visibly new bug annoys me a lot anyway, and that's why I am posting :
When I type a SMS on the EPD, lots of freezes occur. And today, I found a simple pattern. I type a word, and then I back-delete one or a few letters of it. Then I add new letters, and that frequently freezes the EPD for a long moment.
It's not 100%, lots of times it freezes under these conditions, few other times it does not.
I setup 3 languages to choose from (thanks to the update !) and the auto correction is ON.
Does someone else experience the same issue ? Any workaround or fix ?
Thanks
Appens to me 2 times, each time i needed to look/unlook the edp screen to solve
My problem is that with the latest update I need to restart my phone until it starts charging. Otherwise it will not charge ... does this happen to anybody else? Probably I should try to reset ...
no charge bug here
No charge bug here neither. Quite the opposite in fact, I would even say that autonomy obviously improved since this update.
And I confirm I have the same bug with the PIN keyboard not showing up on the EPD when using the Powa button. It happens very often after using the other screen, but unlocking by tapping twice is an easy and efficient workaround.
Surprising obvious bugs anyway, I hope the Yotagods watch us and intend to fix them.
Hi, I'm fairly new to XDA so please forgive me for my newbieness.
I recently purchased the Axon 7 but I got a lot of problems with it to which I can't find solutions here or elsewhere on the internet:
- I can't update my device, I have now A2017GV1.0.0B06 but whenever I try to update, it fails
- I can't open photos/videos in Whatsapp (crash), can't send photos/videos in Facebook messenger (just won't do it without explanation). I checked the permisions which all seem to be fine
- I got random app crashes all the time, sometimes it even uninstalls them.
- The device itself reboots every so often randomly, once or twice a day
For the most part the device works okay, but these problems just drive me insane sometimes.
Would it be a software related error, which I can maybe solve by whiping it clean all again (I had problems since the start so I doubt this would work), or by maybe rooting it?
I must say that I bought the device second hand, but it barely had been used before (everything without any scratches and fairly new in the box). So maybe that's the reason?
Many thanks,
~Pr0fviktorie
I would do a factory wrote and that the system firmware. That should solve the issues as it definitely sounds software related.
Sent from my ZTE A2017 using Tapatalk
May very well be why it was sold lol.
Regarding updating firmware, the official advice is to update to B10 MM before diving straight to Nougat.
I assume the update zip file is at least detected by system updater?
Pr0fviktorie said:
Hi, I'm fairly new to XDA so please forgive me for my newbieness.
I recently purchased the Axon 7 but I got a lot of problems with it to which I can't find solutions here or elsewhere on the internet:
- I can't update my device, I have now A2017GV1.0.0B06 but whenever I try to update, it fails
- I can't open photos/videos in Whatsapp (crash), can't send photos/videos in Facebook messenger (just won't do it without explanation). I checked the permisions which all seem to be fine
- I got random app crashes all the time, sometimes it even uninstalls them.
- The device itself reboots every so often randomly, once or twice a day
For the most part the device works okay, but these problems just drive me insane sometimes.
Would it be a software related error, which I can maybe solve by whiping it clean all again (I had problems since the start so I doubt this would work), or by maybe rooting it?
I must say that I bought the device second hand, but it barely had been used before (everything without any scratches and fairly new in the box). So maybe that's the reason?
Many thanks,
~Pr0fviktorie
Click to expand...
Click to collapse
I had the random reboot stuff too. Tried reflashing but what really fixed it was going to a custom ROM for a couple of months then flashing the stock recovery and installing the update from there
But if you don't wanna go the warranty voiding route do this:
Download Marshmallow B11 (I think it's 1.0.0B11)
Download Nougat B02 (I think it's 1.2.0B02 or 1.1.0B02, don't remember)
Update to Marshmallow B11
Now try updating to Nougat B02
---------- Post added at 04:33 PM ---------- Previous post was at 04:32 PM ----------
Hamburgle4 said:
May very well be why it was sold lol.
Regarding updating firmware, the official advice is to update to B10 MM before diving straight to Nougat.
Click to expand...
Click to collapse
wasn't B11 for that?
Choose an username... said:
wasn't B11 for that?
Click to expand...
Click to collapse
Probably. I'm just reading off the Aus firmware instructions page! Only making sure they aren't trying to jump directly to Nougat from B06 MM.
Hamburgle4 said:
Probably. I'm just reading off the Aus firmware instructions page! Only making sure they aren't trying to jump directly to Nougat from B06 MM.
Click to expand...
Click to collapse
Yeah I guess it fails because he's trying to update from B06. I'll delete the recovery part on my post just to be sure
Thanks for the suggestions, I suppose I have to do it manually?
The OTA update I am getting is MM B11, but that doesn't work. When installing it fails at around 40% and when I check why, it says that 'The system update package did not match the phone'. Would it work if I try it manually?
Pr0fviktorie said:
Thanks for the suggestions, I suppose I have to do it manually?
The OTA update I am getting is MM B11, but that doesn't work. When installing it fails at around 40% and when I check why, it says that 'The system update package did not match the phone'. Would it work if I try it manually?
Click to expand...
Click to collapse
Yeah I'd try what Choose suggested.
You can find the full update files in this thread: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
BTV-DL09 C100, locked, unrooted
I got the tablet a couple of days ago and I've been battling various things and reading lots of guides, I thought this might help others. Tab was on Android 6 with no OTA available, so before I even set it up, I used the Firmware Finder app to upgrade to Android 7 Emui 5 B307 using dload method and dialler
Everything looked good, I set it up and started using it. Then I realised Bluetooth wasn't working, I couldn't change any of the Sounds, and I had a bunch of missing stock apps including Themes, Calendar, Compass, Sound Recorder (and some more)
I went back to Firmware Finder and re-downloaded B307. Then while reading some things online, realised that when it says to put the update.app in 'dload' folder on SD Card, it means internal phone storage not the actual removable SD CARD...so I did that, and installed using 3-button method, buuuuut no change
Back to Firmware Finder this time trying to download B303, but of the many B303 files available all would error except 1, and when it did download it was always corrupt (I always chose Full OTA's) - each time I tried it would take nearly an hour. I tried the Firmware Finder PC program, and after letting it search for a really long time, it only came back with Chinese versions of the firmware. I also found lots of web pages with links to firmware but NONE of them worked, they were all dead links or would redirect to pages that wanted to install malware
Now I started thinking I would just live without Bluetooth or themes
THEN I followed the instructions on this page http://www.stechguide.com/downgrade-mediapad-m3-from-nougat-to-marshmallow/ and downloaded the files to downgrade from Nougat to MM: . This worked, BUT...upon initial setup as soon as I put my wifi password in it started to do an official update to Android 7 and I couldn't stop it because the O/S hadn't properly loaded yet! I wanted the device to start up properly so I could check that the rollback had worked, and check if Bluetooth and the other missing things were working. I risked it and restarted, then the setup started from the beginning and this time I didn't put my wifi password in and was able to complete setup
So now I was on B009, Android 6, and Bluetooth worked...success? NO! The fingerprint sensor wasn't working at all, not for fingerprints and not as a navigation key - I was forced to use the navigation bar (and it's so ugly!)
I set up everything the way I wanted and connected to PC and Hi Suite so I can do a backup, and finally, Hi Suite told me there was an upgrade to B303 available. I let that run - and after many hours of reading and trying and ending up disappointed, I am now on B303 Android 7 Emui 5, and e v e r y t h i n g works!
Bluetooth works
Wifi is fast
Tablet mode works when you select - View mode: small; Font size: normal
Blockada works to block ads
New Pipe is installed to download YT videos
Animation scale in developer options is at 0.5 so everything is snappy
OK Google works
The stereo speakers are AMAZING and loud
...perfect!
Thanks for sharing, everything working. ??
Great !!! Thanx
I have same issue. On nougat now, no keyboard, bluetooth, missing some stock apps. I am on Nougat, locked bootlaoder, US version. I just want to go back to stock, no root, no 5ghz. So I can sell it....