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
Related
OK I have a Sprint GNex that is rooted with unlocked boot loader. It is on stock ICS 4.0.4. I can not send or receive regular text messages. Picture messages work fine. I tryed deleting the moms.apk with sysappremover and installing a new moms.API file I found on this site but it will not install. Also 3rd party messaging apps do not work . I am guessing it is some setting but I can not find any advanced text settings. Is my only fix to use Odin to completely reset the phone? Thanks in advance for any help
you need to correct your SMSC settings.
http://wiki.cyanogenmod.com/wiki/SMSC_Updates
use this guide and it should help you out.
When I follow those directions it gives me a refresh error and a update error. Any other ideas?
call sprint and ask them directly for the correct information.
kal7467 said:
When I follow those directions it gives me a refresh error and a update error. Any other ideas?
Click to expand...
Click to collapse
You have to click only update...So you used this and gave you an error?
07917140140000F0
What info should I ask them for? That number on the site you linked seems to be correct from various sources
yes sir used that exact number. when i enter it it says update error in the field and erases my number
i guess going back to stock will be my next move
Well back at stock with locked boot loader and still getting refresh error and update error in the smsc screen sprint started a repair ticket on it and are supposed to call me in 24-48 hrs...people who have gsm gnex say that putting the sim card in another phone fixes it but since we have no sim I am not sure what to do
Still in same spot. Started sprint fix ticket and they keep moving fix day back saying they are waiting on a part. Sounds like BS to me but maybe this has happiness to one of you also...anyone?
Please note, this is not compatible with the JB OTA - use the app in the Play store instead for now. Thanks!
Howdy all! So, it's time for me to dig out my release thread template... you know what that means?
The LG Optimus G is now unlocked.
Both the AT&T Version and the Sprint Version have been successfully unlocked with this method.
(To answer your question, if you're wondering, we're going to work on the Canadian version next, then the Korean version)
First off, I'd like to write a few words to LG:
Dear LG, a product will rise and fall on the shoulders of it's community.
If you lock a device, and shut out your community, you lose the backing of a very vocal group of people. When you lose the backing of your community, they no longer recommend your product, and you lose money. HTC has discovered this recently.
Please support your development community, we understand product security plays a role here, but ensure that you cater to your community still.
The second you try to fight your development community by locking them out of your products is the second that I will cease to recommend your products.
Keep this in mind, and I assure you that you will find yourself on the top of the game.
With all of that said, let's get back to the goodies.
What is this?!
This is Project FreeGee, silly!
Have an Optimus G ? This project will allow you to unlock your bootloader, and install whatever you want.
Click to expand...
Click to collapse
How does this work?
For the moment, that is a trade secret. Suffice it to say that we put some ones and zeros in the right places, and good things happen.
This is also my opportunity to say do not allow any OTAs to install without asking if they are compatible. LG could possibly patch this in such a manner that makes it rather hard to ever exploit it again.
Click to expand...
Click to collapse
I'm a skeptic. I demand proof!
Alrighty, here it is:
Once again, taken with my HTC Vivid, that would rather mute me than let me speak.
Damn "nose elimination"! I am not noise, and I will not be silenced! (mmhmhmhpmhmp!!)
Click to expand...
Click to collapse
Okay, I'm game. Where do I get it?
Version 0.3 has a confirmed bug-- camera app crashes phone after a few seconds!
If you have 0.3 installed, simply download this, extract the .zip, and extract the .tar file. Inside the freegee-working directory, you'll find boot-att-freegee.img .
Boot your phone to fastboot, then fastboot flash boot /path/to/boot-att-freegee.img
I will release a quick fix .zip for flashing in CWM tomorrow.
Current Version: 0.5
Changelog:
New in v0.5 Removed LG Security check. You are now free to remove any and all apps.
http://downloads.codefi.re/thecubed/lgoptimusg/sprint/freegee/FreeGee-0.5_Sprint.zip
Currently, the download is Windows-only. I will make a OSX/Linux/Windows version soon!
Click to expand...
Click to collapse
FAQ
Can I flash an OTA after installing this?
No. Flashing an OTA could contain a new bootloader, and it would replace the one we have put on your device. If you flash the new OTA, and it replaces the bootloader but not the boot.img, you could be left in a situation where you could not boot the phone due to a security error. Once you're in that position, the only thing you can do is LGNPST back to stock-- and even then, it is possible that an OTA could enable an anti-rollback feature which would disable LGNPST.
Does this mean I can flash custom ROMs now?
Yes. However, the custom ROM must be made for your device. We're working on a decrapified stock ROM, and AOSP ROMs as well. Be patient for those to come.
Can I install a Nexus 4 system image and boot.img and have it work?
We've tested that, and the answer is no, not yet. Some work needs to be done, but once we figure it out, we'll have a quick and easy AOSP ROM.
Does this mean that we can use the Nexus 4 sources (kernel and android) ?
Short answer: Yes.
This phone is essentially a Nexus 4, with minor differences in GPIOs, memory address space, and partition table layouts.
Kernel source is iffy, since we've got Eco mode and a few other things that actually make me like the Optimus kernel more than the Nexus kernel.
However, this discussion is best suited for a new post.
How can I uninstall this?
I'm working on an easy-uninstall for this as well. Stay tuned for the links...
Click to expand...
Click to collapse
Important Information
To enter bootloader, hold volume UP and power.
Upon entering the bootloader, you will notice that there is no 'menu' to enter fastboot or recovery. Unfortunately, since the stars didn't align properly, we were unable to tell the new bootloader where to load the images that contain the menu from.
In light of that, you'll have to navigate the menu blind. Use the volume keys to change selection, and the power key to select.
The choices are (in order of pressing volume down):
Start - boot the phone normally [already selected]
Restart Bootloader - reboot into the bootloader
Recovery Mode - enter recovery (CWM)
Power Off - powers the phone off
So, to get to Recovery, you would press volume down twice then power.
If you have trouble with this, watch my video below for a demonstration.
Click to expand...
Click to collapse
Instructions!
Please note: this requires root before you can install this! If you haven't rooted your phone yet, now is the time to do so.
Also, ensure that you have ADB drivers installed. This WILL NOT WORK without them.
Before we begin: please make sure you have USB Debugging turned on, your phone is in "Charge Only" mode, and your phone's screen is on and unlocked.
This will allow you to see the root access prompt if your phone asks for it.
Download the .zip from this post
Extract it somewhere on your hard drive
Ensure your screen is on and unlocked
Run the "freegee.bat" script, and follow the instructions.
Do not run this as administrator! the install will fail if you do so.
Once the unlock is complete, check to make sure you have a "backups" folder now in the folder where you put FreeGee. If not, DO NOT REBOOT your phone.
Even a failed unlock will still show the 'congratulations you're unlocked!' text, read the output to see if you have errors!
You should not see any "adb.exe not found" errors, or "tar: invalid magic" errors. Those would be errors in the script.
An error which you can ignore is "No space left on device" after it says erasing old recovery and boot. That's just a side effect of how we clear the old images out.
Click to expand...
Click to collapse
Contact Information
"Mister Cubed, how do I talk to you?"
That's easy! Hop on IRC and join me on Freenode in #lg-optimus-g . I'm in there as IOMonster (or IOMonster_desk, or IOMonster_work, depending on where I am)
There's also a lot of other cool people in there too!
When you hop in IRC, if you've got a question, just ask it. Don't say "halp! i does brick'd my phone, and i dunno wat to does?!!", but rather "can anyone help? my phone is stuck in fastboot mode, and I can't get out of it. I flashed <xyz> and now I'm stuck here."
Asking your full question (even though it might be a long message) helps us figure out the best way to assist you, without us having to lead the conversation and ask all the questions for you.
Also, on IRC (for those of you who have never used IRC) if you say someone's name, it will 'ping' (also called 'highlight') them. This tells us that someone is talking to us. So, if you pop in IRC and say "IOMonster, it worked!", I'll get a notification, and will probably say "that's awesome!" in response.
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the assistance of the following people:
Shelnutt2
g33k3r
kmdm
synergy
jcase
sextape
xboxfanj
...and the support of the entire #lg-optimus-g IRC channel
A project like this is really only a sum of it's parts, and in our case, we're over 9,000!
Please make sure to tell someone on this list that they're awesome if you see them on IRC or (*gasp!*) in real life.
Click to expand...
Click to collapse
All right, that about sums up my post. Did I forget anything? Let me know below...
Thanks to all of u guys for all your hard work!
Here is some proof, this is fully working...
{
"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"
}
Sorry for the blurry images, took these from my old OG Evo... But can say its fully unlocked!!!
Nice work thecubed, and shellnut2 on this, thanks for keeping our freedom alive!!!
Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app
Tyederian said:
Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I've already run the OTA, and had no issues unlocking, or rooting after the OTA...
I am so excited! I cannot wait to get this thing unlocked! :victory:
Sweet super excited
Awesome! Will be donating to the team on pay day thanks guys!
Sent from my PG86100 using xda premium
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Wow! Many thanks to all the devs for their hard work and to the beta testers for their willingness to let their phones be guinea pigs. Very much looking forward to this!
Sent from my LG-LS970 using Tapatalk 2
jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
$55 they charged me $99 and some tax on top of it. how did you pull that off?
Super sweet you guys are awesome!!
Christmas came early this year.
Sent from my LG-LS970 using xda app-developers app
New build is up!
Fixed a typo in my code haha
awesome job, big thanks to everyone.
And I second that $55 question.
jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
How on earth did you get it for $55?
tabormeister said:
How on earth did you get it for $55?
Click to expand...
Click to collapse
Had signed up for phone freedom to get $50 gift card back in February.
So I just ran this and had a couple little panic moment!!
1. While reading the script, SU poped up and I missed the "Grant SU" button on the phone. I still got the backup folder but nothing was in it. I then thought it worked, rebooted, and nothing.
The second time I ran this, I got to the "Grant SU" button in time and all went GREAT!!! This time I had files in the backup folder.
2. When I rebooted into recovery, I tried to make a backup. I hit the backup button and got some message that said "Can't mount backup path". So i tried the backup to internal SD and it worked.
Figured I'd write this in case anybody else had the same moment's I did.
The files on the backup folder are very differnt from what I'm used to so hopefully I did it correctly. I noticed there was an option in CWM to choose the backup format after I'd made my backup, so I'm not sure which format is correct for Restore. I guess I used the default which is .dup.
Thank you very much dev's for this!!!!!:laugh:
---------- Post added at 05:54 AM ---------- Previous post was at 05:25 AM ----------
DO NOT use the camera!!!! It'll crash your phone!!!
I read about it in the ATT section just now, but it's too late for me. So I guess we have this bug also.
OK...so not quite a crash. Held the volume down button and power together and got it to reboot.
Now we just need to have a way to recover our phones if/and/or when we do crash our phones. I know the devs are working on this, as obviously they are the bomb!!!
Tease: Two things brewing that hopefully will be up today. Both directly related to this
Shelnutt2 said:
Tease: Two things brewing that hopefully will be up today. Both directly related to this
Click to expand...
Click to collapse
I'm sure hoping you're referring to my post above. I get alittle wiggy if I don't have a way to fix my phone myself.
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?
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)!
Hello. 3 weeks ago I was testing lineage 19 and had decided to install the gapps. The problem is, when I was trying to start TWRP it did not start from the twrp logo so I tried to flash from odin TWRP 3.4.0 to "try" to fix the recovery. When the phone did not start I decided to reinstall the official rom but I only found a version that worked flashing by odin (mexican version. at&t) the phone started and I decided to wait 7 days for the oem unlock to reappear. The problem is that 8 days have passed and oem unlock is still not available and when I go back to download mode it says rmm prenormal.
Will it have to do with having used a telephony rom when installing stock? I have no idea why it does not appear (it should be clarified. I did not turn off the device or disconnect from the internet in all that time, only when it was already on the eighth day because it was already very saturated) Sorry if I'm posting this wrong, or if you misunderstand what I'm trying to say. It's my first time writing here and I don't speak enough English to write this for myself. So I'm trying to "improve" the google translation changing some words
Thank you very much for reading this post and any help is welcome.
.
right now im waiting the 7 days but its weird, i installed the stock of my country but the boot have a att logo and in my country there is no att company lol i even tried downloading from oficial samsung and same logo... hope it work without problem, so Did you fix your problem?
ShadowDeath said:
right now im waiting the 7 days but its weird, i installed the stock of my country but the boot have a att logo and in my country there is no att company lol i even tried downloading from oficial samsung and same logo... hope it work without problem, so Did you fix your problem?
Click to expand...
Click to collapse
not really. After what I have mentioned, I completely cleaned the phone many times. until a week ago I remembered that I just bought the mobile it took approximately 13 days for the oem unlock to appear. (I suppose that because it is a company it will take longer, I don't know) and a friend told me to wait approximately 300 hours (I have currently 222 hours). I feel that if it does not appear again I will be forced to buy a new phone :/
Camkdls said:
not really. After what I have mentioned, I completely cleaned the phone many times. until a week ago I remembered that I just bought the mobile it took approximately 13 days for the oem unlock to appear. (I suppose that because it is a company it will take longer, I don't know) and a friend told me to wait approximately 300 hours (I have currently 222 hours). I feel that if it does not appear again I will be forced to buy a new phone :/
Click to expand...
Click to collapse
damn that sucks and weird, everyone said they just wait 7+ days without power off the phone and worked... first time i read about waiting more time, are you sure your phone isnt power off in the waiting time?
ShadowDeath said:
damn that sucks and weird, everyone said they just wait 7+ days without power off the phone and worked... first time i read about waiting more time, are you sure your phone isnt power off in the waiting time?
Click to expand...
Click to collapse
I am pretty sure. I do not turn off the mobile at all or disconnect it from the mobile data since I cannot make calls because of the VoLTE that is not available so I always receive calls through third-party applications. It should be clarified that I do not have an automatic restart activated, I also registered the mobile in the updates. At the moment I have 250 hours, I will wait 2 days to see if my theory is true.
Camkdls said:
I am pretty sure. I do not turn off the mobile at all or disconnect it from the mobile data since I cannot make calls because of the VoLTE that is not available so I always receive calls through third-party applications. It should be clarified that I do not have an automatic restart activated, I also registered the mobile in the updates. At the moment I have 250 hours, I will wait 2 days to see if my theory is true.
Click to expand...
Click to collapse
It still appears that the phone has been on for 250 hours in the settings. so I don't think it's because of some reboot or shutdown :/
{
"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"
}
Camkdls said:
It still appears that the phone has been on for 250 hours in the settings. so I don't think it's because of some reboot or shutdown :/
View attachment 5566123
Click to expand...
Click to collapse
If you dint re lock the bootloader when you installed that rom, the bootloader is unlocked right now, but pretty sure you have the samsung rmm in prenormal and thats why to "fix" it we need to wait 7+ days of usage so you should enter in download mode and check your RMM setting again or you should try to install another rom, could be some issue with that one
ShadowDeath said:
If you dint re lock the bootloader when you installed that rom, the bootloader is unlocked right now, but pretty sure you have the samsung rmm in prenormal and thats why to "fix" it we need to wait 7+ days of usage so you should enter in download mode and check your RMM setting again or you should try to install another rom, could be some issue with that one
Click to expand...
Click to collapse
I had thought about that, but there are a lot of problems to find and download the correct version for the binary. I was still doing searches when I updated to android 8 just to install TWRP and they also match the 13 days that I had mentioned before. if it doesn't appear again I'll have to download another rom at 50kbps
When updating use odin since by chance the OTA update did not work. The same thing happened to lose the oem unlock and while I was preparing everything to install TWRP, approximately 20 days passed. but I already had the unlocking after 15 days.
Camkdls said:
I had thought about that, but there are a lot of problems to find and download the correct version for the binary. I was still doing searches when I updated to android 8 just to install TWRP and they also match the 13 days that I had mentioned before. if it doesn't appear again I'll have to download another rom at 50kbps
When updating use odin since by chance the OTA update did not work. The same thing happened to lose the oem unlock and while I was preparing everything to install TWRP, approximately 20 days passed. but I already had the unlocking after 15 days.
Click to expand...
Click to collapse
Yeah that sites with ultra low speed sucks, use Bifrost for your pc, it download the specific and latest rom of your device from the samsung servers
ShadowDeath said:
Yeah that sites with ultra low speed sucks, use Bifrost for your pc, it download the specific and latest rom of your device from the samsung servers
Click to expand...
Click to collapse
I want to thank you for the program. It worked perfectly (although I used it from android because I was too lazy to turn on the PC) Today at dawn I installed the romania version (I used that version the first time I installed TWRP) All the AT&T garbage is gone
Now I only have to wait 7 days to see if the rom had any errors (Curiously when trying to update the available time zones by restarting it never updated. I think that was the problem)
Sorry for the question. But, did the oem unlock appear to you in all this time that passed?
Since you commented approximately 9 days ago until now I thought I'd ask you if the oem unlock appeared even using a rom that had the at&t logo
Camkdls said:
I want to thank you for the program. It worked perfectly (although I used it from android because I was too lazy to turn on the PC) Today at dawn I installed the romania version (I used that version the first time I installed TWRP) All the AT&T garbage is gone
Now I only have to wait 7 days to see if the rom had any errors (Curiously when trying to update the available time zones by restarting it never updated. I think that was the problem)
Sorry for the question. But, did the oem unlock appear to you in all this time that passed?
Since you commented approximately 9 days ago until now I thought I'd ask you if the oem unlock appeared even using a rom that had the at&t logo
Click to expand...
Click to collapse
Your welcome mate right now i have 143h(my fault i restart it lol) so we will see tomorrow if the option appear, still i dont care about the OEM option because it was set ON last time because i was using LOS, but the "RMM state = Prenormal" in download mode its what is locking my phone to be available to change rom, so yeah we will see tomorrow!
Saddly dint work, gonna try installing a old version of my country code or try to get a clean version, not this weird thing with att $ht
Edit:nothing seems to work so i installed the newest update of my country and debloat the rom... it let it to my mom again and she will be using a good amount of time 4 weeks and ill check again.
Edit 2: seems we are out of options now https://forum.xda-developers.com/t/...d-expired-certificate-whats-next-lol.4403393/
Yup. that explains everything. It seems that in the end I will have to change my phone, do you think there is a way to remove the prenormal RMM? I'm not very experienced in mobile development. This really makes me cry
Camkdls said:
Yup. that explains everything. It seems that in the end I will have to change my phone, do you think there is a way to remove the prenormal RMM? I'm not very experienced in mobile development. This really makes me cry
Click to expand...
Click to collapse
There are apps for repair services (like ChimeraTool) that can unlock it. Wouldn't be free, though.
Camkdls said:
Yup. that explains everything. It seems that in the end I will have to change my phone, do you think there is a way to remove the prenormal RMM? I'm not very experienced in mobile development. This really makes me cry
Click to expand...
Click to collapse
Again im in the 7th day with 171+h and OEM is missing so pretty sure the rmm its prenormal i really dont know now, you can search the telegram group and ask its called "A5/A7 2017 ROMS" i asked for help but they just give me this, they say for them works this method and they did it recently.
ShadowDeath said:
Again im in the 7th day with 171+h and OEM is missing so pretty sure the rmm its prenormal i really dont know now, you can search the telegram group and ask its called "A5/A7 2017 ROMS" i asked for help but they just give me this, they say for them works this method and they did it recently.
View attachment 5577843
Click to expand...
Click to collapse
I wonder what is "recent" I also tried this when I had the ATT rom. it didn't work for me anyway. I would try if it works but I'm already tired of flashing stock rom every time I try
I guess I'll wait for it to just unlock or I don't know
Camkdls said:
I wonder what is "recent" I also tried this when I had the ATT rom. it didn't work for me anyway. I would try if it works but I'm already tired of flashing stock rom every time I try
I guess I'll wait for it to just unlock or I don't know
Click to expand...
Click to collapse
Yeah forget about it, I tried today all the tricks again many times and nothing, I'm gonna try a month without power off the phone but right now my hopes are lost.