Database Users

[Q] Is the new HTC EVO bootloader really locked??

I KNEED AN ANSWER TO THIS SUBJECT.
I have read some of the posts about the new EVO 4G update, and some of the people have complained about the new update has a locked bootloader.
I need to know is it really locked?
I downloaded a Android 2.3.3 update a couple of months ago, and it came with the new fastboot option enabled by default. With fastboot enabled, the phone boots much faster, but you would be locked out of the bootloader. That was only until you disabled it. Then it was business as usual getting into the bootloader (volume down + power button).
Now I hear that some of the people who have downloaded the latest (unrooted) EVO update have their bootloaders locked, while others were able to do a nandroid recovery to restore their phones after updating because the phone was still S-OFF. That would mean that the bootloader is still unlocked. How can a bootloader be both locked and unlocked.
Is the bootloader really locked by the update, or is it just temporarily locked because these people did not turn off the fastboot option in the settings, which does bypass the bootloader. Does anyone know, or how many people know the answer to this?

It's locked and not encrypted is what I believe.
Sent from my PC36100 using Tapatalk

novanosis85 said:
It's locked and not encrypted is what I believe.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Any sources for this information, or did I overlook a post?

how to access recovery after 2.3.3 update
1.Turn phone off. 2. Remove battery from phone. 3.Hold Volume button down and power button at same time for like 7 seconds. 4. That's it.

If you get a new EVO 4g with 2.3.3 yes it will be locked. HTC said all future devices will be unlocked that is why the EVO 4g is still locked.
The EVO 4g OTA and 2.3.3 out of the box is not encrypted just locked.
Source: me doing a lot of reading today.

Locked. Not encrypted.
I have a hunch that HTC meant to say that their bootloaders would no longer be encrypted rather than locked.

pharmteckCA said:
1.Turn phone off. 2. Remove battery from phone. 3.Hold Volume button down and power button at same time for like 7 seconds. 4. That's it.
Click to expand...
Click to collapse
When are you supposed to put the battery back in??? I'm confused

soxfan81 said:
When are you supposed to put the battery back in??? I'm confused
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PC36100 using Tapatalk

If you were s off when updating, you will still be able to flash recoveries and roms etc. If you were s on and updated, your SOL for now.

exSD said:
Locked. Not encrypted.
I have a hunch that HTC meant to say that their bootloaders would no longer be encrypted rather than locked.
Click to expand...
Click to collapse
First of all, there isn't a phone out there with an encrypted bootloader. There are however cryptographically signed bootloaders. Huge difference.
Second, they did in fact say the bootloaders will no longer be locked.

Rakeesh_j said:
cryptographically
Click to expand...
Click to collapse
That's a crazy serious word right there.

mattykinsx said:
That's a crazy serious word right there.
Click to expand...
Click to collapse
+1 it makes me feel retarded.
HTC EVO = my best friend

I wonder if we can just OEM unlock it in fastboot?

RileyGrant said:
If you were s off when updating, you will still be able to flash recoveries and roms etc. If you were s on and updated, your SOL for now.
Click to expand...
Click to collapse
So, if someone's phone is still S-OFF after updating, and they could just flash another recovery, and then a ROM or backup, then how is the bootloader locked?

shortydoggg said:
So, if someone's phone is still S-OFF after updating, and they could just flash another recovery, and then a ROM or backup, then how is the bootloader locked?
Click to expand...
Click to collapse
Good question
Sent from my PC36100 using XDA App

shortydoggg said:
So, if someone's phone is still S-OFF after updating, and they could just flash another recovery, and then a ROM or backup, then how is the bootloader locked?
Click to expand...
Click to collapse
if your not S-OFF you can't.
asked and answered.

Alanmw86 said:
if your not S-OFF you can't.
asked and answered.
Click to expand...
Click to collapse
That did not answer the question.
The question was if your phone is S-OFF, then how is the bootloader locked, NOT WHAT YOU CANNOT DO IF YOUR PHONE IS NOT S-OFF. We already know that.
The reason I asked this question, is because some people have installed the latest update and rerooted their phones because the phones were still S-OFF. This would seem to suggest that the bootloaders are not locked.
If you do not turn off the fastboot option in the settings, or reset the battery, the bootloader will be bypassed, making it appear that the bootloader is locked when it may not be. I would like to know if anyone installed the latest (unrooted) update, and disabled the fastboot or reset the battery, and found that the bootloader is in fact locked.

My guess is that the update doesn't check your security bit, however it still prevents custom firmware from being loaded in that there isn't any mechanism available to load any custom firmware.
In other words, if your security bit is off already, and you update, you can still place a pc3600.img on your sdcard and have it flash that without it performing a signature check first.
However if your security bit is on at the time of applying the update, then you're a bit SOL, because prior to flashing the new image, it will perform a signature check.
Again, that is just my guess (haven't looked at the update as I've been using AOSP for a long time now.)

shortydoggg said:
That did not answer the question.
The question was if your phone is S-OFF, then how is the bootloader locked, NOT WHAT YOU CANNOT DO IF YOUR PHONE IS NOT S-OFF. We already know that.
The reason I asked this question, is because some people have installed the latest update and rerooted their phones because the phones were still S-OFF. This would seem to suggest that the bootloaders are not locked.
If you do not turn off the fastboot option in the settings, or reset the battery, the bootloader will be bypassed, making it appear that the bootloader is locked when it may not be. I would like to know if anyone installed the latest (unrooted) update, and disabled the fastboot or reset the battery, and found that the bootloader is in fact locked.
Click to expand...
Click to collapse
I had S-off and ran the OTA, no problem turning off the fast boot option and flashing either Clockworkmod or AmonRa. But I did have to switch to AmonRa in order to run the update, it wouldn't install with CWM.

tempe38 said:
I had S-off and ran the OTA, no problem turning off the fast boot option and flashing either Clockworkmod or AmonRa. But I did have to switch to AmonRa in order to run the update, it wouldn't install with CWM.
Click to expand...
Click to collapse
Does anyone who still has S-OFF and installed the new OTA have the new hboot version 2.16?

LG G4 (all variants) Unlock and Root Discussion/News (ONLY)

Hoyo folks.
So I'm sure you've all seen the plethora of "Do we haz root?" "How 2 unlok?" "unlok guide here"(which doesn't work) ect. Here in this thread I will attempt to summarize the current status of Unlock, Custom Recovery, and Root for each model.
Some of our devs now have Devices in hand, THANK YOU TO ALL THAT HAVE DONATED! It REALLY helps the entire G4 community! Now we wait with baited breath. (No pressure guys)
So without Further ado, here is a list of the status of all devices.
CURRENT Unlock/Recovery/Root Status, in order of success:
H815 (Europe Open model ONLY) -
Unlocked? - YES (Via LG's Official Unlocker)
Custom Recovery? - YES (TWRP info)
Root? - YES (Root Info)
NOTE: LG's offcial unlocker is a PERMANENT change. You cannot Re-lock, if you wanted to send in for a warranty claim. If you aren't willing to do that, lets wait and see if the dev's efforts will pay off with a more friendly unlock (which it may or may not)
H815 (Asia) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815 (USA) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815 (France) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H815TR (Turkey) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H818P (Thailand) -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H818N -
NO to all - "adb reboot bootloader" gets into bootloader screen, locked
H811 (T-Mobile) -
NO to all - and "adb reboot bootloader" doesn't work
H810 (AT&T) -
NO to all - and "adb reboot bootloader" doesn't work
LS991 (Sprint) -
NO to all - and "adb reboot bootloader" doesn't work
F500S -
NO to all - and "adb reboot bootloader" doesn't work
F500K -
NO to all - and "adb reboot bootloader" doesn't work
F500L -
NO to all - and "adb reboot bootloader" doesn't work
VS986 (Verizon) -
No to all - and "adb reboot bootloader" doesn't work, AND no "Enable OEM Unlock" in developer settings.

I suggest editing the thread title to be more concise/official since that is the intent of this thread:
Something like "LG G4 (all variants) Root Discussion/News"

After OEM Unlocking in Development settings and rebooting, TMO G4 reboots only after adb reboot bootloader. Anybody confirm this for TMO G4? We need root first!

For any one that ones the source code is available from LG.
T-Mobile
International
Both kernels are compile-able with a little finagling.
On Root:
From what I can see in the International code is there are the defprefs for all of the p1 versions, and it doesn't "Appear" to have ping pong patched.
I have heard "rumors" that jcase , autoprime and thecubed, are working on a root for the device, but I have not heard from either of them. They did just release pingping v6 which supports the M9, a 64-bit kernel, meaning they have made one that works with the 64-bit linux kernel. For any one curious about their progress you can always check them out on twitter. For those of you posting about root and such, you can always see if there is anything you can do to support them in their efforts.
Thanks for making the thread, I think this phone will be a fun one, and I do expect to see some great things happen.
Have a good day all!

H818P Thailand can use adb reboot boot loader

MicroMod777 said:
After OEM Unlocking in Development settings and rebooting, TMO G4 reboots only after adb reboot bootloader. Anybody confirm this for TMO G4? We need root first!
Click to expand...
Click to collapse
Thanks for confirming. Same behavior on my TMo G4.

Not as skilled as some but I do currently maintain the HTC One M8 for DirtyUnicorns.
I have my G4 pre-ordered from Verizon. It has shipped today and current tracking has it arriving Tuesday 6/2. If no one beats me to it, I will post at least the basics of how that variant functions in terms of adb and fastboot. Anything else needed I will gladly try to provide from the VZW variant.

Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?

NCguy said:
Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?
Click to expand...
Click to collapse
Yes

NCguy said:
Ok, so I'm I correct that its possible to root (when available) without it being unlocked? And with just root you could run apps like Titanium but you couldn't install a recovery or different rom while it's still locked?
Click to expand...
Click to collapse
Correct. Having root access to the operating system and having a unlocked bootloader are two different things.

barcodelinux said:
Correct. Having root access to the operating system and having a unlocked bootloader are two different things.
Click to expand...
Click to collapse
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?

NCguy said:
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?
Click to expand...
Click to collapse
I know with the last LG I had, the Optimus L90, there was a LAF partition the you had to zero out to get to fastboot. Once that was done, you could:
Code:
fastboot oem unlock
Now this was on a T-Mobile device, and T-Mobile is known for not locking bootloaders. I don't remember having an unlock.bin file, but I could be mistaken.

NCguy said:
So it sounds like without the needed file from LG this is not going to be a developer friendly phone?
Click to expand...
Click to collapse
Well we have 14 days to return it if LG doesn't give us what we need!

MicroMod777 said:
Well we have 14 days to return it if LG doesn't give us what we need!
Click to expand...
Click to collapse
That's true. I actually haven't purchased mine yet but I had high hopes for this device. Was going to be my first carrier-supplied phone. I guess I'll wait for the oneplus 2 if this doesn't get sorted out.

Has anyone been able to get:
Code:
adb devices
I keep getting error: device not found when trying to talk to my G4.
Yes, I have adb set up correctly.
Yes, I have tried different USB cables, including the stock white LG cable.
Yes, I have updated the SDK Tools to 24.3 (latest) and Android 5.1.1. I can get adb to talk to my N7, S4, and my M8 fine. Just not my G4.
Yes, I have USB debugging enabled on the phone.

barcodelinux said:
Has anyone been able to get:
Code:
adb devices
I keep getting error: device not found when trying to talk to my G4.
Yes, I have adb set up correctly.
Yes, I have tried different USB cables, including the stock white LG cable.
Yes, I have updated the SDK Tools to 24.3 (latest) and Android 5.1.1. I can get adb to talk to my N7, S4, and my M8 fine. Just not my G4.
Yes, I have USB debugging enabled on the phone.
Click to expand...
Click to collapse
You need to install the LG device drivers first

has anyone tried to get into the bootloader on linux? a couple phones i had, you had to use sudo, then type the absolute path to platform-tools, even if you open terminal within the sdk, I.E.,
sudo /home/username/SDK/platformtools/fastboot oem unlock " or adb reboot-bootloader"
sometimes had to use su, im sure you could do the same on windows.
anyway worth a shot.

H815 - International variant here with me can officially use adb reboot bootloader
fw: V.10A

So far i got this but after this pc won't recognize phone have to reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://imageshack.us/i/exlSOF19j

Worked for me on my LG-H815... It's possible to check the status of the bootloder.
Mine says it's locked. Now there's an option to: "fastboot flash unlock unlock.bin"
But where is the unlock.bin file?

[GUIDE] [OREO 8.0] ROOT + TWRP + DRM Fix | DOCOMO S0-01J | 41.3.B.2.2

***NOTE***
I am not responsible if your device explodes during the process. So Please READ carefully before proceeding.
Put all the flashable zip files on your external storage before you start the procees to avoid delay.
And make sure your bootloader unlockable is allowed.
I created this guide for the Docomo version of Xperia XZ Oreo 8.0 users and I am having difficulty flashing the global version.
Since there is no ftf file for XZ Docomo's, here is the short guide for rooting it.
Watch the tutorial on YouTube :
https://youtu.be/v1mWauNkXg8
1.) Downgrade your XZ to Marshmallow, here is the link for the Japanese firmware https://ftf.andro.plus/ you may use the version 39.0.B.0.361.
And backup your TA.img.
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
2.) Update your SO-01J to Oreo 8.0 via Xperia Companion (since no ftf for Oreo) and unlocked your bootloader.
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
*Make sure that the OEM Unlocking in Developer Option is ON
If you encounter some errors during the process, I suggest you should have the latest 39.2.B.0.336 Docomo firmware and the two (2) files from Xperia companion for Oreo update. You can grab the file before proceeding to update the process.
file location:
C:\Users\zed\AppData\Local\Temp\xperiacompanion\deltaupdates
3.) install the latest TWRP from here
https://dl.twrp.me/kagura/
Code:
fastboot flash recovery TWRP.img
and factory reset via TWRP[to eliminate the password entry during bootup] then flash the patcher by @AdrianDC.
https://forum.xda-developers.com/xperia-xz/development/mod-sony-stock-patcher-xperia-xz-t3576493. I attached the zip I used below.
4.) pull the kernel.img via adb or terminal via TWRP. I prefer TWRP, and make sure to use an external SDcard since the internal storage is not mounted at this moment.
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard1/kernel.img
5.) use the rootkernel V5. 23 (unofficial 2.5) by @serajr to patch your kernel.img
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
Here's the link of patched Docomo's stock Oreo 8.0 kernel 41.3.B.1.140 and 41.3.B.2. 2:
***41.3.B.2.2***
https://drive.google.com/file/d/1eKsvM7s9j8RbEDK8xLUEhrfGi-NcU9Zf/view?usp=sharing
***41.3.B.1.140***
https://drive.google.com/file/d/1tSrOG-pReY-nZtXQWDoDrZXC6qsAcuLL/view?usp=sharing
6.) flash the created boot.img using fastboot and restart to boot up (please be patient).
Code:
fastboot flash boot boot.img
7.) install safetyNet cleaning Tool, DRMFix and magisk to root your device.
8.) all done.
Credits:
@serajr @AdrianDC
@tobias.waldvogel
****And please click thumbs-up if it works ****
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

But my xz is global version

Innearo said:
But my xz is global version
Click to expand...
Click to collapse
There is a separate thread for rooting the Global variant. You may check that one.

donedos said:
There is a separate thread for rooting the Global variant. You may check that one.
Click to expand...
Click to collapse
Why doesn't the firmware that I am gonna flash display in the directory when I use flashtool to flash firmware?

I cannot do the unlock bootloader.
The status says:
bootloader unlock allowed: no

blackerpaper said:
I cannot do the unlock bootloader.
The status says:
bootloader unlock allowed: no
Click to expand...
Click to collapse
you must sim unlock(openline to all carriers) your device to make the bootloader unlockable.

wondering you howto unlock bootloader? My phone got simlock unlock long long ago, but my bootload still locked.

donedos said:
you must sim unlock(openline to all carriers) your device to make the bootloader unluckable.
Click to expand...
Click to collapse
I believe i have sim unlock (all carrier). I use other operator than docomo, and its working.
This is the status from Service Info
Sim Card IMSI:
[ ] Network 0
[ ] Network subset 0
[ ] Service provider 0
[ ] Corporate 0
[ ] SIM 0
. . .

moonjourney said:
wondering you howto unlock bootloader? My phone got simlock unlock long long ago, but my bootload still locked.
Click to expand...
Click to collapse
Bootloader and sim unlock are 2 different things. You can unlock sim but have bootloader locked and vice versa and any combination as they are not the same thing.
PS, I added hide tags to your posts as the images were rather large, I hope you don't mind

gregbradley said:
Bootloader and sim unlock are 2 different things. You can unlock sim but have bootloader locked and vice versa and any combination as they are not the same thing.
PS, I added hide tags to your posts as the images were rather large, I hope you don't mind
Click to expand...
Click to collapse
I know. I think all the DOCOMO phones can't allow to unlock bootloader, isn't it?

moonjourney said:
I know. I think all the DOCOMO phones can't allow to unlock bootloader, isn't it?
Click to expand...
Click to collapse
Apparently not, the OP of this thread includes unlocking the bootloader in its instructions. However, if your bootloader says
'Bootloader unlock allowed:No'
Then there is NO way to unlock your bootloader.

What rom MM ver are u use to dowgrade? I can find it where? sorry for my english

gregbradley said:
Bootloader and sim unlock are 2 different things. You can unlock sim but have bootloader locked and vice versa and any combination as they are not the same thing.
PS, I added hide tags to your posts as the images were rather large, I hope you don't mind
Click to expand...
Click to collapse
Yes, I agree that sim unlocking a and bootloader unlocking are two different things. But regarding Rooting Status, specifically on "Bootloader unlock allowed" maybe they have in common.
I have an Xperia Z5 Au before a carrier locked, and it says "Bootloader unlock allowed = NO". But when I unlocked the carrier using flashmode (not thru code), the status changed "Bootloader unlock allowed = YES", from no to yes.
So it has a relation between the sim unlocking (depends on the method) and allowing the bootloader to be unlocked. But then again, unlocking the bootloader is different from sim unlocking.

Daikii said:
What rom MM ver are u use to dowgrade? I can find it where? sorry for my english
Click to expand...
Click to collapse
I updated step 1, use 39.0.B.0.361.

donedos said:
I have an Xperia Z5 Au before a carrier locked, and it says "Bootloader unlock allowed = NO". But when I unlocked the carrier using flashmode (not thru code), the status changed "Bootloader unlock allowed = YES", from no to yes.
Click to expand...
Click to collapse
If this is true, you are the ONLY person that I have ever heard that has changed this status without asking Sony or the carrier to do it.

gregbradley said:
If this is true, you are the ONLY person that I have ever heard that has changed this status without asking Sony or the carrier to do it.
Click to expand...
Click to collapse
As have you stated, only the carrier or sony can allow this process. I don't know the method of Sony, but for the carrier, they provide us codes and the other one is thru flashmode using a sim unlocking tool which I am using(it's paid though). Or maybe the sim unlocking tool comes from sony(just guessing here).

This is the first time i bought docomo phone, and i hate it very much. What the fak is this bootloader locking. Xioami also do that, but they give the unlock for free, its just that when we unlock it, the guarantee become invalid. I don't care about the guarantee, i unlock just 3 days after bought it. This is gonna be the last time i bought from docomo, never bought it again.
Phone which cannot be customized, is same like nokia 6600 in the past. Only good to fight thief by throwing it straight to the head lol.

donedos said:
As have you stated, only the carrier or sony can allow this process. I don't know the method of Sony, but for the carrier, they provide us codes and the other one is thru flashmode using a sim unlocking tool which I am using(it's paid though). Or maybe the sim unlocking tool comes from sony(just guessing here).
Click to expand...
Click to collapse
This is very interesting. Unfortunately I have unlocked the SIM card with the code provided by Docomo. Of course the Bootloader unlock is still set on No. I guess there is no way to reverse the SIM unlock and then use your method?

Temaki said:
This is very interesting. Unfortunately I have unlocked the SIM card with the code provided by Docomo. Of course the Bootloader unlock is still set on No. I guess there is no way to reverse the SIM unlock and then use your method?
Click to expand...
Click to collapse
I can't guarantee you that it will work but you can try it. but it's not free and you need to buy the credit around 20$~25$.
I guess it may work. because it worked with my Z5 Au(regarding bootloader unlocking allowed).
I believe the tool was introduced here on xda in one of the xperia thread long time ago and it's now being used for business purposes..

donedos said:
I can't guarantee you that it will work but you can try it. but it's not free and you need to buy the credit around 20$~25$.
I guess it may work. because it worked with my Z5 Au(regarding bootloader unlocking allowed).
I believe the tool was introduced here on xda in one of the xperia thread long time ago and it's now being used for business purposes..
Click to expand...
Click to collapse
You're very lucky sir. I think you the first one who can actually unlock the bootloader of docomos.

Galaxy S8 SM-950F Stuck on Logo, FRP LOCK: On OEM Lock: On

Hello guys.
My friend was trying to inject TWRP from Odin to his S8. But as guessed it is failed and now the phone is stuck on Logo and doesn't boot. So, as you see from the title,frp and oem locks are in position "on". What should i do? Since FRP lock is on everything i tried on Odin failed as i expected.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm currently desperate and need some advice how do i fix the phone. Since he doesn't have any backup phone i'm trying my best. Thanks already!

Arda A. said:
Hello guys.
My friend was trying to inject TWRP from Odin to his S8. But as guessed it is failed and now the phone is stuck on Logo and doesn't boot. So, as you see from the title,frp and oem locks are in position "on". What should i do? Since FRP lock is on everything i tried on Odin failed as i expected.
I'm currently desperate and need some advice how do i fix the phone. Since he doesn't have any backup phone i'm trying my best. Thanks already!
Click to expand...
Click to collapse
Dude first off did you activated oem unlock in developer settings (does this Samsung even have a unlocked bootloader) Since you messed up patching twrp to the recovery you need to reflash stock firmware run the setup wizard after its done go in developer settings and make sure oem unlock is activated or more important is the option even present?
(alright its thier I didn't see the F in your model number)
([emoji88]Chaos GSI[emoji88])

PoochyX said:
Dude first off did you activated oem unlock in developer settings (does this Samsung even have a unlocked bootloader) Since you messed up patching twrp to the recovery you need to reflash stock firmware run the setup wizard after its done go in developer settings and make sure oem unlock is activated or more important is the option even present?
(alright its thier I didn't see the F in your model number)
([emoji88]Chaos GSI[emoji88])
Click to expand...
Click to collapse
First of all, my friend did nothing about unlocking oem (you can see from the picture i uploaded, both oem and frp locks are active). He didn't even searched about it . I don't think the bootloader also unlocked. So its pretty messed up right now. I actually tried flashing both android 8 and 9 with different variations, odin always failed. If at least oem was unlocked i think i would do something but, i have no idea waht to do.

Arda A. said:
First of all, my friend did nothing about unlocking oem (you can see from the picture i uploaded, both oem and frp locks are active). He didn't even searched about it . I don't think the bootloader also unlocked. So its pretty messed up right now. I actually tried flashing both android 8 and 9 with different variations, odin always failed. If at least oem was unlocked i think i would do something but, i have no idea waht to do.
Click to expand...
Click to collapse
Is thier a android 10 option......
([emoji88]Chaos GSI[emoji88])

PoochyX said:
Is thier a android 10 option......
([emoji88]Chaos GSI[emoji88])
Click to expand...
Click to collapse
Galaxy S8 didn't get android 10 update unfortunately. I'm still thinking that the problem that causes failed flashes comes from probably the roms i have. But i'm downloading from samdb, when it is downloaded i'll try that and it will probably work i assume.

Arda A. said:
Galaxy S8 didn't get android 10 update unfortunately. I'm still thinking that the problem that causes failed flashes comes from probably the roms i have. But i'm downloading from samdb, when it is downloaded i'll try that and it will probably work i assume.
Click to expand...
Click to collapse
Alright let me know the progress your friend shouldn't tinker without the proper knowledge cause now that expensive phone just a piece of metal once he has twrrp installed he should be protected from this happening again cause then again twrp is a modders best friend
([emoji88]Chaos GSI[emoji88])

PoochyX said:
Alright let me know the progress your friend shouldn't tinker without the proper knowledge cause now that expensive phone just a piece of metal once he has twrrp installed he should be protected from this happening again cause then again twrp is a modders best friend
([emoji88]Chaos GSI[emoji88])
Click to expand...
Click to collapse
You are completely right sir. Personally, every phone i had for 5 years were all modded and i always do my search before doing anything. What he did was a really big mistake and he could've asked me. At least he took a lesson from happened to him :laugh:
I just took his phone to my home and connected to my pc, i flashed the stock rom without any problem. I decided to root his phone by myself. I don't think he should attempt to do this kind of critical operations alone . Thanks for the help!
I also have another question; he had a backup of his files and apps using Smart Switch. If i root his phone, i know kies and smart switch doesn't work with updating phones. But can it restore the backup on a rooted phone?

Arda A. said:
You are completely right sir. Personally, every phone i had for 5 years were all modded and i always do my search before doing anything. What he did was a really big mistake and he could've asked me. At least he took a lesson from happened to him [emoji23]
I just took his phone to my home and connected to my pc, i flashed the stock rom without any problem. I decided to root his phone by myself. I don't think he should attempt to do this kind of critical operations alone . Thanks for the help!
I also have another question; he had a backup of his files and apps using Smart Switch. If i root his phone, i know kies and smart switch doesn't work with updating phones. But can it restore the backup on a rooted phone?
Click to expand...
Click to collapse
I don't believe so... Hope he learned his lesson from this
([emoji88]Chaos GSI[emoji88])

Question URGENT! Nothing Phone stuck in fastboot after DSU loader

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi. i was curious about the DSU loader so i installed it and rebooted. But it started bootlooping then showed the "system is corrupt" message. After that it rebooted and only went into fastboot after that, Im a bit panicked since the phone is only a couple hours old and I forgot to unlock the bootloader. if anyone knows how to fix this itd be appreciated.

I did quite a lot of flashing and rooting and as far as I know, there should be an option withing fastboot to reboot to bootloader. But I am not aware of the Nothing recovery image.
When in bootloader, you can then unlock the device with fastboot commands via command line.
Have you tried any of that?

miris83 said:
I did quite a lot of flashing and rooting and as far as I know, there should be an option withing fastboot to reboot to bootloader. But I am not aware of the Nothing recovery image.
When in bootloader, you can then unlock the device with fastboot commands via command line.
Have you tried any of that?
Click to expand...
Click to collapse
sadly doesnt work since oem unlocking is off, and i cant access the os. it seems its in slot b right now, but i cant switch slots due to a locked bootloader.
any ideas would help

why use DSU?if you are stupid in this matter? say goodbye to the phone

Curiosity got the best of me. I used DSU cause I thought I would be able to keep it locked

Seaman228 said:
why use DSU?if you are stupid in this matter? say goodbye to the phone
Click to expand...
Click to collapse
Why do you trash the topic with anything but any attempt for help? Drop the keyboard and take a walk.

Someone had to say it

miris83 said:
Why do you trash the topic with anything but any attempt for help? Drop the keyboard and take a walk.
Click to expand...
Click to collapse
Trash? I told the truth, if you're crying I'm sorry

You really forgot rule 1 in android modding.
Unlock.
The.
****ing Bootloader.

Seaman228 said:
Trash? I told the truth, if you're crying I'm sorry
Click to expand...
Click to collapse
And even more trash ... You are a waste of time, man.

gordonsosig said:
View attachment 5711879Hi. i was curious about the DSU loader so i installed it and rebooted. But it started bootlooping then showed the "system is corrupt" message. After that it rebooted and only went into fastboot after that, Im a bit panicked since the phone is only a couple hours old and I forgot to unlock the bootloader. if anyone knows how to fix this itd be appreciated.
Click to expand...
Click to collapse
As I see it now, this might be your best bet at this point: https://forum.xda-developers.com/t/...t-centre-and-staff-14-september-2022.4492645/
The staff is pretty friendly. I already reported some bugs and it was just fine.

Use "fastboot getvar current-slot" to get your current slot then switch to the other slot with "fastboot --set-active=a" or "fastboot --set-active=b" I believe those commands work even with a locked bootloader.

Seaman228 said:
why use DSU?if you are stupid in this matter? say goodbye to the phone
Click to expand...
Click to collapse
it's Nothing's fault for screwing up their DSU implementation. On a locked bootloader it should either boot the DSU image (like Pixel), or reject it and boot back to normal system. In NO CIRCUMSTANCES it should BRICK the device like this
Google didn't mention the best way to install the Android 12 Beta on Pixel phones
DSU is the best way to install the Android 12 Beta release on Pixel phones, but Google totally neglected to mention it.
www.xda-developers.com
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.

nguyenlucky said:
it's Nothing's fault for screwing up their DSU implementation. On a locked bootloader it should either boot the DSU image (like Pixel), or reject it and boot back to normal system. In NO CIRCUMSTANCES it should BRICK the device like this
Google didn't mention the best way to install the Android 12 Beta on Pixel phones
DSU is the best way to install the Android 12 Beta release on Pixel phones, but Google totally neglected to mention it.
www.xda-developers.com
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
Click to expand...
Click to collapse
sadly i live in switzerland so there isnt any service center i can get to. so either we find a solution or the phone collects dust on my shelf

nguyenlucky said:
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
Click to expand...
Click to collapse
On the other hand the MSM tool may exist only as an internal tool which they might provide on request in such situations. As you pointed out in the article, they messed up the implementation. To be honest, I wonder how this may have happened in the first place - to boot into mode which should not be available with the booloader unlocked. And given the company has a past link with OnePlus and OnePlus does have an MSM tool ...
Unless @gordonsosig asks the support, he will not know.

Have a look here : https://forum.xda-developers.com/t/nothing-phone-1-flashing-utilities.4478457/
And there : https://forum.xda-developers.com/t/help-to-developers.4484061/

I also went into this issue with disabled OEM Unlock. My phone was repaired for free in the customer care because I had an warranty. I wrote an email about this issue to the producer because I think it should not be possible to hard brick the phone by playing with developer options. I hope they will fix it.
And I think moderator should pin this thread to be always on top, because people should see the varning, this can save users from bricking their phones.

kuba3351 said:
I also went into this issue with disabled OEM Unlock. My phone was repaired for free in the customer care because I had an warranty. I wrote an email about this issue to the producer because I think it should not be possible to hard brick the phone by playing with developer options. I hope they will fix it.
Click to expand...
Click to collapse
where do i send it? is it in person or mail in? any help is appreciated

I returned my phone into the place where I buy it, and they sent it to the customer care. There is an official website: https://pl.nothing.tech/ so I think you can find an information about how to send your phone or use an Contact us link and I think they will help you.

kuba3351 said:
I returned my phone into the place where I buy it, and they sent it to the customer care. There is an official website: https://pl.nothing.tech/ so I think you can find an information about how to send your phone or use an Contact us link and I think they will help you.
Click to expand...
Click to collapse
guess im ****ed. already contacted them but i bought the phone from ebay so they said just contact ebay