Related
As a friendly reminder to those unfamiliar with unlocking/re-locking their bootloaders;
Unless your on 100% stock, and planning on reselling your phone, don't re-lock the bootloader.
For some reason re-locking the bootloader while you have a custom ROM installed will cause the phone not to boot (in a way, soft bricking it.)
And, leave "OEM unlocking" in the "Developer Options" CHECKED, once that is unchecked you cannot unlock the phone once a soft brick happens.
The official advice from Essential about re-locking your phone is ONLY for the official firmware. Pretend they never said that on their site, it has caused more trouble then necessary. It's even dangerous to re-lock while running the Oreo beta.
Concerning un-bricking the device, at the moment there is no known way.
And it will be this way until someone figures out a way to exploit the bootloader or reverse engineer it.
So please don't flood this thread with asking for help to un-brick your device, I nor anyone else can help you on that at this given time, all I'm doing is trying to is prevent that happening.
So, safe unlocking! And happy holidays!
EDITS:
1) According to some reports, when you lock your bootloader it will also automatically untoggle the "OEM Unlocking" option.
2) It appears when re-locking the phone on a non-stock ROM some partitions are becoming corrupt, and resulting in the "red boot warning" screen. Under most circumstances you can fix that screen, but not while the bootloader is locked (since you need the fastboot flash command.)
3) When the partitions become corrupt you cannot boot into any mode, including the stock recovery. This is why Essential's suggestions are pointless at this stage of the brick.
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
avd said:
Should be pinned and in the OP of every mod thread
Click to expand...
Click to collapse
totally agree, i made this "trick" with one of my first android phone and it never happen me again. But new user who would flash Los or other rom should be aware of this issue, specially when jtag is not an option. As far we'll make some powerfull 500$ brick :crying:. it's our duty to make people aware of this. @invisiblek you guy made an incredible work and so fast but like he said i think you should warn people of the risk in the OP
avd said:
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Ellises said:
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Click to expand...
Click to collapse
It's very easy to ask for a thread to get stuck to the top.
Just use the report post button, and ask, whether or not becomes a sticky is up to the Mods.
How to Report a Post.
Sent from my XT1254 using XDA Labs
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
ericzhf said:
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
Click to expand...
Click to collapse
Ellises said:
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
Click to expand...
Click to collapse
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
ericzhf said:
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
Click to expand...
Click to collapse
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
tech_head said:
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
Click to expand...
Click to collapse
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
ericzhf said:
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
Click to expand...
Click to collapse
FDR is not "back to stock".
You must to a full flash to get back to stock.
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Ellises said:
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Click to expand...
Click to collapse
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
I could also mention on their stock build page it wants you to unlock the bootloader to manually update through the bootloader. But on the oreo beta page it mentions nothing about having to be unlocked, or locked to do it via the stock recovery. So the average user could presume they need to be unlocked.
NaterTots said:
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
Click to expand...
Click to collapse
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
No.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Obamaloominaty said:
No.
Click to expand...
Click to collapse
tech_head said:
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Click to expand...
Click to collapse
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
WiddleyScudds said:
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
Click to expand...
Click to collapse
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
tech_head said:
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
Click to expand...
Click to collapse
I just got an ota notification for OPM1. 180104.092. think I'll be safe I I take it, then factory reset and then lock? Because I can't seem to locate stock NMK24B to flash. Maybe I'm not looking hard enough .
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
post-mortem said:
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Click to expand...
Click to collapse
That unfortunatly doesn't work. It's only for unlocked or at least unlockable deviced. I still tried it, but most fastboot commands require the bootloader to be unlocked. flashing unlock, flashing unlock_critical oem unlock, flash, format, boot, --set-active all don't work with a non-unlockable bootloader.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Click to expand...
Click to collapse
Also fails with 'oem unlock is not allowed'.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
Click to expand...
Click to collapse
Fails with 'Command is not supported. Please unlock device to enable this command.'
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
junglism93 said:
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
Click to expand...
Click to collapse
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Marvin0509 said:
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Click to expand...
Click to collapse
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Sent from my Pixel using XDA Labs
junglism93 said:
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Click to expand...
Click to collapse
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
Definitely seems a non recoverable scenario and happy days on getting it RMA'd for free :good:
Sent from my Pixel using XDA Labs
Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
It's over a year old right?? And they RMAed it for free?
aholeinthewor1d said:
It's over a year old right?? And they RMAed it for free?
Click to expand...
Click to collapse
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Marvin0509 said:
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Click to expand...
Click to collapse
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
post-mortem said:
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
Click to expand...
Click to collapse
No, I told them the whole truth, that I rooted it, modified the system, and that it doesn't work at all anymore.
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
HeinrichSpy said:
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
Click to expand...
Click to collapse
I have a subscription for Google One, so I contacted support from one.google.com. They quickly talked to me, then added a Pixel support employee to the conversation. I think I could have also contacted Pixel support directly on this page: support.google.com/pixelphone/contactflow. However I'm not sure if this will work in your country, I'm from Germany and the page wants me to select my Pixel, then I could contact a support employee via chat or wait for a callback, but if I change the language to English, the page seems broken and is just blank.
Marvin0509 said:
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
Click to expand...
Click to collapse
i tried flashing a stock ota image...it was successful, but on reboot, nothing has changed. still the same. u know of a solution? i cant find it anywhere. thanks
Hi good people at XDA. This is my first post on this website and I am absolutely hoping to receive help from you all to find a way out of the depressing and extremely anxious situation I'm in.
I was using my OP6 normally today and while I was typing something on Telegram the phone suddenly froze and after I re-booted it, it took me to the Qualcomm Crashdump screen.
My OP6 isn't tampered in any way (no bootloader unlocked, no TWRP recovery installed, nothing rooted).
At the moment, I can enter the fastboot mode while pressing volume up and power button.
The crucial thing is the data which I MUST RETRIEVE, can't afford to lose it.
Could y'all please suggest a way where the data can be retrieved or the phone can be revived without data loss?
I did read the forums on MSMDownload Tool but I believe it wipes off the phone, right?
PLEASE HELP!
If ADB ( read: USB Debugging ) got enabled on phone - what is the door to Android OS - then try this to pull out user-data stored on phone
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
jwoegerbauer said:
If ADB ( read: USB Debugging ) got enabled on phone - what is the door to Android OS - then try this to pull out user-data stored on phone
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
Click to expand...
Click to collapse
Thanks @jwoegerbauer for the prompt response. I can surely try that. Considering that I'm fairly a noob, could you please share in a bit detail, the steps I need to take before executing those commands?
Also, since there's a tiny chance that USB Debugging may not have been enabled, what's the alternative that I consider?
Thanks!
Since I must retrieve the data in internal SD, can this help me enter the OS?:
1. Extracting the boot.img of the latest version that's currency installed on my OP6, from payload.bin
2. Testing if this boot.img can revive me into the OS by fastboot boot boot.img.
Also, one pressing doubt: does a fastboot flash boot boot.img command erase internal SD contents??
Please help!
Any help, anyone?
pagan_1 said:
Any help, anyone?
Click to expand...
Click to collapse
My friend has the same problems. Did you find any ways to retrive data? I found a way to use msm tool but it surely erases all data and its his college memories so I'm trying to find alternate ways. Does the msm tool work on bootloader locked phones?Sorry that I am of no help to you. I too am a novice
KannanSathyanarayanan said:
My friend has the same problems. Did you find any ways to retrive data? I found a way to use msm tool but it surely erases all data and its his college memories so I'm trying to find alternate ways. Does the msm tool work on bootloader locked phones?Sorry that I am of no help to you. I too am a novice
Click to expand...
Click to collapse
No man. Still looking for some solutions. Read umpteen threads only to see that MSMDownload Tool erases data because it first unlocks bootloader (which mandatorily wipes data), flashes system files and then relocks it.
But I'm pretty sure, there exists some way out to flash a OP 6 with locked bootloader but retaining userdata partition intact.
Hoping to receive some solution here from this community of Android geeks.
pagan_1 said:
No man. Still looking for some solutions. Read umpteen threads only to see that MSMDownload Tool erases data because it first unlocks bootloader (which mandatorily wipes data), flashes system files and then relocks it.
But I'm pretty sure, there exists some way out to flash a OP 6 with locked bootloader but retaining userdata partition intact.
Hoping to receive some solution here from this community of Android geeks.
Click to expand...
Click to collapse
Hey man, were you able to do anything abut it? I'm in the exact same situation. Don't mind losing the phone if I'm able to save the data.
Smohi said:
Hey man, were you able to do anything abut it? I'm in the exact same situation. Don't mind losing the phone if I'm able to save the data.
Click to expand...
Click to collapse
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
pagan_1 said:
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
Click to expand...
Click to collapse
Oh, that's awesome. I have some hope then. Do you mind telling me what your location is. I'm based out of bangalore and wondering I'll have to take it to your specialist incase I don't find any solution locally. All others have been saying they were asked to replace motherboard by Oneplus service centres. Please let me know of your repair centre as well. I'll try to atleast speak to them. Thank you so much
pagan_1 said:
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
Click to expand...
Click to collapse
How much did it cost? They changed IC and since then your phone is working properly?
pagan_1 said:
Hi. So, I gave my phone to a phone repair specialist. Apparently he changed some IC, which made the phone to boot up to the system. which is what allowed me to take the data backup of the phone.
Click to expand...
Click to collapse
Bro can i have your number please i m stuck with the same problem since last year but not got the solution to boot up my phone normally its always showing crash dump mode. I tried everything but nothing worked for me.
like many even i too ugraged my op6 to oo11.1.1.1, rooted was running well for a week till i encountred face crash dump mode error
Stupid thing i did was instead of flashing fastboot oos 10.3.8 i tried to flash msm 10.3.8 which didnt solve crash dum and also locked my BL.
now nonof the msm could solve crash dump nor we can unlock BL bz we cant toggle OEM in Dev option,
i discussed with @L0ND0NB0Y regarding this, his suggestion would be to take a backup of oos10.3.8 config partation of a working rom, then use edl to flash it on affected op6, by that way we can unlock bootloader and flash fastboot rom.
we need to fide a working op6 and back config which @L0ND0NB0Y can guide us. if it works he ll creat a post to solve crashbump and BL locked issue.
if this wont work, we may need to wait for msm oos11 file.
update : managed to solve crash dump by flashing msm international 5.1.5 but ended up getting black screen with white notification light, if my op6 had BL unlocked all i had to do is to boot stock/twrp recovery and factory wipe.
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
vlc_marcos said:
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
Click to expand...
Click to collapse
No duplicated thread are permitted
Please help us to keep the forums neat
Thanks
vlc_marcos said:
I downloaded the wrong Firmware for the Pixel 5
Click to expand...
Click to collapse
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
l7777 said:
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
Click to expand...
Click to collapse
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
vlc_marcos said:
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
Click to expand...
Click to collapse
when its plugged into a computer does the computer see it at all?
thewraith420 said:
when its plugged into a computer does the computer see it at all?
Click to expand...
Click to collapse
not at all is there some kind of hard unbrick??
vlc_marcos said:
not at all is there some kind of hard unbrick??
Click to expand...
Click to collapse
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
thewraith420 said:
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
Click to expand...
Click to collapse
Mine bricked about a month ago and Google suggested uBreakiFix. They tried to do a force flash on it but it didn't work. They ended up replacing the motherboard which fixed it, but now my proximity sensor is always on. I don't know if they can fix that or if it will require another motherboard.
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
p_a_r_s_a7 said:
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
Click to expand...
Click to collapse
Did you use any special way to even turn on the phone or reach the bootloader?
vlc_marcos said:
Did you use any special way to even turn on the phone or reach the bootloader?
Click to expand...
Click to collapse
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
p_a_r_s_a7 said:
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
Click to expand...
Click to collapse
how did you end up with it like that with bootloader locked? what caused it?
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
But you could reach fastboot right?
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
speo said:
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
Click to expand...
Click to collapse
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
speo said:
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
Click to expand...
Click to collapse
I send back to Google, i couldn't fix it
Cj719 said:
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
Click to expand...
Click to collapse
thank you anyway, it was a little light on the horizon at least ;-)
p_a_r_s_a7 said:
I send back to Google, i couldn't fix it
Click to expand...
Click to collapse
have you been charged ?
Mine is from another dealer, will see..
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
psorincatalin87 said:
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
Click to expand...
Click to collapse
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
V0latyle said:
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
Click to expand...
Click to collapse
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
psorincatalin87 said:
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
Click to expand...
Click to collapse
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
V0latyle said:
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
Click to expand...
Click to collapse
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
psorincatalin87 said:
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
Click to expand...
Click to collapse
I downloaded the firmware with Frija and I get the same issue with Odin.
psorincatalin87 said:
I downloaded the firmware with Frija and I get the same issue with Odin.
Click to expand...
Click to collapse
What options do you have checked in Odin?
V0latyle said:
What options do you have checked in Odin?
Click to expand...
Click to collapse
I haven't touched any of the options, everything is on default.
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
nsfnd said:
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
Click to expand...
Click to collapse
OH.MY.GOD! Thank you very much, man! I love you! I could kiss you right now, stranger!
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
nsfnd said:
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
Click to expand...
Click to collapse
Nah, this is my last one.
psorincatalin87 said:
Nah, this is my last one.
Click to expand...
Click to collapse
don't be that way lol, it's fun, just do it on hardware you own. get a cheap phone off ebay to play with