My brand new sealed HTC 10 just arrived yesterday. For some reason I can't pull down the notification bar when I swipe down from the top.
I have tried factory resetting my phone, wiping cache and updating my phone to the latest software update but the problem still persists.
If I swipe down the notification bar while on the lock screen, it works fine and it pulls up the notifications along with the "Quick toggle" items.
When the phone is unlocked and then rotated to landscape mode it also works fine and pulls up the notifications.
The notification panel won't slide down when the handset is unlocked and left in portrait mode!
I'm on stock 1.95.401.3 with S-ON.
When the phone is unlocked and then rotated to landscape mode it also works fine and pulls up the notifications.
Click to expand...
Click to collapse
Strange, because normally it doesn't work in landscape mode !!!
hija31 said:
Strange, because normally it doesn't work in landscape mode !!!
Click to expand...
Click to collapse
Nevermind just found out my digitizer is defective out of the box lol
I used the line sensor test and the top part didn't register any red lines
http://imgur.com/a/fbyE4
hija31 said:
Strange, because normally it doesn't work in landscape mode !!!
Click to expand...
Click to collapse
You think so....?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from quite brutal hTc 10 ..
@jauhien
Yes, stock and not rooted.
i have same issue but i have find a solution for htc 10 is android casual issue after MM is solved whit this tricks for other smartphone: Go to settings - users - switch to "guest" - switch back to "owner".
But HTC 10 dont have this option, my casual find for resolve this issue if restore the phone whit ruu
and when you make a setup after reboot end of restore change the name at your phone
(before i have assigned every time same name at my phone=Paolo after ruu update i have changed whit any other)
after this notification bar pull down again
ps: before this solution when make a test line in my htc 10 notification area in the top of screen dont sign any lines(i make this test in the first step of inizial setup) after the apply my solution in the last step of wizard
after changed the name of phone i have make again the line test and top of screen is sensisitive again and pull down works.
iccipsu said:
Nevermind just found out my digitizer is defective out of the box lol
I used the line sensor test and the top part didn't register any red lines
http://imgur.com/a/fbyE4
Click to expand...
Click to collapse
solved see my post, is not a hardware issue but android bug, before the solution i have same line in your screenshot after fix all touch screen is drawable
caxio said:
i have same issue but i have find a solution for htc 10 is android casual issue after MM is solved whit this tricks for other smartphone: Go to settings - users - switch to "guest" - switch back to "owner".
But HTC 10 dont have this option, my casual find for resolve this issue if restore the phone whit ruu
and when you make a setup after reboot end of restore change the name at your phone
(before i have assigned every time same name at my phone=Paolo after ruu update i have changed whit any other)
after this notification bar pull down again
ps: before this solution when make a test line in my htc 10 notification area in the top of screen dont sign any lines(i make this test in the first step of inizial setup) after the apply my solution in the last step of wizard
after changed the name of phone i have make again the line test and top of screen is sensisitive again and pull down works.
Click to expand...
Click to collapse
i am having the same problem, would you be able to help me do this? how do i do this, can you go step by step please? i have tried everything, this started on STOCK rom after i updated and the i tried resetting phone, then I tried custom rom, nothing helped. I would greatly appreciate your help. Thank You.
caxio said:
i have same issue but i have find a solution for htc 10 is android casual issue after MM is solved whit this tricks for other smartphone: Go to settings - users - switch to "guest" - switch back to "owner".
But HTC 10 dont have this option, my casual find for resolve this issue if restore the phone whit ruu
and when you make a setup after reboot end of restore change the name at your phone
(before i have assigned every time same name at my phone=Paolo after ruu update i have changed whit any other)
after this notification bar pull down again
ps: before this solution when make a test line in my htc 10 notification area in the top of screen dont sign any lines(i make this test in the first step of inizial setup) after the apply my solution in the last step of wizard
after changed the name of phone i have make again the line test and top of screen is sensisitive again and pull down works.
Click to expand...
Click to collapse
Its not working
Shafin Uddin said:
Its not working
Click to expand...
Click to collapse
confirm in my case working only for short time at the end is a hardware defect of upper part of touch screen only way is rma in warranty period
I am also facing same issue, please help me. I had tried flashed stock rom and even up to three-four custom roms but nothing changed.I had also tried the "guest user" method. My status bar is not coming down in portrait mode and only when the phone is unlocked . But when I tried in reverse portrait mode, everything works fine. But, please do give me a solution for this problem as soon as possible
Anurag98 said:
I am also facing same issue, please help me. I had tried flashed stock rom and even up to three-four custom roms but nothing changed.I had also tried the "guest user" method. My status bar is not coming down in portrait mode and only when the phone is unlocked . But when I tried in reverse portrait mode, everything works fine. But, please do give me a solution for this problem as soon as possible
Click to expand...
Click to collapse
What you are describing is a hardware issue that HTC is always good about repairing when it does rarely happen.
Set phone back to stock configuration, and call HTC and tell them of the issue. They will repair it under warranty or send you a new device.
You can call them before setting the device back to stock but make sure you have the correct firmware and correct stock rom for your region/carrier etc. That way if they attempt to troubleshoot it or walk you through providing information step by step asking you questions, you will have the same menus.
HTC will repair a hardware defect like this under warranty.
Sent from my HTC 10 using Tapatalk
This is hardware issue. When I buy my HTC 10 it comes with this problem. After they changed it I experienced this problem again. I think this phone has digitizer bug and something was happen it trigged this issue.
I am facing this problem too and I believe it is not hardware issue. because I can pull down notification on lockscreen. And also those notif bar area are touchable when I'm using camera.
I have the same issue. Notification shade doesn't pull down in portrait mode while unlocked. Notification pulls down fine while locked so I don't understand how this can be hardware.
I've played with it on the lockscreen and pull down is very responsive. Anybody find a fix?
Related
This morning I received a software update message from AT&T, when I tried to update it, i got this error. My phone is rooted and installed CWM.
Is that the reason why it won't let me install the update? Do I have to unroot the phone back to factory setting ?
Once I download the update and hit install, the phone will restart and goto CWM screen (screen shot). Can someone tell me how to fix that and do the upate ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I haven't looked into it myself so i'm not 100% but from what i've read this update is just to comply with apple winning an injunction against android's universal search in a patent lawsuit. So instead of being able to simultaneously search the web, your contacts and your apps. you'll only be able to search the web from the google search bar. I would just avoid installing it at all personally and go with custom roms where the chef can cook in the old universal search.
True.
lungfujinshin said:
I haven't looked into it myself so i'm not 100% but from what i've read this update is just to comply with apple winning an injunction against android's universal search in a patent lawsuit. So instead of being able to simultaneously search the web, your contacts and your apps. you'll only be able to search the web from the google search bar. I would just avoid installing it at all personally and go with custom roms where the chef can cook in the old universal search.
Click to expand...
Click to collapse
I made the mistake of thinking this was the Jelly Bean update and updated...:crying:
You need the stock recovery (3e) to update with ota's.
johnw91498 said:
I made the mistake of thinking this was the Jelly Bean update and updated...:crying:
Click to expand...
Click to collapse
I was hoping it was too ,but I hope you have a backup to go back if you updated.
I too am rooted with CWM and have the notice to update. I know not to update but how do I get rid of the annoying notice, the only options are to postpone for 1, 4 or 8 hours I do not see a cancel option anywhere.
Foolishly Accepted OTA=BRICK
I should have known better than to accept the OTA with the phone rooted! It now only shows the SAMSUNG logo and "Boot Recovery" up at the top briefly before turning off again. After work I'll be attempting to fix it... Any guidance on how would be greatly appreciated. My girlfriend is probably calling and texting about the house being on fire or something and I have no idea lol.
I used the SGSIII toolkit posted somewhere else on this forum to root.
JaguarGuy said:
I should have known better than to accept the OTA with the phone rooted! It now only shows the SAMSUNG logo and "Boot Recovery" up at the top briefly before turning off again. After work I'll be attempting to fix it... Any guidance on how would be greatly appreciated. My girlfriend is probably calling and texting about the house being on fire or something and I have no idea lol.
I used the SGSIII toolkit posted somewhere else on this forum to root.
Click to expand...
Click to collapse
Flash to stock, rinse, repeat.
Then once you root again, install Titanium Backup and freeze the software update app. That will put it to sleep for good without uninstalling it entirely.
-Ryan
Success!
ryandelman said:
Flash to stock, rinse, repeat.
Then once you root again, install Titanium Backup and freeze the software update app. That will put it to sleep for good without uninstalling it entirely.
-Ryan
Click to expand...
Click to collapse
I was able to use the toolkit on the home computer to put the phone in download mode. A wave of relief hit me the moment I saw my phone go from black to the download screen lol... From there, like you said, was able to flash and fix. Thanks! And today I've learned a valuable lesson about OTA updates...
A side note, the house is not on fire and my girlfriend was still asleep where I left her.
JaguarGuy said:
I was able to use the toolkit on the home computer to put the phone in download mode. A wave of relief hit me the moment I saw my phone go from black to the download screen lol... From there, like you said, was able to flash and fix. Thanks! And today I've learned a valuable lesson about OTA updates...
A side note, the house is not on fire and my girlfriend was still asleep where I left her.
Click to expand...
Click to collapse
good thing there wasn't a fire while she was asleep! on another note, i only got a text telling me that there was an updated. i'm kind of intrigued as to why some of you got actual notifications almost making you upgrade vs me only receiving a message. i'm assuming that i must have not noticed that i froze/uninstalled the update app.
JaguarGuy said:
I was able to use the toolkit on the home computer to put the phone in download mode. A wave of relief hit me the moment I saw my phone go from black to the download screen lol... From there, like you said, was able to flash and fix. Thanks! And today I've learned a valuable lesson about OTA updates...
Click to expand...
Click to collapse
Can you please point me to where I can find the "toolkit" or the stock ROM that is safe for AT&T i747? Thanks.
is the "updated app" named update.apk? if not, i would appreciate someone sharing the name of the app to freeze. thanks.
Toolkit
heringcheng said:
Can you please point me to where I can find the "toolkit" or the stock ROM that is safe for AT&T i747? Thanks.
Click to expand...
Click to collapse
The link below is the toolkit I used to root originally as well as fix my SGSIII earlier. It is a great program; make sure to thank the author if you find it useful.
http://forum.xda-developers.com/showthread.php?t=1746665
cortez.i said:
is the "updated app" named update.apk? if not, i would appreciate someone sharing the name of the app to freeze. thanks.
Click to expand...
Click to collapse
I didn't see 'software update app' either - but there is a 'FWUpgrade 1.2.0' that has the same icon as the notification about the OTA update so I'm assuming it's that one - I froze it and rebooted, and nope - the reminder notification is still there.
So...
Searching on the backup/restore tab shows 'AT&T Software update V3_1205_2_2' - and that icon matches the color of the notification, so I'm assuming it's that one and now the notification is gone.
Not sure if I need to unfreeze that 'FWUpgrade' app, but I wouldn't think so. I picture my life with the stock rom to be more of a one night stand rather than a meaningful relationship...
This thread might be useful if you want to apply the OTA from CWM without losing root and without getting the Google Search "upgrade": http://forum.xda-developers.com/showthread.php?t=1768826
'AT&T Software update V3_1205_2_2'
^ that's the app you wanna freeze.
Hope this helps.
- Ryan
Sent from my SAMSUNG-SGH-I747 using xda premium
I bought a tab 3 8.0 recently and which after it got updated through wifi touch was not responding as it should later I restared and it was back to normal. Later after few hours the problem started so I rebooted into recovery to clear the cache it displayed error. The tab works fine sometimes but goes back to touch unresponsiveness when I resume the tab after resumining from sleep mode. Can any please help meand if there are similar problems with tab 3
ansonlarken said:
I bought a tab 3 8.0 recently and which after it got updated through wifi touch was not responding as it should later I restared and it was back to normal. Later after few hours the problem started so I rebooted into recovery to clear the cache it displayed error. The tab works fine sometimes but goes back to touch unresponsiveness when I resume the tab after resumining from sleep mode. Can any please help meand if there are similar problems with tab 3
Click to expand...
Click to collapse
you cannot clear cache from stock recovery.
Only data. (act as reset anyways)
just odin another firmware see if it continues.
Update works most of the time, if you let it sits for around 15 minutes after updating.
Many people got problem after system updates was caused by themselves really.
Rules for updating.
1) let it sits for 15 minutes after update.
2) Do not do manual reboot right after update. (After auto reboot) (Wait for 15 Minutes -- minimal)
3) Do not run/install/download right after update. (Leaving it alone for 15 minutes)
4) make sure nothing is running before tapping system update. (reboot, wait 3 minutes, then press system update) / or clear ram from task manager before tapping system update
*Reasons: update is installed, but it might have to convert/translate certain already existing data. We don't know, but just to avoid data corruption, just leave it alone and do not interrupt the process by doing anything above.
The problem still persist...even after resetting the device through recovery and settings... now when I try to update it says that I have the latest update what do I do. Where do I get another firmware if I wana odin the device. This is really annoying help me please
comscier said:
you cannot clear cache from stock recovery.
Only data. (act as reset anyways)
just odin another firmware see if it continues.
Update works most of the time, if you let it sits for around 15 minutes after updating.
Many people got problem after system updates was caused by themselves really.
Rules for updating.
1) let it sits for 15 minutes after update.
2) Do not do manual reboot right after update. (After auto reboot) (Wait for 15 Minutes -- minimal)
3) Do not run/install/download right after update. (Leaving it alone for 15 minutes)
4) make sure nothing is running before tapping system update. (reboot, wait 3 minutes, then press system update) / or clear ram from task manager before tapping system update
*Reasons: update is installed, but it might have to convert/translate certain already existing data. We don't know, but just to avoid data corruption, just leave it alone and do not interrupt the process by doing anything above.
Click to expand...
Click to collapse
The problem still persist...even after resetting the device through recovery and settings... now when I try to update it says that I have the latest update what do I do. Where do I get another firmware if I wana odin the device. This is really annoying help me please
ansonlarken said:
The problem still persist...even after resetting the device through recovery and settings... now when I try to update it says that I have the latest update what do I do. Where do I get another firmware if I wana odin the device. This is really annoying help me please
Click to expand...
Click to collapse
Samfirmware.com is the place to get firmware.
Sent from my GT-P5210 using XDA Premium HD app
Benzoman said:
Samfirmware.com is the place to get firmware.
Sent from my GT-P5210 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks will check It out
US Firmware
I had trouble finding the US version of the Firmware for the Tab 3 8" until I found this post
http://forum.xda-developers.com/showthread.php?t=2471516
it contains a link to the firmware :good:
ansonlarken said:
I bought a tab 3 8.0 recently and which after it got updated through wifi touch was not responding as it should later I restared and it was back to normal. Later after few hours the problem started so I rebooted into recovery to clear the cache it displayed error. The tab works fine sometimes but goes back to touch unresponsiveness when I resume the tab after resumining from sleep mode. Can any please help meand if there are similar problems with tab 3
Click to expand...
Click to collapse
I'm having the exact same issue that you are, and it is in fact extremely annoying. I'm the one that posted the firmware for our device (linked in the post above this,) and it will not fix our problem.
I've flashed stock rom, modified rom, modified kernel, stock kernel, wiped every single thing possible, and have had absolutely no luck with getting the touch panel (digitizer) working properly again.
It has something to do with the tsp driver being corrupt, or stuck in a constant loop of powering on/off. If you connect to ADB and run "dmesg" you will see over and over again
"[TSP] DVFS On!" and then [TSP] DVFS Off!"
Something to do with "melfas-ts," I think.. As far as I know, it's a Mali chipset, and we need to somehow get the kernel to reinitialize it, or remove it and then reinstall it..
Here's a picture of what I'm talking about:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
foil said:
I'm having the exact same issue that you are, and it is in fact extremely annoying. I'm the one that posted the firmware for our device (linked in the post above this,) and it will not fix our problem.
I've flashed stock rom, modified rom, modified kernel, stock kernel, wiped every single thing possible, and have had absolutely no luck with getting the touch panel (digitizer) working properly again.
It has something to do with the tsp driver being corrupt, or stuck in a constant loop of powering on/off. If you connect to ADB and run "dmesg" you will see over and over again
"[TSP] DVFS On!" and then [TSP] DVFS Off!"
Something to do with "melfas-ts," I think.. As far as I know, it's a Mali chipset, and we need to somehow get the kernel to reinitialize it, or remove it and then reinstall it..
Here's a picture of what I'm talking about:
Click to expand...
Click to collapse
Dude the problem is resolved.... i went to a samsung servicing center told them about the problem, they said it would take atleast 2 days to check it. Finally the tab is working absolutely ok as it should be. Said they had to change the motherboard. Thats all they said as there was a problem linked with it. Why don't you get it checked and i think thats the only solution rather then hampering the device. Good luck. I also tried almost everything.
ansonlarken said:
Dude the problem is resolved.... i went to a samsung servicing center told them about the problem, they said it would take atleast 2 days to check it. Finally the tab is working absolutely ok as it should be. Said they had to change the motherboard. Thats all they said as there was a problem linked with it. Why don't you get it checked and i think thats the only solution rather then hampering the device. Good luck. I also tried almost everything.
Click to expand...
Click to collapse
I appreciate the input, and I have actually already sent it off to a service center this morning. However, I'm a hardware hacker, and know what I'm doing with it - it's the touch panel controller that needs the firmware reflashed onto it. If I could reflash the firmware myself, I would have much rather done that, and also had a fix for everybody else. I need the device too bad for work at the moment, or I wouldn't have even bothered sending it in.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally Here!
Firstly thanks everyone who helped me test this!
It is a work in progress so don't expect much
Code:
#include "std_disclaimer.h"
/*
* Your warranty is void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Device Tree: https://github.com/armandopartida0/android_device_zte_urd
Kernel Tree: https://github.com/armandopartida0/android_kernel_zte_urd/tree/cm-14.1-test
Vendor Tree: https://github.com/armandopartida0/vendor_zte_urdLatest (Will upload link when new version is out): https://www.androidfilehost.com/?fid=1322778262904004195
Working:
Data
Calls (no VoLTE yet)
SMS
MMS
Wifi
Bluetooth
Screen (XD)
Buttons
Volume (Soundcloud does not work for some reason)
Fingerprint
Camera (No video record)
GPS
Everything else not mentioned in Not Working (I hope)
Not Working:
Flash Notification Toggle (some 3rd party apps work)
Video Recording
VoLTE
Soundcloud music app (does not play audio)
Hotspot
You tell me
How to Flash:
Make sure you are rooted by following this guide: https://androidforums.com/threads/new-root-method-for-z981-zmax-pro.1284305/
Boot into TWRP
Wipe system, data, cache, internal storage
Flash lineage zip
GAPPS (Optional)
Flash MAGISK
DONE!
DO NOT DONATE UNLESS YOU WANT TO: https://www.paypal.me/APartida332
Awesome! Thank you!
I can't seem to get my newly rooted z981 to get past the boot Ani. For this ROM nor discorded
ctindell1981 said:
I can't seem to get my newly rooted z981 to get past the boot Ani. For this ROM nor discorded
Click to expand...
Click to collapse
Make sure to flash magisk after flashing all of the other stuff
armandop_ said:
Make sure to flash magisk after flashing all of the other stuff
Click to expand...
Click to collapse
Thank you for your support
I love love love the ROM. Once I flashed magisk on a hunch that I needed magisk installed to boot... it booted. Fast. So I'm here to report oddities.
The Gboard app (flashed with open gapps) closes if I click on any of it's settings besides theme. I've tried installing from the play store to see if the results bath but it stays the same.
The camera take pics upside down. I've reflashed the ROM and heeded differing results. Sometimes the app crashes and never loads the viewfinder. Fish does not work at all. Video does work though... Long as the app works
There send to be an issue with accessing external storage. The first flash it recognized my songs etc. Then randomly it couldn't find anything on my sdcard. After 3 reflashes it started working. Each reflashes was for me messing up.
Bluetooth doesn't want to turn on sometimes. It takes restarting the phone.
Torch causes reboots
Randomly all apps will start force closing
I found that it works best to flash ROM>flash other apps such as titanium backup, etc>flash magisk>boot>go through lineage setup>reboot recovery>flash gapps>reboot>sign in to Google>open magisk and check that the settings are correct>flash systemless Xposed>reboot recovery>flash arise 4 Android>reboot>profit
I'm interested in this. My father has been wanting something other than stock on his. I'll keep watch on this, good work.
just picked one of these up for 50 bucks. not a bad device. would love this rom to be polished on it. heres to the future! gonna give it a run and report back. thanks!!
I'm not asking for an ETA by any means. That being said, so you plan on fixing bugs?
Hotspot issue
Wondering if anyone fix the hotspot problem? & The rear camera?
oscar112709 said:
Wondering if anyone fix the hotspot problem? & The rear camera?
Click to expand...
Click to collapse
so what i found out with this rom is that wifi tether router app works for tethering wifi you need to set it up correctly to get it to show up + when you are connecting to the phone threw wifi make sure your phone screen does not turn off before the connection is complete or the app will shut off. usb tethering has to use a 3rd party app like clockwork mod usb teher or pda net is the only way i could get that to work as well but it does work.warrning when useing wifi tether your phone will get hot!!!!!! so i just put it by a fan. the camera is werid im not really sure how i got it to work but you can try make a backup then restore it DO NOT HAVE A PASSWORD SET ON PHONE WHEN DOING THE BACK UP OR YOU WILL NOT BE ABLE TO OPEN THE PHONE not sure why but just giving a heads up
Cloudxddd said:
so what i found out with this rom is that wifi tether router app works for tethering wifi you need to set it up correctly to get it to show up + when you are connecting to the phone threw wifi make sure your phone screen does not turn off before the connection is complete or the app will shut off. usb tethering has to use a 3rd party app like clockwork mod usb teher or pda net is the only way i could get that to work as well but it does work.warrning when useing wifi tether your phone will get hot!!!!!! so i just put it by a fan. the camera is werid im not really sure how i got it to work but you can try make a backup then restore it DO NOT HAVE A PASSWORD SET ON PHONE WHEN DOING THE BACK UP OR YOU WILL NOT BE ABLE TO OPEN THE PHONE not sure why but just giving a heads up
Click to expand...
Click to collapse
I got the tether to work but the wifi tether router app can't get the router to work correctly looked up the setting still no luck, what settings you have it on?
I got the flashlight to work with this app Flashlight Tile Fix Kenzo_v1.7 works nice...
oscar112709 said:
I got the tether to work but the wifi tether router app can't get the router to work correctly looked up the setting still no luck, what settings you have it on?
I got the flashlight to work with this app Flashlight Tile Fix Kenzo_v1.7 works nice...
Click to expand...
Click to collapse
wifi channel 1 interface wlan0 methed 2 android vertion 4.2 0r higher prevents stand by checked lte thether patch checked turn your wifi off before enabling it it will take about a min or two keep scaning for your wifi do not let the screen turn off until its connected
Cloudxddd said:
wifi channel 1 interface wlan0 methed 2 android vertion 4.2 0r higher prevents stand by checked lte thether patch checked turn your wifi off before enabling it it will take about a min or two keep scaning for your wifi do not let the screen turn off until its connected
Click to expand...
Click to collapse
Got it to work thanks just, xb1 can't find thanks this
Bit of a silly question, but does this ROM work on the non-pro version of this phone, i.e. Z970?
Is this ROM still being developed? I've had the Zmax Pro for a couple years now, and the software is sorely lacking in a lot of areas. I'd love to see a decent replacement, as the phone has good potential.
I've got a spare one I can try out the ROM on. I'll try to do that when I get some time.
Thanks for your work on this.
toaddawet said:
Is this ROM still being developed? I've had the Zmax Pro for a couple years now, and the software is sorely lacking in a lot of areas. I'd love to see a decent replacement, as the phone has good potential.
I've got a spare one I can try out the ROM on. I'll try to do that when I get some time.
Thanks for your work on this.
Click to expand...
Click to collapse
Ice Bear believes there is work being done on a something sweeter, and it begins with O or P. Don't quote Ice Bear on that though. Ice Bear is just making a hypothesis.
Ice Bear said:
Ice Bear believes there is work being done on a something sweeter, and it begins with O or P. Don't quote Ice Bear on that though. Ice Bear is just making a hypothesis.
Click to expand...
Click to collapse
Very good hypothesis
Hello and thanks for your hard work. I am/was loving this rom. But for some reason my phone quit booting after having been running the rom with no major issues for several months. My phone is stuck on the first boot flash screen that says ZTE and powered by android. I am trying to get it to let me into recovery so I can reflash the room but I am having no success. I don't believe I have enough time to get the phone to accept the key presses to trigger entering recovery. I have tried to load up adb but again I don't think the phone is getting far enough to communicate with the adb. Any help or suggestions would be greatly appreciated. So to recap the phone is basically stuck on at the first splash screen and will only reboot when the power button is pressed and held. Thansk!
davvid420 said:
Hello and thanks for your hard work. I am/was loving this rom. But for some reason my phone quit booting after having been running the rom with no major issues for several months. My phone is stuck on the first boot flash screen that says ZTE and powered by android. I am trying to get it to let me into recovery so I can reflash the room but I am having no success. I don't believe I have enough time to get the phone to accept the key presses to trigger entering recovery. I have tried to load up adb but again I don't think the phone is getting far enough to communicate with the adb. Any help or suggestions would be greatly appreciated. So to recap the phone is basically stuck on at the first splash screen and will only reboot when the power button is pressed and held. Thansk!
Click to expand...
Click to collapse
I think your only option here is getting into twrp somehow.
Make sure to power off the device by holding power.
Turn it back on by holding "volume up and power" and do not let go till you see twrp recovery.
Note:
If holding power button to shut it down causes the phone to reboot instead then you have to time it and hold volume up and power right when the screen shuts off.
I was in a similar situation, but for different reasons(development) and the power button was only rebooting, so I timed it and got into twrp.
Good luck
GameTheory. said:
I think your only option here is getting into twrp somehow.
Make sure to power off the device by holding power.
Turn it back on by holding "volume up and power" and do not let go till you see twrp recovery.
Note:
If holding power button to shut it down causes the phone to reboot instead then you have to time it and hold volume up and power right when the screen shuts off.
I was in a similar situation, but for different reasons(development) and the power button was only rebooting, so I timed it and got into twrp.
Good luck
Click to expand...
Click to collapse
Thanks I got it taken care of. I ended up taking the phone apart and disconnecting the battery and holding the volume up and down key at the same time while in plugged in the usb cord hooked up to my computer.
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j
Razviar said:
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j
Click to expand...
Click to collapse
Did you try out the first posts suggestion?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Morgrain said:
Did you try out the first posts suggestion?
View attachment 5483007
Click to expand...
Click to collapse
Yep, didn't work. In the end, safe mode boot worked. Way to fix it:
1. Boot in safe mode (volume down while looking at boot animation)
2. Wifi on in safe mode
3. Open Play Market and update everything
4. Reboot normally.
Razviar said:
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
https://www.reddit.com/r/GooglePixel/comments/rfzz6j
Click to expand...
Click to collapse
Hey! I also experienced this problem. Following the steps about updating Google apps doesn't really help as the error reboot will come again the next time you reboot your phone. Rather, follow Razviar solution that you need to enable airplane mode as soon as your phone boots up and enable wifi. Only after a while you can turn off airplane mode and start using cellular data. That way you'll be able to safely avoid the restart loop.
Never expected such a silly bug on a flagship device. Shame on you, Google!
hafatih27 said:
Hey! I also experienced this problem. Following the steps about updating Google apps doesn't really help as the error reboot will come again the next time you reboot your phone. Rather, follow Razviar solution that you need to enable airplane mode as soon as your phone boots up and enable wifi. Only after a while you can turn off airplane mode and start using cellular data. That way you'll be able to safely avoid the restart loop.
Never expected such a silly bug on a flagship device. Shame on you, Google!
Click to expand...
Click to collapse
I managed to restart the phone once without getting error message, but next reboot failed again. So currently on affected devices we have to do this reboot shaman dance every time we need to reboot.
hafatih27 said:
Hey! I also experienced this problem. Following the steps about updating Google apps doesn't really help as the error reboot will come again the next time you reboot your phone. Rather, follow Razviar solution that you need to enable airplane mode as soon as your phone boots up and enable wifi. Only after a while you can turn off airplane mode and start using cellular data. That way you'll be able to safely avoid the restart loop.
Never expected such a silly bug on a flagship device. Shame on you, Google!
Click to expand...
Click to collapse
Hey guys, I'm also having the exact same problem with my pixel 6 pro December build SQ1D.211205.016.A1. And I can confirm that restarting while airplane mode On prevents the phone from restarting again and crash with "failed to load Android system". I really hope Google acknowledge this problem and fix it in future updates. I posted the issue in google community support and no one replied. I thought I was the only one having this issue. Y_Y
imivantj said:
Hey guys, I'm also having the exact same problem with my pixel 6 pro December build SQ1D.211205.016.A1. And I can confirm that restarting while airplane mode On prevents the phone from restarting again and crash with "failed to load Android system". I really hope Google acknowledge this problem and fix it in future updates. I posted the issue in google community support and no one replied. I thought I was the only one having this issue. Y_Y
Click to expand...
Click to collapse
did you fix your issue? it looks like restarting in safe mode and updating all your google services apps can resolve your issue. if not, flashing the mid-november build can fix it also.
Alekos said:
did you fix your issue? it looks like restarting in safe mode and updating all your google services apps can resolve your issue. if not, flashing the mid-november build can fix it also.
Click to expand...
Click to collapse
I haven't tried restarting with my Internet turned on again. I'll just wait until January or February update by Google and see how it goes. I don't want to do any tinkering with safe mode or flashing of builds because my device is an import set and if I mess up, I'm literally burning the money I've spent on this phone. So, fingers crossed, google acknowledge and fix it in the future. If not, then at least I can still use my phone (if I need to restart, just turn on airplane mode). It's just annoying that such a fundamental bug that causes this kind of OS error happens at Google. Had I known that, I could've applied for a software engineer role there. Probably I'll fix it myself. XD
imivantj said:
I haven't tried restarting with my Internet turned on again. I'll just wait until January or February update by Google and see how it goes. I don't want to do any tinkering with safe mode or flashing of builds because my device is an import set and if I mess up, I'm literally burning the money I've spent on this phone. So, fingers crossed, google acknowledge and fix it in the future. If not, then at least I can still use my phone (if I need to restart, just turn on airplane mode). It's just annoying that such a fundamental bug that causes this kind of OS error happens at Google. Had I known that, I could've applied for a software engineer role there. Probably I'll fix it myself. XD
Click to expand...
Click to collapse
there's a known fix for this. restart in safe mode, enable wifi and update your play services apps (long press on play store icon, my apps, update all). every user I've seen has pretty much fixed it doing this. its an issue with Bluetooth actually.
Alekos said:
there's a known fix for this. restart in safe mode, enable wifi and update your play services apps (long press on play store icon, my apps, update all). every user I've seen has pretty much fixed it doing this. its an issue with Bluetooth actually.
Click to expand...
Click to collapse
Hi, it doesn't work. My apps are all updated. And based on my personal testing, it's not the bluetooth. It's the wifi/mobile network issue. Because when I tested it, my bluetooth was already off. It's the internet (either wifi/mobile network that's causing the restart and crash). I appreciate your help though :'). I'm just always unlucky when it comes to buying hardware. All kinds of hardware I bought always met with issues. I really put such high bar for Google. But unfortunately, it's really a shame and disappointing that such a giant company fails miserably in this kind of thing.
Were you rooted and manually flashed the update? I know of a few things that could cause a similar issue if the update was done manually over fastboot.
NippleSauce said:
Were you rooted and manually flashed the update? I know of a few things that could cause a similar issue if the update was done manually over fastboot.
Click to expand...
Click to collapse
Absolutely not. I don't do such things to an expensive phone
imivantj said:
Absolutely not. I don't do such things to an expensive phone
Click to expand...
Click to collapse
Ahh, gotcha. It's not too risky to do - but is if you know what you're doing / aren't willing to learn before doing it.
Regardless, good luck figuring this out (and Happy Holidays)!
after getting board and flashing stock global and like a dope I lock the bootloader so it would be certified at the playstore , now wanting to unlock again , the bootloader they never send verification code , I've
UPDATE did finally receive code through text
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
even change the the recovery phone on the mi-account but still never get the code any tips , tricks would be great .
jefffrom said:
after getting board and flashing stock global and like a dope I lock the bootloader so it would be certified at the playstore , now wanting to unlock again , the bootloader they never send verification code , I'veView attachment 5545021 even change the the recovery phone on the mi-account but still never get the code any tips , tricks would be great .
Click to expand...
Click to collapse
Bro they won't send a verification code, it's just written there lmaoooo
For example, here the code is 5kFNX, it will different the next time but at least look before posting things lol, This is Basic.
Spuffyffet said:
Bro they won't send a verification code, it's just written there lmaoooo
For example, here the code is 5kFNX, it will different the next time but at least look before posting things lol, This is Basic.
Click to expand...
Click to collapse
then why in the beginning it says we will SEND verification code to your recovery phone number, text it to you?
jefffrom said:
then why in the beginning it says we will SEND verification code to your recovery phone number, text it to you?View attachment 5545099
Click to expand...
Click to collapse
They wont...
When when they send code via phone it does not work. Reports as wrong code , in short don't bother trying w that option
Rstment ^m^ said:
They wont...
When when they send code via phone it does not work. Reports as wrong code , in short don't bother trying w that option
Click to expand...
Click to collapse
well they did send a code via text and it worked , they don't give you a whole lot of options if you can't receive it , the problem is on their end basically they never send it tryed all day yesterday no go , today after hitting resend code it finally went through, I changed my recovery number to a google voice since the phone was in fastboot mode , from the reserch that I found they limit you to 3 send codes a day , for 24 hours how fu% up is that ? will never lock this boot loader again....
jefffrom said:
well they did send a code via text and it worked , they don't give you a whole lot of options if you can't receive it , the problem is on their end basically they never send it tryed all day yesterday no go , today after hitting resend code it finally went through, I changed my recovery number to a google voice since the phone was in fastboot mode , from the reserch that I found they limit you to 3 send codes a day , for 24 hours how fu% up is that ? will never lock this boot loader again....
Click to expand...
Click to collapse
Which rom you will try now?
jefffrom said:
well they did send a code via text and it worked , they don't give you a whole lot of options if you can't receive it , the problem is on their end basically they never send it tryed all day yesterday no go , today after hitting resend code it finally went through, I changed my recovery number to a google voice since the phone was in fastboot mode , from the reserch that I found they limit you to 3 send codes a day , for 24 hours how fu% up is that ? will never lock this boot loader again....change your recove
Click to expand...
Click to collapse
jefffrom said:
well they did send a code via text and it worked , they don't give you a whole lot of options if you can't receive it , the problem is on their end basically they never send it tryed all day yesterday no go , today after hitting resend code it finally went through, I changed my recovery number to a google voice since the phone was in fastboot mode , from the reserch that I found they limit you to 3 send codes a day , for 24 hours how fu% up is that ? will never lock this boot loader again....
Click to expand...
Click to collapse
Bro plz tell You change your recovery number to google voice what does that mean
jefffrom said:
then why in the beginning it says we will SEND verification code to your recovery phone number, text it to you?View attachment 5545099
Click to expand...
Click to collapse
I think they have a bug. I have noticed that if I do anything on a browser requiring a verification sms, it comes through immediately AFTER I do a captcha dialog. I think that dialog is missing from the unlock tool and as a result, the sms is never sent. Try it. Do anything on your mi account that requires them to verify with sms and you'll get it immediately after you do the captcha. That's the only difference I see between changing recovery email or number on the unlock tool ( never get an sms) or doing the exact same thing in the web browser on account.xiaomi.com. It's a really stupid bug.
bobcov said:
I think they have a bug. I have noticed that if I do anything on a browser requiring a verification sms, it comes through immediately AFTER I do a captcha dialog. I think that dialog is missing from the unlock tool and as a result, the sms is never sent. Try it. Do anything on your mi account that requires them to verify with sms and you'll get it immediately after you do the captcha. That's the only difference I see between changing recovery email or number on the unlock tool ( never get an sms) or doing the exact same thing in the web browser on account.xiaomi.com. It's a really stupid bug.
Click to expand...
Click to collapse
does the bug still exist now? i still can't receive a code even though i changed my recovery phone number multiple times. if there's a solution, can you explain the procedures?
This is taken from another post on this topic. You might not need a google voice number, let me know please:
I changed my registration number to a Google voice number and used version 4.5.813.51 to be able to log in to the tool. This version presented the captcha and the SMS arrived shortly afterwards. Cookies apparently preserve this across other versions. It seems to me that a captcha dialog is missing from later versions, blocking SMS send.
At this point, I closed version 4.5, used "adb reboot bootloader" command to put the phone into bootloader mode (prematurely, it turned out). I then launched Unlock version 6.5.406.31. No SMS check was required. The phone was seen and the unlock stopped because of "Couldn't verify phone," which I call Problem 3.
The rest of the post is at https://forum.xda-developers.com/t/unable-to-unlock-bootloader-resolved.4456861/page-3#post-87646843 if you run into further problems.
bobcov said:
This is taken from another post on this topic. You might not need a google voice number, let me know please:
I changed my registration number to a Google voice number and used version 4.5.813.51 to be able to log in to the tool. This version presented the captcha and the SMS arrived shortly afterwards. Cookies apparently preserve this across other versions. It seems to me that a captcha dialog is missing from later versions, blocking SMS send.
At this point, I closed version 4.5, used "adb reboot bootloader" command to put the phone into bootloader mode (prematurely, it turned out). I then launched Unlock version 6.5.406.31. No SMS check was required. The phone was seen and the unlock stopped because of "Couldn't verify phone," which I call Problem 3.
The rest of the post is at https://forum.xda-developers.com/t/unable-to-unlock-bootloader-resolved.4456861/page-3#post-87646843 if you run into further problems.
Click to expand...
Click to collapse
i've also seen you on xiaomi.eu forum, tysm!!!!
nhm2606 said:
i've also seen you on xiaomi.eu forum, tysm!!!!
Click to expand...
Click to collapse
Did it work? I rarely post except when I find something that might save others a lot of time. I was at it for about two weeks on and off.
bobcov said:
Did it work? I rarely post except when I find something that might save others a lot of time. I was at it for about two weeks on and off.
Click to expand...
Click to collapse
i changed my phone number to a textplus (google voice alternative) number through the recovery phone reset form. the SMS did work flawlessly and now i have to wait 9 days for bootloader unlocking. thank you for your asking.
After 2 days back and forth looking for solution to acces using the older and latest mi unlock pc version. I manage to get the sms, it was my local number that was deactivate, also the help section say it I need credit in my number for it to work. The unlock tool is super buggy, at some point i though it was blank since i could not scroll or fullscreen it but arrow button could show the lower section, and i could not change country prefix number on pc when trying to add number. The QR login from phone to pc is work much better. Hope that help.
There is a catch with this tool , when you request to receive a text on the first screen it sends you to the second screen, there you have to enter the captcha code then click on the CTA Button, if you validate that captcha, you will instantly receive the SMS and it will send you back to first screen where you have to actually enter the code and click on CTA. Done
0xHelium said:
There is a catch with this tool , when you request to receive a text on the first screen it sends you to the second screen, there you have to enter the captcha code then click on the CTA Button, if you validate that captcha, you will instantly receive the SMS and it will send you back to first screen where you have to actually enter the code and click on CTA. Done
Click to expand...
Click to collapse
You should have a metal man you saved my ass I thought the phone was never going to be workable. The captcha is so hard to see it never dawned on me. Thank you