Edited; flashed pie without critical_unlock post bootloader unlock. Caused a no touch condition until I critical unlocked and reflashed. Apparently it's required even if you plan on relocking phone post flash. Lesson learned.
Related
I'm not sure what is up, this isn't a new thing, but people keep coming to me (1-2 a day) with this issue.
If your phone isn't stock, DO NOT RELOCK your bootloader. You will 'soft brick' it, and at this time there is no easy route to fixing it.
If you are on EE UK, Verizon or another carrier blocking bootloader unlocks, and you used dePixel8 to unlock it, DO NOT relock your bootloader unless you are sure you don't want it unlocked again.
Finally, dePixel8 is UNSUPPORTED. Don't come to me if you can't get it to work, don't come to me if you used it them messed up your phone by flashing something bad or whatever. Its on you.
Great announcement. With the monthly security update out today, it is recommended that you don't install the update or have automatic updates enabled.
I have just bought a "new" s5 g900f with the intention of installing a custom ROM, the phone is unlocked from the factory apparently, but it was off ebay and I can't help thinking it may be a refurbished carrier locked device previously, so it may still have a locked bootloader. So how can I tell without flashing anything if it is locked or not
Edit: unlocked! Did some more research then flashed twrp, all OK
My brother has a RETIN Athene running stock ROM with latest April patch and he's been complaining about frequent ghost touches. He'd often find his phone call, text someone at random, apps opening automatically and what not. I've suggested him to do a factory reset but I'd like to know if this can be solved without a factory reset. I had already unlocked his bootloader earlier to let him try a custom ROM as the stock was getting sluggish so if needed, a fastboot ROM can be flashed as well if it comes to that.
He recently got a QC 3.0 charger from Motorola but the problem has been going on before that (if he recalls correctly). Could this be because of the charge as I remember his G4 plus had some occasional ghost touches when his phone was new but that only happened while it was being charged.
I'm open to any advice and tips. His phone is barely usable now.
Update: I did a cache wipe from recovery a few minutes ago and noticed that his recovery was showing the the following info:
oem_locked
Software status: Official
Maybe I relocked the bootloader when flashing stock back then. Do I need to unlock bootloader again with "fastboot oem unlock"?
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
gioyocho said:
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
Click to expand...
Click to collapse
I see... I'll tell him to change the brightness to auto. Do you think upgrading to a new phone is better and the only available solution?
Also, after I flashed the fastboot ROM a while ago, he has updated to all the following OTAs without any issues, that's how he's on the April patch. No hard brick, nothing.
gioyocho said:
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
Click to expand...
Click to collapse
You can relock your bootloader. And the bricking kicks in only if you flash OTAs when rooted or on a custom recovery. Generally when you have system modifications.
corlatemanuel said:
You can relock your bootloader. And the bricking kicks in only if you flash OTAs when rooted or on a custom recovery. Generally when you have system modifications.
Click to expand...
Click to collapse
Well, no system modifications were done. That's why the OTAs were successful
I went to switch to a different carrier, and was on cricket, and also tried tmobile both wich worked fine unlocked bootloader and rooted.
I then switched to sprint, and verizon and found out both carriers the phone would not work right. The data worked but the call and texting did not.
As a side note, I was informed by someone who was on sprint, and he said that you had to get on the network unrooted and locked bootloader, once registered you could then root and get the bootloader unlocked and be just fine.
So I then proceeded to unroot the phone ie: removing everything root, and keeping twrp with an unocked bootloader only, no sign of root. I took the phone back to the stores and tried again, and the phone still had the same issue.
After finally finding a way to finally after 6mo lock the bootloader again, and was at pure stock, locked bootloader and no root.
What this tells me is that some how verizon and sprint both some how some way detect an unlocked bootloader....how? I have no clue, I've never in my 5+ years of rooting multiple phones, never ever ever seen anything like this. The only reason I know this is what it was, is from common deduction and reasoning.........unroot = still doesn't work.....locked bl = works fine with not a single issue. Keep in mind this was all with base stock rom, not a custom rom.....everything was stock, accept for the root and un;ocked bootloader part. I rooted with magisk.
Since I had a very long time and issue with locking the bootloader, (about 6mo) after trying a ton of things, without resolve, I FINALLY got the bootloader locked.
If it's going to be anything like before trying to get it locked again to work on sprint and verzion, I really do not want to bother with unlocking it to begin with. It was an utter nightmare to get locked, no matter what I tried it just would not lock for whatever reason.
So given all that, my question is, how hard or easy is it now to unlock and lock the bootloader?
Hi all. I have been searching high and low for information on this specific question:
Will activating an unlocked Pixel 3a on Verizon disable the OEM Unlock and bootloader unlock capability?
I got a Verizon variant before I realized that there was not way to unlock the bootloader. Bummer. So, I returned it for an Unlocked version from Google, which I just received tonight. I breezed through the setup (without the SIM card) and noticed that OEM Unlock was disabled stating I needed to connect to the internet. So, I enabled WiFi and the OEM Unlock was then available. It would seem that I an now able to follow the unlocking procedure.
My goal is to unlock the bootloader and root, but do I have to do it immediately? My concern is that activating the phone with my Verizon SIM could:
1) Prevent unlocking the bootloader in the future if I don't unlock it before I activate with SIM (research seems to indicate that factory resets will undo disabling OEM Unlock if this can happen if I understand correctly)
2) Re-lock an unlocked bootloader - maybe this is not even possible?
I don't want to mess this up. All the info I am finding are discussions related to trying to unlock a Verizon variant and I cannot find good info on what happens to bootloader unlocking options on unlocked phones that are activated on Verizon. The only reason I may want to delay this process is because I dont have a lot of time at the moment and would rather not rush the bootloader unlock and root process. However, my HTC 10 is in bad shape and need a phone to get through the holidays. I was hoping that I could activate it on Verizon now, use it with its locked bootloader for a few weeks, and when things cool down after the holidays, implement the bootloader unlock and root.
If that is not advisable, what about unlocking the bootloader immediately (doesn't seem too hard and I have used ADB before), and activating without root. Then root later? Any possibility of concern #2?
Can OTA's re-lock a bootloader and prevent future unlocking?
I appreciate anyone's incite, experience, or links to the needed information for clearing this up. Thanks you!
I would advise you to unlock the bootloader asap. If you wait it will be a pain later because unlocking causes loss of data. If you don't care about that, wait as long as you like.
As far as Verizon is concerned, if the phone is unlocked, I don't see how they could possibly lock the bootloader. They may restrict your services but they can't touch the lock status of a device you purchased.
Sent from my Pixel 3a using Tapatalk