Man, I've really done research until my eyes are ready to pop out lol. Can someone please help me.
I'm using this guide to try and unlock my bootloader: https://www.youtube.com/watch?v=cfpehEkhfyg
Problem is, it's for a verizon version, mine's a note 4 T-mobile sm-n910t3
I'm just a noob and never had to do this unlock bootloader crap on my note 2. I need help.
I just want to unlock the bootloader, and flash recovery, supersu, and a cool rom like res. remix or CM remix.
On the video, the part I'm stuck on is he's using a file: "samsung_unlock_n4-2" with no file extension (.xxx)
I'm assuming this is a bootloader file?? I found a bootloader for my version which is a folder with contents:
FOLDER: BL_N910T3_DOK2 CONTENTS: aboot.mbn / NON-HLOS.bin / rpn.mbn / sbl1.mbn / sdi.mbn / tz.mbn
He goes on to use a CMD and fastboot to temporarily root the phone to install TWRP recovery,
but when he pushes this command: "adb push samsung_unlock_n4-fix /data/local/tmp/"
I don't think I can do that with a folder and I don't know which file to use.
QUESTION:
-DOES ANYONE KNOW WHICH FILE I NEED
-OR-
IS THERE A BETTER WAY TO FLASH A CUSTOM KERNEL THAT UNLOCKS THE BOOTLOADER, THEN ROOT, FLASH ROM AND EVERYTHING A LOT EASIER.
Side note, I didn't know I had to unlock FRP and tried to flash recovery. I also tried CFautoroot.
Both are blocked from working so I'm just assuming the bootloader is locked, otherwise it would say "mode developer" on the stock recovery. Off topic, I started reading about CyanogenMod Installer.... wtf ever happened with this program?!?!?! It sounds awesome!! It said it even would unlock bootloaders and everything. It was only after reading that it was put out of service that I stopped doing my happy dance. why in the fudge brownie cheesecake would you delete something so awesome? Anyway, can you guys plesaea help before I commit android suicide. That would be great.
I CAN'T BOOT INTO CUSTOM RECOVERY. IF I COULD DO THAT I COULD DO ANYTHING. UGGGGG
Anything, whatever...
I'm at a loss here......
It's been days and I'm frustrated.
910T3 versions are locked down for good after 6.0.1MM update but you could DO2 it and then just be stuck without wireless and NFC. Lol, its just so dumb isnt it lol. Pretty soon in the future maybe they'll jusf give us an option to have our devices custom made by your own specs??
djscottallen said:
Man, I've really done research until my eyes are ready to pop out lol. Can someone please help me.
I'm using this guide to try and unlock my bootloader: https://www.youtube.com/watch?v=cfpehEkhfyg
Problem is, it's for a verizon version, mine's a note 4 T-mobile sm-n910t3
I'm just a noob and never had to do this unlock bootloader crap on my note 2. I need help.
I just want to unlock the bootloader, and flash recovery, supersu, and a cool rom like res. remix or CM remix.
On the video, the part I'm stuck on is he's using a file: "samsung_unlock_n4-2" with no file extension (.xxx)
I'm assuming this is a bootloader file?? I found a bootloader for my version which is a folder with contents:
FOLDER: BL_N910T3_DOK2 CONTENTS: aboot.mbn / NON-HLOS.bin / rpn.mbn / sbl1.mbn / sdi.mbn / tz.mbn
He goes on to use a CMD and fastboot to temporarily root the phone to install TWRP recovery,
but when he pushes this command: "adb push samsung_unlock_n4-fix /data/local/tmp/"
I don't think I can do that with a folder and I don't know which file to use.
QUESTION:
-DOES ANYONE KNOW WHICH FILE I NEED
-OR-
IS THERE A BETTER WAY TO FLASH A CUSTOM KERNEL THAT UNLOCKS THE BOOTLOADER, THEN ROOT, FLASH ROM AND EVERYTHING A LOT EASIER.
Side note, I didn't know I had to unlock FRP and tried to flash recovery. I also tried CFautoroot.
Both are blocked from working so I'm just assuming the bootloader is locked, otherwise it would say "mode developer" on the stock recovery. Off topic, I started reading about CyanogenMod Installer.... wtf ever happened with this program?!?!?! It sounds awesome!! It said it even would unlock bootloaders and everything. It was only after reading that it was put out of service that I stopped doing my happy dance. why in the fudge brownie cheesecake would you delete something so awesome? Anyway, can you guys plesaea help before I commit android suicide. That would be great.
I CAN'T BOOT INTO CUSTOM RECOVERY. IF I COULD DO THAT I COULD DO ANYTHING. UGGGGG
Anything, whatever...
I'm at a loss here......
It's been days and I'm frustrated.
Click to expand...
Click to collapse
So far i know is N910T3 bootloader is not locked unlike verizon or at&t .
All you have to do is go to settings/about device and hit on build number 7 times .
You will see in settings "developer options" go to OEM UNLOCK and just turn it on this will unlock your bootloader and make sure reactivation lock is turned off in settings/security.
Thats it now you can go to download mode and flash twrp recovery and flash any rom from twrp compatible for your model.
Trex888 said:
So far i know is N910T3 bootloader is not locked unlike verizon or at&t .
All you have to do is go to settings/about device and hit on build number 7 times .
You will see in settings "developer options" go to OEM UNLOCK and just turn it on this will unlock your bootloader and make sure reactivation lock is turned off in settings/security.
Thats it now you can go to download mode and flash twrp recovery and flash any rom from twrp compatible for your model.
Click to expand...
Click to collapse
Did this work, as in actually unlocking the bootloader right then, just by checking that box? I thought that option only got the phone ready for unlocking or something like that. I'm trying to root a T3 and don't want to flash over an unlocked bootloader, of course.
Trex888 said:
So far i know is N910T3 bootloader is not locked unlike verizon or at&t .
All you have to do is go to settings/about device and hit on build number 7 times .
You will see in settings "developer options" go to OEM UNLOCK and just turn it on this will unlock your bootloader and make sure reactivation lock is turned off in settings/security.
Thats it now you can go to download mode and flash twrp recovery and flash any rom from twrp compatible for your model.
Click to expand...
Click to collapse
Has anyone tried this? I have an 910T3 running a custom ROM on lollipop 5.1.1. I wish to try and upgrade to marshmallow 6.0.1, and eventually a new custom ROM, but I am hesitant to do so as I have read that the 910T3 cannot be downgraded, should I like to return back to lollipop.
After setting OEM unlock , don't you need to use a procedure with adb fastboot through a terminal interface to unlock the bootloader?
I would love to know more about this before I attempt and irreversible upgrade.
Any help or advice would be greatly appreciated.
580guy said:
Has anyone tried this? I have an 910T3 running a custom ROM on lollipop 5.1.1. I wish to try and upgrade to marshmallow 6.0.1, and eventually a new custom ROM, but I am hesitant to do so as I have read that the 910T3 cannot be downgraded, should I like to return back to lollipop.
After setting OEM unlock , don't you need to use a procedure with adb fastboot through a terminal interface to unlock the bootloader?
I would love to know more about this before I attempt and irreversible upgrade.
Any help or advice would be greatly appreciated.
Click to expand...
Click to collapse
Once you upgrade to marshmallow you cannot downgrade to lollipop forget it.
To unlock bootloader you just have to turn on oem unlock thats it no need adb.
If you are already running custom rom as you mentioned your bootloader should be already unlocked.
Trex888 said:
Once you upgrade to marshmallow you cannot downgrade to lollipop forget it.
To unlock bootloader you just have to turn on oem unlock thats it no need adb.
If you are already running custom rom as you mentioned your bootloader should be already unlocked.
Click to expand...
Click to collapse
So, trying to clarify, what you are saying is once you upgrade to marshmallow bootloader is permanently locked? From what I understand, locked bootloaders are what prevent you from changing ROMs, so I assume you are saying that OEM unlock will not work under marshmallow?
So no way I could reflash DOK2 Bootloader and return to Lollipop again? Or just flash a stock Lollipop ROM with ODIN?
580guy said:
So, trying to clarify, what you are saying is once you upgrade to marshmallow bootloader is permanently locked? From what I understand, locked bootloaders are what prevent you from changing ROMs, so I assume you are saying that OEM unlock will not work under marshmallow?
So no way I could reflash DOK2 Bootloader and return to Lollipop again? Or just flash a stock Lollipop ROM with ODIN?
Click to expand...
Click to collapse
Oem unlock will work no problem on marshmallow and you can root & flash roms easily same as lollipop.
But you can only flash marshmallow roms once you upgrade.
I was saying only you cannot downgrade from marshmallow to lollipop.
odin will fail if you try to downgrade
Trex888 said:
Oem unlock will work no problem on marshmallow and you can root & flash roms easily same as lollipop.
But you can only flash marshmallow roms once you upgrade.
I was saying only you cannot downgrade from marshmallow to lollipop.
odin will fail if you try to downgrade
Click to expand...
Click to collapse
Thanks for the reply. In doing more searching around I found one of your older posts from 2016 and it sounds to me like it is a idiosyncrasy of the 910t3. I believe you stated you sold the T3 and ended up getting a 910T for that reason, so you could downgrade if you wished. Looks like I will be sticking with lollipop, unless I get another motherboard or phone. Thanks again for the response.
Related
Hello, I am returning my Moto X back to motorola and had a few questions. I have the Tmo US xt1053 model that i've updated to 4.4.2, unlocked the bootloader, flashed twrp and rooted. I want to return it to stock but there are no factory firmware images for the Tmobile US 4.4.2 and I would like to avoid bricking my phone. I was going to return to the stock recovery and then just factory reset it from the privacy menu but I am afraid to flash the stock recovery for fear of bricking it.
So my question is, can I flash the stock recovery found here: http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ ? I can't seem to figure out if there are different recovery versions like there is bootloader versions and if I don't flash the correct one I'll brick something.
I know the bootloader was updated with 4.4.2 so I can't return to 4.4 but if I flash that stock recovery can I just use the factory restore option in the stock rom to remove all my data and root? I know the bootloader will still be unlocked but I highly doubt they will notice that since they never seem to check the bootloader unless its obviously unlocked.
Are you slow???
Turn your phone off then turn it back on and explain to me how you expect them not to notice your bootloader is unlocked?
Even if you used a different boot image to hide the warning, it shows that you're bootloader is unlocked in fastboot. I wouldn't bother hoping they don't notice, I'd hope they don't care.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
Did you read at all when you unlocked the bootloeader? Your warranty is voided. They do not need to have physical contact with your phone at all to determine it's voided.
Just for xt1053, you can downgrade firmware from 4.4.2 to 4.4, but just for this specific case, it doesn't mean it won't brick for other version.
SymbioticGenius said:
Are you slow???
Turn your phone off then turn it back on and explain to me how you expect them not to notice your bootloader is unlocked?
Even if you used a different boot image to hide the warning, it shows that you're bootloader is unlocked in fastboot. I wouldn't bother hoping they don't notice, I'd hope they don't care.
Click to expand...
Click to collapse
Fastboot OEM lock
Problem solved?
eksasol said:
Just for xt1053, you can downgrade firmware from 4.4.2 to 4.4, but just for this specific case, it doesn't mean it won't brick for other version.
Click to expand...
Click to collapse
I hope you didn't flash the bootloader for 4.4, if you did... enjoy your new paperweight
mastarifla said:
Fastboot OEM lock
Problem solved
Click to expand...
Click to collapse
Relocking the bootloader and never locking the bootloader are completely different things. Good luck with that.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
SymbioticGenius said:
Relocking the bootloader and never locking the bootloader are completely different things. Good luck with that.
Click to expand...
Click to collapse
Turns out Motorola uses the QFuse system. While the bootloader will look perfectly "stock"/locked to you, Moto will be able to see that the secure boot fuse was blown, thus, re-locking your bootloader is effectively pointless.
mastarifla said:
Fastboot OEM lock
Problem solved?
I hope you didn't flash the bootloader for 4.4, if you did... enjoy your new paperweight
Click to expand...
Click to collapse
It doesn't let you downgrade it regardless, so doesn't matter.
Also fastboot oem lock only work for developer version, and you have to go through the "fastboot oem lock begin" process: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I don't think you can relock the regular version.
eksasol said:
It doesn't let you downgrade it regardless, so doesn't matter.
Also fastboot oem lock only work for developer version, and you have to go through the "fastboot oem lock begin" process: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I don't think you can relock the regular version.
Click to expand...
Click to collapse
...Unless if you manually flash the files, in which the problem occurs
T-Mobile version is the same as the Dev, maybe the AT&T version is different
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
SidedX said:
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
Click to expand...
Click to collapse
First check here... http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Get the sdk tools and once set up, see if you can do adb devices and have the phone show up on the PC, if so, do adb push (name of rom file) then boot to twrp and install. If that doesn't work, check the same page above (since you don't have an OS not sure what would happen) try the unlock instructions for fastboot ( I would wait for someone else to comment before trying this). You might want to message this user http://forum.xda-developers.com/member.php?u=2872010 rootSU and see if he can give guidance, he has lots of experience.
Locked Bootloader
I still can't seem to get past the fact that my bootloader is locked...
Thanks though.
SidedX said:
I attempted to flash and unroot my Nexus 6 via Wugfresh's tool, and thought it was a success. I hit 'relock' and now the device is bootloader locked with no OS installed.
However, I can connect via fastboot so far, but I am not very good with it. I think I may also be able to push files, but when I attempted to flash SlimLP the device just reset.
TWRP is still present on the device, but I cannot unlock my bootloader without getting a ROM on there... So I am stuck...
I need to mail this phone back in tomorrow for cracked screen, so I am hoping someone can help me. Thank you.
Click to expand...
Click to collapse
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexu...tboot-t3066052.
Flashing
Hey, thanks for the tip.
The link you sent was dead, and can you help me understand the commands for flashing in ADB with a locked bootloader?
SidedX said:
Hey, thanks for the tip.
The link you sent was dead, and can you help me understand the commands for flashing in ADB with a locked bootloader?
Click to expand...
Click to collapse
Sorry my bad, here it is http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Follow the instructions as i posted, place the download rom in the /android-sdk/platform-tools/ folder and boot in bootloader and select recovery, select adb sideload there and type in cmd: adb sideload name.zip.
Unlocked Bootloader
The thread says they are for unlocked bootloader only.
I have TWRP installed, but for some reason at one point my bootloader was relocked.
So now I have No OS to 'enable oem unlock' to unlock my bootloader.
This is my issue.
SidedX said:
The thread says they are for unlocked bootloader only.
I have TWRP installed, but for some reason at one point my bootloader was relocked.
So now I have No OS to 'enable oem unlock' to unlock my bootloader.
This is my issue.
Click to expand...
Click to collapse
It worked for other users, but hey if you have a better option try that.
I don't understand, what do you mean it worked for other users? The thread specifically states the bootloader has to be unlocked, and unfortunately I do not have an unlocked bootloader.
So I cannot fix this issue unless I either get a rom to flash with a locked bootloader, or somehow force unlock the bootloader
SidedX said:
I don't understand, what do you mean it worked for other users? The thread specifically states the bootloader has to be unlocked, and unfortunately I do not have an unlocked bootloader.
So I cannot fix this issue unless I either get a rom to flash with a locked bootloader, or somehow force unlock the bootloader
Click to expand...
Click to collapse
Look in this thread http://forum.xda-developers.com/nex...bootloader-t3116744/post60931367#post60931367, he had the same problem as you (locked bootloader). I`m not a jehova witness trying to convince you to swap sides, i`am trying to help you here.
Thanks
I see, I was able to adb push /sdcard/. a factory image to get back in with a locked bootloader, thank you.
gee2012 said:
Look in this thread http://forum.xda-developers.com/nex...bootloader-t3116744/post60931367#post60931367, he had the same problem as you (locked bootloader). I`m not a jehova witness trying to convince you to swap sides, i`am trying to help you here.
Click to expand...
Click to collapse
hallelujah!
cam30era said:
hallelujah!
Click to expand...
Click to collapse
That covered the spiritual moment of the day
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.
Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk
SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.
TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.
Hi,
I've searched and found how to do it but it was for Android 5.1 but I'm on 7.0 and I my recovery is TWRP 3.0.2-0 and apparently there are more steps to do if you are on TWRP, I'm wondering what are they.
Thanks
test84 said:
Hi,
I've searched and found how to do it but it was for Android 5.1 but I'm on 7.0 and I my recovery is TWRP 3.0.2-0 and apparently there are more steps to do if you are on TWRP, I'm wondering what are they.
Thanks
Click to expand...
Click to collapse
First, questions need to go in the Nexus 6 Q&A, Help & Troubleshooting Thread, not the General thread. Second, the steps to lock the bootloader have not changed. It's done from the bootloader with fastboot and the command "fastboot oem lock". It shouldn't matter what recovery you have.
Re-locking needs stock recovery(maybe full stock; boot, recovery, system) if you try to re-lock your boot loader without stock recovery you might hardbrick your phone. So just backup your apps and files, flash a stock image from google and re-lock your boot loader with "fastboot oem lock". Which probably needs wiping your phone.
Before you do anything search these forums for the many people who locked their bootloader and then when they had problems ended up with a bricked and useless device. Unless you have a very special reason for locking, leave it unlocked
dahawthorne said:
Before you do anything search these forums for the many people who locked their bootloader and then when they had problems ended up with a bricked and useless device. Unless you have a very special reason for locking, leave it unlocked
Click to expand...
Click to collapse
this right here...there is really no reason to ever re lock your bootloader
I flashed the factory image and and it went fine. But the bootloader is still unlocked. My main concern for locking the bootloader is to prevent any malicious app to root the phone and hide themselves by like installing as system app or something. And I'm not planning to flash any custom ROM. So:
1- Since I'm on stock ROM, is there still a possibility of hard bricking my phone if I relock?
2- If I leave it unlocked, will malwares be able to tamper with the phone by the means I mentioned or similar approaches?
Thanks
2. No, they don't. Bootloader is on a completly different layer.
test84 said:
I flashed the factory image and and it went fine. But the bootloader is still unlocked. My main concern for locking the bootloader is to prevent any malicious app to root the phone and hide themselves by like installing as system app or something. And I'm not planning to flash any custom ROM. So:
1- Since I'm on stock ROM, is there still a possibility of hard bricking my phone if I relock?
2- If I leave it unlocked, will malwares be able to tamper with the phone by the means I mentioned or similar approaches?
Thanks
Click to expand...
Click to collapse
I feel your concerns. I think the safest bet is to watch where you download apps and content from. And make sure "unknown sources" is turned off. That should minimize your potential for problems. I think the main thing is watching where you get apps from.
Hello
Hoping somebody can help getting my phone up and running again.
I wanted to unroot my phone, because i was having issues with danish "MitId". And was a bit sloppy with it.
First i tried using SuperSU to remove root. Because i didnt feel like setting everything up again. Didnt work.
Then I locked the OEM Lock in developer settings. Not thinking this would be a fatal error.
Got home from work, and said to myself. Jusk lock the bootloader and the phone will reset itself.
But this is not the case, when you have been stupid enough to lock the OEM lock.
Now I am stuck on "No valid operating system could be found. The device will not boot"
I can get in to fastboot by pushning power+vol down. But cannot flash anything since the phone thinks the OEM Lock is locked on it.
Does anyone know of a solution for me. Or is it going to the shop tommorow and say that my phone is going this. And hope they will sort it for me?
Can't you fix stuff by using https://flash.android.com/ ?
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Pearsondk said:
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Click to expand...
Click to collapse
Try sideloading the full OTA. You don't need an unlocked bootloader for that.
Unfortuatly not, if I try to enter recovery mode. The phone just goes back to the screen saying "No valid operating system could be found. The device will not boot"
ADB is not available to me
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
*****I apologize I just saw it's actually still locked****"
Contact U-break I-fix if I typed that correctly. The third party warranty repair center for Google's warranty. I believe they can attempt to switch the boot slot with a locked bootloader with the equipment they use to reflash these devices. If anything it's under warranty get the RMA and if the bootloader is locked on it trade someone or sell it and use it to make buying a new cheaper..
JovialQuestion said:
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
Click to expand...
Click to collapse
No, I can get into fastboot and that is it.
But everything I try in fastboot gets rejected, since it says the phone is locked.
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
JovialQuestion said:
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works. Use the volume keys and power button to select it
Click to expand...
Click to collapse
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
Google is not responsible for phone's with locked bootloaders. They make the device with the specifications the carrier that sells it stipulates. Google themselves allows the unlock.
Lughnasadh said:
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Click to expand...
Click to collapse
Iam guessing the same. Phone doesnt want to do anything.
And since i cant get into the phone to oem lock i am stuck. Live in Denmark, so by law I havnt voided the warrenty by rooting.
Pixel warranty is always valid even if you unlock and root. Google doesn't void the warranty. Go to Google pixel support page. Find warranty and act as if your submitting a RMA and it will tell you after you enter the device IMEI how long your warranty is valid for
Delete
If that were true. Android flash tool https://flash.android.com/welcome
Would work as it's the same process for the browser to flash the very same file. Motorola allowed signed factory img on locked. Google had never allowed that in fastboot as far as I am aware
DroidRommer said:
All you need to do is go here Factory pixel firmwares and scroll down to pixel 7 panther assuming you're not on the pro (cheetah)
-select the latest version for your model whether that's Verizon or whatever if you have the carrier unlocked one like myself just choose the Feb firmware that doesn't have a carrier name at the end of the firmware number (you should have your phone plugged into your PC and in fastboot mode) click flash and follow the steps. These are Googles factory images so it doesn't matter if your bootloader is unlocked or not as long as you choose the latest version and the correct version for your phone. Tbh you can't really brick the pixel 7 as long as you have a PC and are able to put the phone in fastboot mode (holding the volume down and power button while powering on)
-Anytime you run into some kind of bootloop issue or wanna get rid of root flashing the stock firmware from this website will factory reset and revert your phone to the way it was the very first time it was pulled out of the box and powered on. If you have already tried this and you know forsure you did everything correctly then I must admit I have never had this happen and I'm someone who flashes custom roms and goes back to stock to get the latest security update just to turn around and flash another custom rom right after lol. If you need any help or advice feel free to pm me whenever. I have been rooting phones for a long time and have to say that the Google pixel is by far the most user friendly phone I've ever owned when it comes to custom rooms, rooting etc. You can ALWAYS go back as long as you know what steps to take. Sorry for the rant especially if you already figured it out.
Happy Customizing!
DROIDROMMER
Click to expand...
Click to collapse
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Edit: I was not aware you couldn't flash the stock firmare using googles dev page without oem unlock. I apologize for jumping to conclusions. I thought I had every possible bad scenario happen to me by now but apparently I learned something new today.
DroidRommer said:
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Click to expand...
Click to collapse
Dude. You cannot flash factory images of any kind on any Google phone with the bootloader in locked status. Please stop giving false information on here. If you want to talk up Samsung do it on a Samsung post. Let's not confuse everyone please
DroidRommer said:
Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader.
Click to expand...
Click to collapse
To use Android Flash Tool, you have to have OEM Unlocking enabled in Developer Options for it to be able to unlock the bootloader.
To flash the factory image in fastboot you must have an unlocked bootloader.
Lughnasadh said:
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Click to expand...
Click to collapse
Okay my bad you are right fortunately I have never had this happen. And like someone else said if he can't get into recovery then he can't sideload a factory ota... sorry I'm at a loss on this one. Some custom roms use "fastboot update file.zip" would that do anything in this case or would that command not even work with a locked bootloader I'm assuming. I apologize for trying to act like a know it all I've just never heard of this happening