[SOS!!!] My Pixel doesn't boot!!! - Google Pixel Questions & Answers

Hi there:
I’ve got a second-hand Pixel 1 last week, I unlocked, installed TWRP and rooted yesterday, but I unrooted today because some reasons.
I did a wrong decision, I erased the phone by System Settings, and locked it.
After I locked it, when I boot it, it only have Google logo flash for about 0.1second then gone. I tried to flash the factory images from Google, but it requires unlock to flash it.
I even can’t unlock it now because I can’t get into the System to turn on “Allow unlock OEM loader”, so it got failed. I used fastboot OEM unlock and fast flashing unlock, they both doesn’t work.
I don’t really want to send the phone back to Google US because I doesn’t live in America, so it’s not really easy and really expensive to send it, and I also really need this phone because the battery of my old phone is almost dead. And the Google Support Team in my country/region says that I can’t send to the repair center locally because they only accept Pixel 3/3XL/3a/3aXL/4/4XL
Thanks the suggestions from you guys!

I have a similar issue.
I unlocked the bootloader via ADB but I couldn't even get a copy of TWRP to work at all. The phone also eventually stopped working on the stock install too but taking the option it presented of doing a full wipe and reset fixed at least THAT part.
Still can't get TWRP or Lineage up on it :/

Reboot to fastboot mode and flash stock recovery image (according to your os version).

Related

Google repair shop re-locked my bootloader... wtf now?

OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.
If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.
Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N
n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.

Phone just crashed. Could it be because of an unlocked bootloader ?

I opened up the developer options on my Moto G Stylus and went under OEM Unlocking and selected the allow the bootloader to be unlocked option. That was either last week or a few weeks ago because I wanted to root it and put a custom rom on it. I didn't rooted it yet because I'm not sure what roms are good, I only had cyanogin mod roms on my other phones and I'm not sure which rom is the safest and best to use so I still use the stock rom. I turned on Pandora to play music before I went to sleep. When I woke up my phone was in some kind of recovery mode and said something like the operating system failed to boot. Two options were available, 1- to try booting again, and 2-factory reset the phone which would erase all data. I selected 1, and my phone booted up. Could this be because the bootloader is unlocked? Does having the bootloader unlocked leave it suspectable to being hacked? Could my phone have been hacked?
Switching OEM Unlocking is not enough to unlock, you then must on motorola unlock webpage paste code from your phone and, wait for unlock code in email, via fastboot with this unlock code doing finaly real umlocking...
k3dar7 said:
Switching OEM Unlocking is not enough to unlock, you then must on motorola unlock webpage paste code from your phone and, wait for unlock code in email, via fastboot with this unlock code doing finaly real umlocking...
Click to expand...
Click to collapse
Would selecting the bootloader option to be unlocked in the developer options make my phone more vulnerable to be hacked?
A few hours later my phone did the same thing and went into recovery mode saying that my phone could not load the OS and might be infected or something. I had the same options to either try to load the OS again or factory data reset the phone. How could this happen?
I factory data reset my phone this time. I just hope I don't have some kind of malware.
Mine was hacked like this. Changed stuff so it won't boot back to original. Got into system files and remote control my phone. Is there a way to get back to original without computer? It's useless now

Question Flash stock firmware and lock bootloader

HHello, I wanted to consult something before getting into a problem. I have the moto g100 with the challenge channel, since the Android 12 ota did not come out for this channel, I decided to install the Android 12 retail ota, Everything worked correctly, but now I want to install my original firmware which is RETAR and block the bootloader, so my question is the following, can I flash my original firmware and lock the bootloader?.
Yes if you flash ORGINAL ROM (Android Version) for your device you can LOCK bootloader for your device.
Lock the bootloader at your own risk, this forum has a thread full of people who have bricked their device after relocking.
Phone wouldn't boot into the system after bootloader locking back...
I wanted to help someone whose phone wouldn't boot into the system after bootloader locking back, phone hangs on a red warning. And in the process of experimenting myself got confused and got into the same situation. Unlocking the bootloader...
forum.xda-developers.com
The stock roms found on lolinet won't boot after relocking and you'll loose the ability to flash anything else. YOU HAVE BEEN WARNED! Also, you can't downgrade the bootloader. What this means is that if you flash older Android 11 stock image it may result in bootloop.
I have a G8 doha that was hard bricked a few years ago.. It did not show up in device manger at all, no matter how i tried. Not even the Qualcomm mode. This did happen after locking bootloader or change slot A/B. (Don't remember, sorry). The phone was totally dead, so it was just "archieved for later use".. Then one month ago i found a description on how to wake it up to qualcomm mode by shorting two points on pcb. I tried, and it did work. Phone showed up in device manager, and i flashed blankflash. After that i flashed stock rom. Phone is now working again. I had to do several tries to get it up running. The description on how to do it was not accurate, but i found a sequence to start it. Unfortunately i don't remember exactly. It is something with pushing/holding a button when connecting USB or shorting points on pcb.. Youtube link show how to do it..
GT
Somebody try relock bootloader on g100 and have succes ? I back to stock rom with Rescue and Smart Assistant tools but I am slightly afraid that the phone will not get up after relock the bootloader. :|
sp6ina said:
Somebody try relock bootloader on g100 and have succes ? I back to stock rom with Rescue and Smart Assistant tools but I am slightly afraid that the phone will not get up after relock the bootloader. :|
Click to expand...
Click to collapse
Yes I relock my bootloader on the Moto g100 the North American version. Right after I did it I tried to set up my phone and it wanted my last four digit Google pin code and if you didn't do it fast enough it kept rebooting so for a half hour I tried everything under the sun Google kept asking me I want to try another way. But I have two step verification on my Google account so it couldn't send me the code over my telephone number so after a couple tries using the recover my account option underneath which asked you like personal information like your name and everything it finally gave me three options of three different Google emails I have. I got my unlock code and unlock the bootloader without using a PC or a computer. I used bugjaeger. The premium app is well worth the $10 it works super easy and super efficient
sp6ina said:
Somebody try relock bootloader on g100 and have succes ? I back to stock rom with Rescue and Smart Assistant tools but I am slightly afraid that the phone will not get up after relock the bootloader. :|
Click to expand...
Click to collapse
Yes I relock my bootloader on the Moto g100 the North American version. Right after I did it I tried to set up my phone and it wanted my last four digit Google pin code and if you didn't do it fast enough it kept rebooting so for a half hour I tried everything under the sun Google kept asking me I want to try another way. But I have two step verification on my Google account so it couldn't send me the code over my telephone number so after a couple tries using the recover my account option underneath which asked you like personal information like your name and everything it finally gave me three options of three different Google emails I have. I got my unlock code and unlock the bootloader without using a PC or a computer. I used bugjaeger. The premium app is well worth the $10 it works super easy
sp6ina said:
Somebody try relock bootloader on g100 and have succes ? I back to stock rom with Rescue and Smart Assistant tools but I am slightly afraid that the phone will not get up after relock the bootloader. :|
Click to expand...
Click to collapse
Yes I relock my bootloader on the Moto g100 the North American version. Right after I did it I tried to set up my phone and it wanted my last four digit Google pin code and if you didn't do it fast enough it kept rebooting so for a half hour I tried everything under the sun Google kept asking me I want to try another way. But I have two step verification on my Google account so it couldn't send me the code over my telephone number so after a couple tries using the recover my account option underneath which asked you like personal information like your name and everything it finally gave me three options of three different Google emails I have. I got my unlock code and unlock the bootloader without using a PC or a computer. I used bugjaeger. The premium app is well worth the $10 it works super easy

[Help] Bricked phone stuck in bootloop

I have an old Asus Zenfone 4 that randomly got stuck in a boot loop while it was recharging, and now I don't know how to fix it, or even if it is possible to fix. The only thing that still works is fastboot mode (recovery mode doesn't work either, so SD cards are out of question).
I have tried a number of things to factory reset the phone and see if it changes anything, but it seems impossible to unlock its partitions for flashing: commands such as fastboot flashing unlock, fastboot oem asus-go or anything similar just throw errors saying that the command doesn't exist, or if it does, that I don't have permission to run them. For this same reason, I couldn't use things such as TWRP as I can't flash any of the partitions on my phone. Additionally, I have tried to enable adb through fastboot oem, but even though the command is successful, whenever I get the system info, it says that adb debugging is still off.
Does anyone know a way to either unlock this device or factory reset it without unlocking?
Another old-ish device killed by the silent OTA update of the OEM!
The deadly mistake of connecting an old-ish device to OEM servers for fresh install.
Check with unauthorized service centers who have <Miracle Box> if they can flash with fastboot. Or authorized service centers might charge but they could revive the device.
OldNoobOne said:
Check with unauthorized service centers who have <Miracle Box> if they can flash with fastboot. Or authorized service centers might charge but they could revive the device.
Click to expand...
Click to collapse
By what you are saying... Is it actually impossible for me to unlock the bootloader? I have no problem with service centers, but it would be much better and quicker if there was was a way for me to unlock it.
rafk12 said:
By what you are saying... Is it actually impossible for me to unlock the bootloader? I have no problem with service centers, but it would be much better and quicker if there was was a way for me to unlock it.
Click to expand...
Click to collapse
I threw away two old chaina phones just because I made the mistake of reflashing the original OS and tried to update from OEM servers..BOOM! Dead Phone!
The moment OEM servers detect an old device connected to their servers for an update, they kill the device so that new devices can be sold in the market, why would this happen to a device which was working perfectly under a Custom ROM before? I dont update the device from OEM channelsbecause OEM might try to kill the device after warranty period, instead I update through the Custom ROM channel.
Maybe some chip got fried while charging the device, among the asian brands shamshung & WonPlus have durable components but other asian brands maximum 4 years before the components like display etc. or even the chipset components begin to fail. Or it could be the OEM update thing too

(Guide) how to update Huawei p9 EVA-AL10 from emui 4.1 to emui 5 (Android 6 to Android 7)(also works for other models)

After further testing (well actually I mean bricking my device a few times) it turned out that rebranding is not needed for the update from mm to nougat, although your device will boot into a "test" system instead (This is likely due to the vendor information being mismatched). Your p9 would still work with HWOTA7.
The original post has not been changed.
I got hold of an EVA-AL10 model from China. However it was still stuck on emui 4.1 Android 6.
Spoiler
After some research, I found out that Chinese internet was ridiculously unreliable and riddled with useless information, and the fact that most Chinese are tech-illiterate does not help either. Then I turned to good old XDA and found out a few (pretty obsolete posts) that had similar problems and got them solved. However, they all (unsurprisingly) involved the European model (EVA-L0X), which had different firmware.
I then got in contact with a former Chinese colleague. With his help, I managed to send an email to Huawei China and get a representative. After giving him his phone number and all information in the about section of the phone (IMEI and stuff) they took an entire day only to phone him back saying he needs to go to a repair shop. They told him that the oldest version of EMUI available for update was for emui 8 (Android 8) so that was a dead end.
After more searching, I stumbled across a thread about rebranding an European model into the one I got to get to, ironically, emui 8.
Spoiler
According to a Chinese nationalist blogger, it turns out that Huawei severely displeased our international community due to halting the provision of bootloader unlock codes, and they dicided to get us back by not updating us to emui 8. Although there might be more reasons than that, the fact is clear that they had to change their model.
Luckily, XDA is the perfect platform to find help.
Spoiler
Although the in-house search engine is relatively good at dealing with the Chinese e-thefts which take the hard work of this community and sell it shamelessly in China,
a fair amount of time was taken to Google search, however it was definitely worth the effort. Soon, I drew out a simple flowchart to update my p9:
1. Unlock bootloader
2. Rebrand the phone to European model
3. Update to Android 7
4. Rebrand back
5. update to Android 8
(6. Do cool stuff)
Unlocking the bootloader is now a hard part for some. (make sure you have backed up your data on the phone because it will do a factory reset)
Spoiler
While unlocking services here are mostly genuine, it is 75% scam in China. My friend maaged to get my bootloader unlocked from a (crazy) shopping site in China named Taobao, which is well-known for selling fake sneakers and even Uranium. It only costed me two dollars.
Make sure to keep the unlock code. You need it later. If you forgot your unlock code but have it unlocked, no worriess. You can root your phone (I used good old supersu) follow this guide (the commands are the important part, I personally have not verified this method though)
You can also try this tool:
Huawei Nova 2 Plus Bootloader Unlock (Solution)
Hello Developers! I have found an easy way to unlock the bootloader of our Huawei Nova 2 Plus. No need to use Testpoint or pay for software to unlock. it is an Python Script which would brute force the code through the IMEI number you have...
forum.xda-developers.com
However it was intended for another device so your luck may vary.
After that, I used SRKtool to rebrand the phone, although the software of the phone itself has not changed. Keep in mind after the rebrand not to reboot into the system, as it will cause an error. (see below post) If you do manage to get into the system unfortunately, it will ask you for your password (bootloader unlock code) Do not enter the code, shut down your phone and get into fastboot by holding down power and volume down WHILE cable is attached to computer.
After trying hard to get into TWRP, I used this guide to boot into it (turns out I was not quick enough)
I then used this file to update it to the European android 7, which worked perfectly. You do need to enter the unlock code again though, and you need an SDcard or an USB disk that supports OTG(so the device can recognise it in twrp).
After that, you can follow this guide to get it to Android 7 Chinese version(399). I got my friend to set up a vpn connecting to China, where the Chinese system recognized that it could update to android 8. If yours does not, follow the guide to update it to android 8. It already contains the firmware, so do not download other firmware (unless you prefer). If you already got the firmware, use the androidfilehost link he provided and find in the older versions V1.1, which did not have the firmware to save time (and possibly bandwidth)
You will have your bootloader locked at this stage. If you want to stay on the Chinese firmware (Which has a lot of bloatware and needs you to manually sideload playstore apk) do not unlock it. If you do want to go further and install a custom treble GSI, go ahead and unlock the bootloader, and follow the instructions,
Error after force rebranding location with SRKtool:
After using SRKtool to rebrand, your system boot warning will turn from unlocked to unverified (text color orange to red)
If you continue to boot, it will go to a screen where you have to enter a password (the bootloader unlock code) you should not enter the code.
If you still proceed to enter the code, you will be "greeted" with a message telling you that the data on your phone is corrupt and you have to factory reset. after you boot into the OS, you will see this "mix" of the classic nexus 2012 style wallpaper with some android app icons (such as settings) in the aosp style, with everything else that are Huawei-branded seen in 2012-style icons. This has to do with a theme engine bug.
In the about page you might also notice that the system version has been slightly changed. the "al10" part has been deleted but the c00 still remains. The page where the CE and FCC stuff are displayed (forgot precise wording) now lists the phone as "eva-l09"
Go into settings and developer options as usual. You should now see that there is an oem unlock opion that has been toggled off. turn it on.
Reboot into fastboot again. You would see that most commands you would usually use such as flash recovery and erase would not work anymore(returns command not allowed) This has to do with the bootloader locked although it technically unlocked. Unlock it as you would normally do. If this does not work, reboot and turn off oem unlock, go to fastboot and enter the unlock command (it would obviously not work but it registers that wants to be unlocked), reboot and turn on oem unlock again and reboot into fastboot, then you should unlock the bootloader and flash recovery again.

Categories

Resources