Database Develop

Bricked Nexus 6 and cant unlock bootloader

I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?

win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
without enabling oem unlock in the developer options, nope. but you can use the stock recovery to check if a factory reset would help.

Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).

win465 said:
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
Click to expand...
Click to collapse
Had you unencrypted?

Yes, but i flashed backed to stock kernal.

win465 said:
Yes, but i flashed backed to stock kernal.
Click to expand...
Click to collapse
How?

Using the nexus tool kit. After that I locked the bootloader to sideload the update.

win465 said:
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
Click to expand...
Click to collapse
Were you rooted before all of this too?

Nope

Evolution_Tech said:
Were you rooted before all of this too?
Click to expand...
Click to collapse
Nope

win465 said:
Nope
Click to expand...
Click to collapse
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.

Evolution_Tech said:
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Click to expand...
Click to collapse
Thank you for your help

Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.

RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
Click to expand...
Click to collapse
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.

Possible idea
Evolution_Tech said:
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Click to expand...
Click to collapse
There's some more concrete info in the first couple pages, especially regarding our N6's:
http://forum.xda-developers.com/nexus-9/help/to-toggle-allow-oem-unlock-via-fastboot-t3091119
Hope this helps.
I'll keep my eyes open for anything that seems pertinent.
Best of luck

RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
Click to expand...
Click to collapse
I get this error message "system partition has unexpected contents" (Status 7).

win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
Can you fastboot boot twrp recovery? And if that is possible, will twrp flash zips with a locked bootloader?
Edit: I'm almost certain fastboot boot recovery won't work with a locked bootloader. I almost thought I had a good idea.

I am in the same situation. Bootloader locked and no custom recovery nor adb enabled. surprisingly enough, yesterday my phone could boot up but it's stuck now in the configuration process. I cannot access to the settings so I can check usb debugging or oem unlock. I can only access the dialer. my question is: is there anyway to do that with just a dialer code?

Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).

Didgeridoohan said:
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Click to expand...
Click to collapse
Sorry for the noob question but where can I find these OTAs and how to install one of them? Does it require usb debugging to be enabled?

XT1092 stuck in wipe bootloop after OTA to 6.0

Hi guys,
Im using XT1092 RetEU, i have installed latest ota without a problems
Then i wanted to wipe/factory reset from recovery after the upgrade, i thought it went well.
from this point im stuck at wipe bootloop, every time phone starts it goes through moto logo then blank for a second, again motorola logo and starts to wipe itself, i managed to enter recovery during the wipe, at begining it was just showing me android logo with text "erasing" when i press power + vol up it enters recovery, i tried to do the wipe from there, but it still stuck. Ive got acces to bootloader, version 60,16, recovery version is 23.32-25.1.

1) Download the latest 5.1.1 Stock Firmware for your device (there is thread, where all the firmwares are available) and flash it using fastboot terminal.
Note: It will delete everything on your device and make it vanilla clean.
2) Wait for the device to boot into 5.1.1 and then download the OTA update (in my case victara_reteu.reteuall) manually. Someone uploaded the zip file in the General forum , one is for Eu/Asia, another is German, I think.
3) Reboot the device into fastboot mode, then into recovery mode and flash the OTA zip that we downloaded earlier. It would take at most 10-15 mins. Don't worry, drink some coffee.
After that Wipe/Factor Reset the device and Reboot.
There you go, plain and simple. Enjoy Marshmallow. I heard you like'em.

Hi, still not working, when flashing there is info :"version downgraded for system" during the system.img_sparsechunk0 flashing

kaisangi said:
Hi, still not working, when flashing there is info :"version downgraded for system" during the system.img_sparsechunk0 flashing
Click to expand...
Click to collapse
I am guessing that your boootloader is locked? That would be the most likely cause for that to fail. With a locked bootloader you can only flash the same version, you can't downgrade. You have 2 options, unlock your bootloader and try again. Or wait for a 6.0 full firmware for your model to leak.
Sent from my XT1095 using Tapatalk

Thanks for your help, yes, i'm locked. Is there any way to unlock the bootloader without ticking the box "enable OEM unlock"? since i can't start the system...?

kaisangi said:
Thanks for your help, yes, i'm locked. Is there any way to unlock the bootloader without ticking the box "enable OEM unlock"? since i can't start the system...?
Click to expand...
Click to collapse
No, there is no way to do it. At this point you have 2 choices. Send it in for repair, or wait for a full 6.0 firmware image for your model to appear.
Sent from my XT1095 using Tapatalk

Custom Binary (TWRP) bootloop/no boot

Hi All, I have a N950F/DS currently running Stock N950FXXU3CRE5 FW and every time I install twrp and do the "Data mount fix" my phone refuses to boot unless I root it with Magisk or SuperSU. I dont want root but I do want twrp, can someone help with this problem thanks in advance.

What are you trying to achieve with Data mount fix?
try RMM-State_Bypass_Mesa_v2 so oem unlock would not turn off after reboot here

bluecub1st said:
What are you trying to achieve with Data mount fix?
try RMM-State_Bypass_Mesa_v2 so oem unlock would not turn off after reboot here
Click to expand...
Click to collapse
For some reason this didn't work for me. I kept losing OEM unlock anyway. I ended up having to not reboot my phone for a week.

I found a solution. I downloaded two boot imgs without the "dm verity" and my phone booted with twrp. Also it doesn't remove twrp after rebooting

help
Vell123 said:
I found a solution. I downloaded two boot imgs without the "dm verity" and my phone booted with twrp. Also it doesn't remove twrp after rebooting
Click to expand...
Click to collapse
can you help me like you did I have the same problem and I do not know what to do

deyher2007 said:
can you help me like you did I have the same problem and I do not know what to do
Click to expand...
Click to collapse
Sure what binary are you currently using?

U4
Vell123 said:
Sure what binary are you currently using?
Click to expand...
Click to collapse
U4

i dont have any dm verity for u4 besides that sounds like snapdragon or the american model so this method wont work for you friend

Cant flash TWRP Recovery

Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.

VortexHD said:
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
Click to expand...
Click to collapse
ARE YOU EXYNOS OR SNAPDRAGON ?? Below guide is for EXYNOS!!
Did you follow this guide --> https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143 ??
And did you do step 3 ? 3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card ??i haven't rooted my Note 9 yet but i think that's where you messed up!

Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f

rana14301 said:
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
Click to expand...
Click to collapse
read dr ketans guide in the general discussion thread.

N960F Lost IMEI after successful root

Hello ... Any ideas on recovering IMEI after successful root of Note9 ?
IMEI currently unknown (both), TWRP shows empty EFS folder (should i see these files?), Software Baseband is UNKNOWN too.
Software factory wipe done with no effect, OEM unlock is unlocked (and not greyed out).
Thanks

Just wondering if anyone has recovered from this ?

did you read all of dr ketans thread on root?
go to general discussion section / dr ketan oem fix and root and simply do a search in that thread for imei
edit
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143
basicaly you flash back stock firmware and try again.

bober10113 said:
did you read all of dr ketans thread on root?
Click to expand...
Click to collapse
do let us know the tread link

bober10113 said:
did you read all of dr ketans thread on root?
go to general discussion section / dr ketan oem fix and root and simply do a search in that thread for imei
edit
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143
basicaly you flash back stock firmware and try again.
Click to expand...
Click to collapse
nrah said:
do let us know the tread link
Click to expand...
Click to collapse
added link

Thanks for the link
I have been plowing through - i still can't work out how to backup the EFS before TWRP is installed.
Should the backup take place after TWRP is installed, before the first reboot (and before running the Dr's script) ??

nrah said:
Thanks for the link
I have been plowing through - i still can't work out how to backup the EFS before TWRP is installed.
Should the backup take place after TWRP is installed, before the first reboot (and before running the Dr's script) ??
Click to expand...
Click to collapse
restore back to stock and be sure everything works.
then flash twrp with odin and dont let phone reboot.
manualy reboot to recovery. using an external sd card backup EFS partition.
go to wipe menu and format data.
go to reboot menu and reboot back to recovery.
go to wipe menu and do a factory wipe, the default swipe right option.
now you have 2 choices:
either flash dr ketan method 1 root oem fix zip and stay on stock firmware.
or
flash dr ketan method 1 zip and then flash a custom rom.
then reboot. if no signal restore the backup of efs you made earlier.

bober10113 said:
restore back to stock and be sure everything works.
then flash twrp with odin and dont let phone reboot.
manualy reboot to recovery. using an external sd card backup EFS partition.
go to wipe menu and format data.
go to reboot menu and reboot back to recovery.
go to wipe menu and do a factory wipe, the default swipe right option.
now you have 2 choices:
either flash dr ketan method 1 root oem fix zip and stay on stock firmware.
or
flash dr ketan method 1 zip and then flash a custom rom.
then reboot. if no signal restore the backup of efs you made earlier.
Click to expand...
Click to collapse
I have been doing this, except for the additional step on the factory wipe that you pointed out - thanks.
But after three full rounds of rooting and trying to restore the EFS, i still have "unkown" and no Baseband information when i get to the end. When i return to the stock image, both Baseband & IMEI's are present.
I have backed up EFS/Baseband/Carrier configs/carrier images successfully and restored all 4 partitions. But IMEI does not return.

nrah said:
I have been doing this, except for the additional step on the factory wipe that you pointed out - thanks.
But after three full rounds of rooting and trying to restore the EFS, i still have "unkown" and no Baseband information when i get to the end. When i return to the stock image, both Baseband & IMEI's are present.
I have backed up EFS/Baseband/Carrier configs/carrier images successfully and restored all 4 partitions. But IMEI does not return.
Click to expand...
Click to collapse
are you on pie or oreo?

bober10113 said:
are you on pie or oreo?
Click to expand...
Click to collapse
8.1, Oreo .. was thinking of grabbing a ver9 image and giving it a go

nrah said:
8.1, Oreo .. was thinking of grabbing a ver9 image and giving it a go
Click to expand...
Click to collapse
did you try method 2 in dr ketans oem fix root hread?
also maybe try flashing a custom rom instead of being on stock and see if that works out for you.
but to think of it, believe your issue is kernel related. i think i remember reading something about it.
so after twrp and data format , reboot back to twrp and oem fix, dont reboot to OS yet. try flashing endurance kernel or tgp kernel. just be sure to take the appropriate oreo or pie version depending on what android os version you go on.

bober10113 said:
did you try method 2 in dr ketans oem fix root hread?
also maybe try flashing a custom rom instead of being on stock and see if that works out for you.
but to think of it, believe your issue is kernel related. i think i remember reading something about it.
so after twrp and data format , reboot back to twrp and oem fix, dont reboot to OS yet. try flashing endurance kernel or tgp kernel. just be sure to take the appropriate oreo or pie version depending on what android os version you go on.
Click to expand...
Click to collapse
:good:
I have not tried method 2 yet .. I did flash OREO and when i tried to run to flash TWRP, the console echoed "Only official released binaries are allowed to be flashed(Recovery)". So i will need to roll back to an earlier image on 8.1
Forgive my lack of knowledge - where would i find the endurance kernel ? Thanks.

nrah said:
:good:
I have not tried method 2 yet .. I did flash OREO and when i tried to run to flash TWRP, the console echoed "Only official released binaries are allowed to be flashed(Recovery)". So i will need to roll back to an earlier image on 8.1
Forgive my lack of knowledge - where would i find the endurance kernel ? Thanks.
Click to expand...
Click to collapse
that binaries issue you had should have been fixed by ketans oem fix root.( method 1)
when you flash back stock to correct the issue. go to system settings and go down to software update and make if manualy find updates. it will then pop up "device registered". then to go to software and tap "build" a few times to make developer options appear.
then go check in dev options oem unlock should say already unlocked."
if i dont do the manual software update check thing after a binaries issue, i would get stuck.
also unrelated:
when you flash stock, you flash all 5 files right?( in odin csc slot you put csc.md5 and not the home csc.md5 and all the other slots only have 1 appropriate file so you cant go wrong there)
endurance:
https://forum.xda-developers.com/galaxy-note-9/development/kernel-endurance-kernel-v1-1-7-t3883862/
v2.xxxx is pie
v1.xxxx is oreo
after flashing kernel.zip you MUST flash magisk or you wont have anyways to manage root and give permissions.
so also flash right after kernel:
https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-v19.3.zip will eventualy be not the latest( check last link below dor mire up to date)
then if and when phone boots up you can install the magisk manager app:
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.1.2/MagiskManager-v7.1.2.apk
both can be found here are up to date :
https://github.com/topjohnwu/Magisk/releases

bober10113 said:
that binaries issue you had should have been fixed by ketans oem fix root.( method 1)
when you flash back stock to correct the issue. go to system settings and go down to software update and make if manualy find updates. it will then pop up "device registered". then to go to software and tap "build" a few times to make developer options appear.
then go check in dev options oem unlock should say already unlocked."
Click to expand...
Click to collapse
In developer mode, it was set for USB debug correctly. The OEM lock option was not present on this OREO version.
Currently bumping back to 8.1
And yes, I select all 4 files in Odin.

nrah said:
In developer mode, it was set for USB debug correctly. The OEM lock option was not present on this OREO version.
Currently bumping back to 8.1
And yes, I select all 4 files in Odin.
Click to expand...
Click to collapse
well thats one of your problems. if oem unlock has not appeared you either need to wait for 7 days or try the method i described by visiting system/software update/manual update and wait for a pop up message that says device registered. then go back to dev options to see of OEM unlock has appeard and says that it is unlocked

Waititng 7 days sure....
That doesn't work imho. Just download an older 8.1 stock rom and flash . u will find OEM to be unlocked there.

The fix in the end was to use the Root_for_OEM_issue_devices_v5 script. I had been using the v3 script. I had followed Max's vid from high on Android, where he's got the earlier script version on his site.
Issue also, once rooted, was that Magisk was out of sync - Magisk was ahead of the manager, so i down graded the manager (once I worked out the release pairs), and magisk was stable again. I did note that the Magisk did not always maintain root for some reason, when the version were out of sync. Possible connection, not sure.
Must admit you learn a lot about these phones when you have a root problem - a lot more compared to someone just following someone else's good work and wanting the %100 it will work path !
Thanks bober10113 for chipping in along the way.