Hey people,
This is my first post here, so excuse me if I'm posting in the wrong section. Now about the issue - it seems I have fallen into a soft brick boot loop, which happened after upgrading my stock Xiaomi 9T to MIUI 12. There are several factors to this problem, so bear with me.
Phone wasn't modified, ROM wasn't tinkered with
Phone can be turned on as usually, however after displaying Mi logo it shuts down
Fastboot is available
Recovery mode is available
Wiping data with recovery mode stops after 3% and fixes nothing
Bootloader is locked
Developer options are disabled
And here is the worst part:
I can't flash any recovery image (like TWRP) because my bootloader is locked -> I can't unlock my bootloader because developer options are turned off -> I can't turn on developer options because ADB requires root to do so -> I can't operate as root because I can't flash any recovery image
See what I mean? It's also worth mentioning that most of the adb/fastboot commands return errors because of the OEM lock. So I guess my question is "do I go straight to a local Mi Center and ask for help or is it possible to salvage it manually at home?"
@jebacmarcina
Accessing Android's Developer options doesn't require Android got rooted
You must NOT flash a Custom Recovery , you simply boot into it
Phone's Android must NOT be rooted in order to modify / replace its ROM
@jwoegerbauer
When setting Developer Options through ADB I get "Error: closed"
Still can't do that because the device is locked
Maybe I'm misunderstanding things, but if so, could you post a tutorial here or redirect me to one?
@jebacmarcina
As I would do it:
Open MUI12 Settings menu
Goto Additional Settings
Select Developer options
jwoegerbauer said:
@jebacmarcina
As I would do it:
Open MUI12 Settings menu
Goto Additional Settings
Select Developer options
Click to expand...
Click to collapse
At the very beginning I mentioned that I can't turn on my phone, so opening Settings is impossible
jebacmarcina said:
At the very beginning I mentioned that I can't turn on my phone, so opening Settings is impossible
Click to expand...
Click to collapse
Oops, have overseen it. Sorry for this.
My advice: Re-flash Stock ROM.
jwoegerbauer said:
Oops, have overseen it. Sorry for this.
My advice: Re-flash Stock ROM.
Click to expand...
Click to collapse
Tried that too, can't be done when bootloader is locked :/
jebacmarcina said:
Tried that too, can't be done when bootloader is locked :/
Click to expand...
Click to collapse
AFAIK re-flashing phone's Stock ROM ( what in contrast to Custom ROM is digitally signed by OEM/Carrier ) by means of phone's Stock Recovery doesn't require phone's boot-loader is unlocked: a locked boot-loader always loads Stock ROM.
jwoegerbauer said:
AFAIK re-flashing phone's Stock ROM ( what in contrast to Custom ROM is digitally signed by OEM/Carrier ) by means of phone's Stock Recovery doesn't require phone's boot-loader is unlocked: a locked boot-loader always loads Stock ROM.
Click to expand...
Click to collapse
My thoughts exactly; however, when I tried doing that I still got the error "flashing is forbidden in a Locked State" so I decided to send the phone back to customer service. Still, thanks for your help and time.
Thread can be closed.
Related
Hey guys, Kyuubi10 here again.
Recently I had an issue with my nexus 9, which is becoming increasingly common.
Where one can permanently soft-brick their nexus, for lack of ticking the "Enable OEM unlock" button, then bootlooping their device while locking their bootloader, thus making it impossible to reflash a system image through fastboot.
If you're lucky enough to still be able to access your custom recovery your device is still salvageable, but if as me you were performing a factory reimage when you locked your bootloader chances are that you have gone back to stock recovery, and only after realised that your OS was bootlooping.
From reading about it, I found out that it was virtually unrecoverable, unless you managed to keep your custom recovery, by either flashing a new system or if your recovery refuses to flash new system you can use this: http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539.
But in all of these cases you still need a custom recovery.
At the end most people gave up and either bought another device or used their warranty to replace their device (Which I am trying to attempt, if my warranty isn't completely voided.)
So, finally reaching the important point of this thread, I have had a couple ideas which could work to solve this issue but since I don't have enough knowledge I am unable to actually test the idea.
For the device to recognize the lock status of the device even without an OS present means that there must be a flag the bootloader reads. By reading further I found this. http://newandroidbook.com/Articles/Nexus9.html
This basecally explains that Nexus 9 has a partition called PST (Persist) whose only job is to provide the value of this flag. I was wondering whether it is possible by using Linux could get a more direct access to the partition and change its binary value to enable the "enable OEM unlock" variable (Described by fastboot as "Ability is 0").
I had this idea because one day when I bootlooped another device and ADB on windows failed to recognize the device I booted linux and used ADB from there. And the phone was reconized.
This works because Linux can view partitions with different filesystems, where as windowns can only see partitions which have been formatted into "Windows" partitions (e.g. FAT32, NTFS).
So in theory using a Linux OS to access the different partitions in Android should show up much more information, and give you better access. But apart from this I don't know much more. I will be testing this theory out in more detail. But I am challenging the more experienced contributors out there to help out in overcoming this issue!
Please, this is a real issue which is limiting newer nexus devices. If anyone has any new ideas please share by commenting, and lets help each other out to find a solution to this problem.
..
cam30era said:
@Kyuubi10
Have you seen this thread > http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
Click to expand...
Click to collapse
Yes, in fact I have the same exact link in the OP.
But unfortunately as I have described my case is quite unique in which I don't have a custom recovery. This in turn means I have no access to ADB because no partitions are mounted.... I'm stuck with using fastboot for now.
Kyuubi10 said:
Yes, in fact I have the same exact link in the OP.
But unfortunately as I have described my case is quite unique in which I don't have a custom recovery. This in turn means I have no access to ADB because no partitions are mounted.... I'm stuck with using fastboot for now.
Click to expand...
Click to collapse
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
@Halleyscomet is very right, the N preview saved me from this problem, allowing me to enable OEM unlock and then go back to stock marshmallow.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
defmetal96 said:
@Halleyscomet is very right, the N preview saved me from this problem, allowing me to enable OEM unlock and then go back to stock marshmallow.
Click to expand...
Click to collapse
Thank you guys for your reply!!
Unfortunately as described in my signature my N9 was stolen.
But I'll change the title of this thread to [SOLVED] so that others know where to find an answer.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
angerized said:
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
Click to expand...
Click to collapse
For that a Moderator needs to be made aware ) Let's try do that!
angerized said:
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
Click to expand...
Click to collapse
Any chance you still have this file? Doesn't seem to exist on the internet anymore.Having same issue.
joeish said:
Any chance you still have this file? Doesn't seem to exist on the internet anymore.Having same issue.
Click to expand...
Click to collapse
Hello,
I don't have this specific file anymore, but I think you can sideload the latest OTA from here:
Images OTA complètes pour les appareils Nexus et Pixel | Google Play services | Google for Developers
developers.google.com
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Whoa! the unlock tool is out!
Is there any chance someone can make a root guide? I really want to buy Zenfone 3 Ultra but I wouldn't do it without root method out there. Any help is appreciated.
Were waiting on a dev to compile TWRP for us then we can get root
Trying to root ZU680KL
Hi!
I have unlocked my ZU680KL with the Asus unlock tool. Bootloader shows 'unlocked'.
Then I unpacked the stock boot.img (from WW_13.6.15.21_20161215, this what I have installed) and using Vim I set:*ro.secure=0, ro.adb.secure=0, and*ro.debuggable=1 in default.prop.
Repacked the new boot.img and flashed it with 'fastboot flash boot new-boot.img'.
'adb shell getprop' indicates that the new setting was applied.
Yet in the stock recovery mode I cannot install SuperSU-v2.79.zip and no adb devices are seen in recovery mode.
What else is needed? Do I have to edit something in the stock recovery or must wait for custom TWRP?
I was following the basic instructions found here:
https://machiry.wordpress.com/2012/10/26/getting-root-access-on-android-the-actual-way/
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
hillg001 said:
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
Click to expand...
Click to collapse
Any news?
https://forum.xda-developers.com/ze...t-zenfone-3-ultra-7-0-ww14-1010-1703-t3612108
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
when the ultra 3 first came out, many suggested waiting for a boot loader unlocker, & not updating any Android versions, because an unlock program might not work on subsequent Android versions. Is that the case? ... or does the unlocker work on the newest Android version too.
Thanks
.
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
I have just downloaded the zip, made the APK and installed it on my Zenfone 3 Ultra.
When I run the app, after clicking all the "are you sure..." acknowledgements, the app does not succeed in unlocking the bootloader. The error message indicates an unknown or perhaps network error, and suggests I "try again later..."
Running WW_14.1010.1804.75_20180612
Anybody else seeing this?
Ideas??
Reading on the ASUS blogs, they indicate it isn't supported anymore (no surprise), but shouldn't it still work??
heroxbd said:
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
Click to expand...
Click to collapse
Note the links above no longer work. Yes, you can get to the page, but the unlocker isn't there any more.
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
Does anybody know which version(s) of the stock ROM this works with? I've tried a couple, and all of them just yield the "unknown error" when running the unlocker.
If you know of a stock ROM version this works with, please post a URL for where I can find it (as it's proven really hard to find specific versions...)
Thanks in advance.
agree it no longer works. getting the unknown error...wait message that everyone else is getting. there are other XDA threads that indicate the same.
Keeping bootloader locked. Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even the SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
-
jrchester said:
Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even and SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
Click to expand...
Click to collapse
How did you do that? Can I get more details?
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hi Madlzz:
Checkout my XDA post here for more details on how I did this:
unlocking bootloader zenfone ultra
Hi all ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago, my friend wanted to see if my phone could be charged with a dash charger, where others wouldnt my battery was already low and overnight it ran out and when i...
forum.xda-developers.com
- John
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
lucy1983 said:
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
Click to expand...
Click to collapse
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
jrchester said:
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
Click to expand...
Click to collapse
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
lucy1983 said:
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
Click to expand...
Click to collapse
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
jrchester said:
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
Click to expand...
Click to collapse
You can install Magisk 24 without any problems. For me it doesn't break safetynet and play store says "certified". Even without enabling zigisk.
[SOLVED] i'm stuck in a vicious loop of flashing that i need to unlock my bootloader to flash stock rom but my phone is stuck on the page "CHECKING CONNECTION THIS MAY TAKE A WHILE" hence rendering me helpless on how to turn allow oem unlock on in dev settings on my lenovo vibe k5, I used king root to root my device but it started misbehaving with google play services so i decided to factory reset it, now i can't even get into my phone, and can't even flash stock rom any suggestions how to get out of this?
Edit: HI everyone thanks for the helpful comments after I've SOLVED this just a suggestion for whoever who stumbles on this or is in a similar situation like this , Turns out my twrp did not do the factory reset properly and hence allow oem unlock was on and hence i was able to flash a stock ROM using QFIL program in QPST description of the procedure will be and can be found on the super thread of the device please refer and flash it.
IMPORTANT: flash a stock ROM of a lower version that seems to work wonders ,I literally had to uninstall android by wiping my system folder because I didn't have a backup[NOOB MISTAKE] and i thought i'll wipe entirely and reinstall the OS and that worked out by the power of other helpful XDA threads
One question
What is bootloader status when you buy the phone from your provider??
I want to buy it but Not if at the end i will have bootloader locked and not to be able to unlock it??
Like the Sony Xperia models
All provider ones comes with bootloader locked forever so you never even get root or twrp or anything custom
Please advice me regarding bootloader locked status
Thanks
Hello. guys! My smartphone: Samsung Galaxy J4(2018), j4lte. I trying to flash custom recovery TWRP. I have already unlocked the bootloader in settings, and have been waiting over two weeks for it to physically unlock. But the bootloader itself does not want to be unlocked physically. And more, I will add. I have this thing, I press a keyboard shortcut to go into download mode, my phone turns on and immediately turns off. To enter download mode, I need to go into the built-in recovery and select "reboot to download mode" there. But then, I don't have a warning that a custom system might put the phone at risk of breaking. And there are no lines that indicate the status of the bootloader, for example, is it unlocked or not.
My version Android: 10
Download Mode: U8
I use program for flashing: Odin, current version
Damn i have the same issue with the Note8, lez hope that soemone ansers that cuz reinstalling the Stock dosent help with this when try to install TWRP
NikitaSav said:
Hello. guys! My smartphone: Samsung Galaxy J4(2018), j4lte. I trying to flash custom recovery TWRP. I have already unlocked the bootloader in settings, and have been waiting over two weeks for it to physically unlock. But the bootloader itself does not want to be unlocked physically. And more, I will add. I have this thing, I press a keyboard shortcut to go into download mode, my phone turns on and immediately turns off. To enter download mode, I need to go into the built-in recovery and select "reboot to download mode" there. But then, I don't have a warning that a custom system might put the phone at risk of breaking. And there are no lines that indicate the status of the bootloader, for example, is it unlocked or not.
My version Android: 10
Download Mode: U8
I use program for flashing: Odin, current version
Click to expand...
Click to collapse
Did you install smasung multi disabler?
DavidxxxD said:
Did you install smasung multi disabler?
Click to expand...
Click to collapse
oh no **** guess im just dumby ^_°
DavidxxxD said:
Did you install smasung multi disabler?
Click to expand...
Click to collapse
tho crap how im supposed to install it? odin dosent want it and i cant use since ivent got TWRP on it wich i can not install because it says, as u guesst: Only official binaries can be installed no matter WHAT I DO -.- hate samsung by now
NikitaSav said:
Hello. guys! My smartphone: Samsung Galaxy J4(2018), j4lte. I trying to flash custom recovery TWRP. I have already unlocked the bootloader in settings, and have been waiting over two weeks for it to physically unlock. But the bootloader itself does not want to be unlocked physically. And more, I will add. I have this thing, I press a keyboard shortcut to go into download mode, my phone turns on and immediately turns off. To enter download mode, I need to go into the built-in recovery and select "reboot to download mode" there. But then, I don't have a warning that a custom system might put the phone at risk of breaking. And there are no lines that indicate the status of the bootloader, for example, is it unlocked or not.
My version Android: 10
Download Mode: U8
I use program for flashing: Odin, current version
Click to expand...
Click to collapse
And this version of Odin? https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
joke19 said:
А эта версия Одина? https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Click to expand...
Click to collapse
I have RMM Prenormal
C7TJFVB7-CAZ said:
hate samsung by now
Click to expand...
Click to collapse
Same here, reinstalling full stock should fix it. Also try combiation firmware if that doesn't work. Does your device have a vbmeta partition?
DavidxxxD said:
Same here, reinstalling full stock should fix it. Also try combiation firmware if that doesn't work. Does your device have a vbmeta partition?
Click to expand...
Click to collapse
combination file not working on Binary 8/9 on Samsung Galaxy J4
I've had the same issue on a J330F after Android 9 update - tried to modify, got stuck in the same red text. I don't remember any info from odin mode, but It booted fine again after flashing the same version over it. Though I had to wait 24 hours before trying to modify again. Not sure what's going on in your case, but Samsung security can be real pain, that's for sure.
I wouldn't get any of their newer models to mess around with, compatibility is good and there are reliable methods, but generally everything works better on more generic Qualcomm devices. Just take a look at most MSM845 devices from around 2019 - big diffrence in terms of compatibilty, many of them are supported by newer versions of Linux than what is included with Android, some can even boot Windows 11.
DavidxxxD said:
I've had the same issue on a J330F after Android 9 update - tried to modify, got stuck in the same red text. I don't remember any info from odin mode, but It booted fine again after flashing the same version over it. Though I had to wait 24 hours before trying to modify again. Not sure what's going on in your case, but Samsung security can be real pain, that's for sure.
I wouldn't get any of their newer models to mess around with, compatibility is good and there are reliable methods, but generally everything works better on more generic Qualcomm devices. Just take a look at most MSM845 devices from around 2019 - big diffrence in terms of compatibilty, many of them are supported by newer versions of Linux than what is included with Android, some can even boot Windows 11.
Click to expand...
Click to collapse
I have Android 10
I try all, that i can to try
Same problem
After unlocking your bootloader, you have to allow your device to boot again:
Helix-one said:
I AM NOT RESPONSIBLE FOR ANY DAMAGES DONE BY YOUR MISHAPS
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some cirumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Voila! Your bootloader now accepts unofficial images in download mode.
Click to expand...
Click to collapse
After flashing TWRP, you may need to wipe data and flash Multidisabler
V0latyle said:
After unlocking your bootloader, you have to allow your device to boot again:
After flashing TWRP, you may need to wipe data and flash Multidisabler
Click to expand...
Click to collapse
I cant even flash TWRP
Kgstate said:
I cant even flash TWRP
Click to expand...
Click to collapse
When you're in Download Mode, look for something that says "KG: Checking". If this says "Prenormal" you won't be able to flash custom binaries, and need to do as I described - boot the device, connect to the Internet, wait for the OEM unlocking toggle to become visible again.
V0latyle said:
When you're in Download Mode, look for something that says "KG: Checking". If this says "Prenormal" you won't be able to flash custom binaries, and need to do as I described - boot the device, connect to the Internet, wait for the OEM unlocking toggle to become visible again.
Click to expand...
Click to collapse
Editing date to make it 7 days later and Connecting the internet just worked, thank you for your help!
Omarqaissy said:
I have a problem with my device, Google Pixel 7 Pro, after rooting and deleting it, after rebooting it did not work. Code 3 error appears and the phone does not work. Is there a solution for it?
Click to expand...
Click to collapse
Omarqaissy said:
لا يمكنني تشغيل الهاتف لتشغيل وضع المطور وفتح قفل المصنع. تتطلب المشكلة عند تثبيته فتح قفل المصنع
هل هناك طريقة للاتصال بك لإيجاد حل للمشكلة؟
Mod translation:
I can't boot the phone to turn on developer mode and factory unlock. The problem when installing it requires a factory unlock
Is there a way to contact you to find a solution to the problem?
Click to expand...
Click to collapse
My confusion starts with your statement "after rooting and deleting it".
What did you delete?
The gist of your posts seems to be: you did not unlock your bootloader; you tried to use PixelFlasher, but you gave it the wrong file -- you gave it a downloaded OTA file, which is an incremental update, but you were supposed to give it a full system file; somehow this resulted in you damaging your installation.
It is likely that you have already lost all data. If you have not already lost all data, it is likely that anything you do will destroy all data. If it is important to you to recover your data, find an official Google repair shop -- I do not know if your data can be recovered, but I expect an official Google repair shop to have the best chance.
If you accept the total loss of your data, and you want to try to fix the phone yourself, I think your best bet is to find a complete ROM image. It must be an official Google image. With the bootloader still locked, you will not be able to install any image that is not official.
There may be an easy way to install a ROM image. It would start with you booting your phone to recovery mode. This is not the same as booting Android, which you do not seem to be able to do. Try googling "pixel recovery mode".
I do not know if @badabing2003's PixelFlasher will help you. I think before you can use PixelFlasher you need to make sure you have properly installed "adb" and "fastboot". Start by reading instructions for PixelFlasher. Good luck.
J.Michael said:
My confusion starts with your statement "after rooting and deleting it".
What did you delete?
Click to expand...
Click to collapse
I'm confused as well.
One moment it was rooted and another it can't even OEM unlock?
J.Michael said:
The gist of your posts seems to be: you did not unlock your bootloader; you tried to use PixelFlasher, but you gave it the wrong file -- you gave it a downloaded OTA file, which is an incremental update, but you were supposed to give it a full system file; somehow this resulted in you damaging your installation.
Click to expand...
Click to collapse
He couldn't have done this in PF, PF will refuse to work with OTA image to do a full factory flashing.
J.Michael said:
There may be an easy way to install a ROM image. It would start with you booting your phone to recovery mode. This is not the same as booting Android, which you do not seem to be able to do. Try googling "pixel recovery mode".
I do not know if @badabing2003's PixelFlasher will help you. I think before you can use PixelFlasher you need to make sure you have properly installed "adb" and "fastboot". Start by reading instructions for PixelFlasher. Good luck.
Click to expand...
Click to collapse
Yes this is possible in PF,
Custom Flash
Select OTA image
Select SIDELOAD option
Flash
Root is not needed.
But if the device does not respond to adb commands because the author said he can't set the developer options and enable ADB, then it won't work.
badabing2003 said:
I'm confused as well.
One moment it was rooted and another it can't even OEM unlock?
He couldn't have done this in PF, PF will refuse to work with OTA image to do a full factory flashing.
Yes this is possible in PF,
Custom Flash
Select OTA image
Select SIDELOAD option
Flash
Root is not needed.
But if the device does not respond to adb commands because the author said he can't set the developer options and enable ADB, then it won't work.
Click to expand...
Click to collapse
I'm guessing "rooting" really meant "did something in an attempt to root".
I think the first question to answer is, how did he manage to damage his installed system when he hasn't unlocked the bootloader?
Although, if the words mean what they should, it *should* be possible to flash a random image with a locked bootloader, it just shouldn't be possible to boot it. But that is not the way the words seem to work with most of the people who post.