So last night I managed to root the phone and today tried to lock the bootloader, now I can't turn my phone on. Backup is saved to my PC but i dont know what to do
So managed to unlock the bootloader but now I can't get past my pin code, keeps saying wrong pin
closed as per OP request
Related
Hi,
I either hard-bricked or soft-bricked my phone. It does not turn on, led indicator shows nothing. (It does not even load into bootloader). But when I connect it to my PC it shows up in device manager and let's me access phone's internal storage. So I'm wondering if it's a hard-brick and i'm screwed or do I still have any chances of recovering it?
What happened:
Firstly I was trying to go back to stock with a ruu from ruu.lalleman.net. I've checked my CID and got the correct one.
Then I relocked my phone, after that when I booted into bootloader it showed "RELOCKED" "SECURITY WARNING", but from now my phone wasn't able to boot normally, it booted straight into fastboot.
Now I tried loading the RUU on my sd card as explained here: http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238 But all I've got was an error saying "device halted due to Large Image update fail !"
I figured out that I couldn't install the original RUU because I had the update to MM.
At this point I was fiddling with my phone for a long time so I thought that it needed charging so I tried to boot into recovery just to charge it. It didn't work it booted straight back to fastboot.
Then I tried unlocking my relocked phone via htcdev just to flash any recovery to charge my phone. (this was probably the stupidest decision out of desperation ) After the last step of unlocking, when it asked me if I want to unlock the bootloader I selected "yes" and the phone just vibrated and went black.
If someone has any ideas on how to recover my phone, please help, I'm desperate. :crying:
nevermind, after trying for a while I somehow managed to do "adb reboot".
Hi, my phone has been dead for like 2 weeks now I even did a remote session in which they tried doing the MSMDownloadtool thing and it did nothing, no vibrations, black screen they just said its fully dead. fast forward to today it just started to react again.
When it tries to boot it boots straight to the OnePlus recovery mode and tells me to input a password, obviously I dont have one seen as its been set and if I click forget password it says it will format everything but it just turns off.
After a few boots I managed to get it to fastboot to realise the bootloader is now locked. the bootloader has always been unlocked since the first day I got it so it must of happened during the MSMDownloadTool process but the issue is now I cant unlock the bootloader because it says "remote: oem unlock is not allowed"
Any suggests that preferably not run MSMDownloadtool because thats been ran so many times already. Thanks
Essentially. No OS, Broken recovery, Locked bootloader and MSMDownloadTool doesnt seem to work. I imagine its just fully locked down and finished but its worth a try
First try the MSMDownload tool with the very first stock Oxygen OS
Then re-lock the bootloader using Adb
I had the same problem and now its fine
LJAM96 said:
Hi, my phone has been dead for like 2 weeks now I even did a remote session in which they tried doing the MSMDownloadtool thing and it did nothing, no vibrations, black screen they just said its fully dead. fast forward to today it just started to react again.
When it tries to boot it boots straight to the OnePlus recovery mode and tells me to input a password, obviously I dont have one seen as its been set and if I click forget password it says it will format everything but it just turns off.
After a few boots I managed to get it to fastboot to realise the bootloader is now locked. the bootloader has always been unlocked since the first day I got it so it must of happened during the MSMDownloadTool process but the issue is now I cant unlock the bootloader because it says "remote: oem unlock is not allowed"
Any suggests that preferably not run MSMDownloadtool because thats been ran so many times already. Thanks
Essentially. No OS, Broken recovery, Locked bootloader and MSMDownloadTool doesnt seem to work. I imagine its just fully locked down and finished but its worth a try
Click to expand...
Click to collapse
I think that your only option is to try the MSM Download Tool. You may have to run it for a few times before it succeeds. I bricked my phone and recovered with the Mega Unbrick Guide (at first attempt). Following the instructions to the letter is most important.
So, I had rooted my phone some time ago but also found out that some apps don't run on rooted phones, so I tried to unroot it, but now it is stuck in a light blue screen saying "Security Error"
I have found some solutions online but all of them required to toggle on OEM Unlocking but I toggled off developer options some time ago and I forgot to turn it on before unrooting. So, now I can't access Recovery Mode, only download mode, and can't flash anything on my phone since it always fails because OEM isn't unlocked so Odin fails every time I try to flash my phone.
I hope someone here has a solution because I really need to get my phone working again. And by the way, I'm not that new but also not that knowledgeable in rooting phones and also my first time posting here. Hope someone can help.
Try Samsung Smart Switch
https://www.samsung.com/us/support/owners/app/smart-switch
(Apparently someone faced this problem before, but phone did tell him to get Smart Switch to restore firmware. Wonder why you dont have one)
Sidenote: use Question & Answers.
Everything was running fine, I flashed a ROM, rooted etc. Got everything installed, all was working perfectly. I turned the phone off, came back to it a few days later, now I get the above error when turning the device on.
I have read that I now need to flash the full stock firmware via Odin to unbrick it. I have the latest G960FXXSEFUA1 firmware downloaded and ready to go. How can i make it so I dont get in this situation again?
I was using a GSuite account, and had a screen lock PIN. I wonder if that caused it?
Yesterday, I flashed stock ROM, then set OEM Unlock, and then trioed to flash TWRP. I saw 'Only official released binaries are allowed to be flashed', somewhow i got round it, and got everything set up, custom ROM, the lot. Obviously we know how that ended, i saw the 'custom binary blocked by frp lock'
I've now flashed Stock via Odin, done the OEM unlock bit, it got me to wipe the device. I now turn it on and the OEM Unlock bit has gone.
Download Mode says 'OEM Unlock OFF', and 'KG State Prenormal'.
Do I now have to wait the seven days? Even though ive already done the OEM Unlock and reset the phone?
Is there any way i can flash the firmware with bootloader locked? my device has no mi account logged in so i cant used miunlocktool, i already tried XiaoMiToolV2 but when sideloading update via adb it just goes way over 100% and the device screen stucks at 4.99% then restarts back.
Using miflash it just gives me an error of "erase is not allowed in lock state"
Not absolutely sure, but I don't think there is. Would love to be told I'm wrong though...