Related
Bought my Huawei G520 direct from China
Never occured to me that it would have no access to google apps
Anyway I found out the bootloader was also locked so i couldn't flash anything (except for those complete roms with INSTALL file)
Sent an email to Huawei with phone details requesting the code to unlock the bootloader
They sent me the code the very next day!!!
With the message "Thanks for supporting Huawei"
Brilliant
but my hopes were soon dashed - the phone *still* wont root??????????????????
I must of tried 10 different root methods and how I haven't bricked it I'll never no - but they all fail at some point
I mean, the bootloader is now definitely UNlocked, (it reports UNLOCKED and used to report LOCKED), it even has clockwork mod on it some how and it works fine, but any attempt to install roms fail
I have Rom Explorer on the phone and that quite clearly says the phone is not rooted???
I dont know whats going on?
Any ideas what else might be locked on it?
JethroUK said:
Bought my Huawei G520 direct from China
Never occured to me that it would have no access to google apps
Anyway I found out the bootloader was also locked so i couldn't flash anything (except for those complete roms with INSTALL file)
Sent an email to Huawei with phone details requesting the code to unlock the bootloader
They sent me the code the very next day!!!
With the message "Thanks for supporting Huawei"
Brilliant
but my hopes were soon dashed - the phone *still* wont root??????????????????
I must of tried 10 different root methods and how I haven't bricked it I'll never no - but they all fail at some point
I mean, the bootloader is now definitely UNlocked, (it reports UNLOCKED and used to report LOCKED), it even has clockwork mod on it some how and it works fine, but any attempt to install roms fail
I have Rom Explorer on the phone and that quite clearly says the phone is not rooted???
I dont know whats going on?
Any ideas what else might be locked on it?
Click to expand...
Click to collapse
It sounds like a filesystem issue, maybe a hardware problem, like bad flash memory. Are you able to install apps and copy files to it?
Did you install CWM, or did it come with it?
electromage said:
It sounds like a filesystem issue, maybe a hardware problem, like bad flash memory. Are you able to install apps and copy files to it?
Did you install CWM, or did it come with it?
Click to expand...
Click to collapse
I think cwm just appeared after running one of the rooting tools
Have no trouble installing apps and copying files over
Hello,
I messed with my Pixel phone and now I feel it bricked. It was working fine until I update it to 8.0 Oreo. Then I rooted it using magisk.
Later, I decided to re-lock my bootloader, which was really a big mistake. I did re-lock it using the following command:
fastboot oem lock
It showed me if I lock my bootloader, it would wipe everything. I hit yes.
After that, this issue started, my phone won't start, as soon as the google logo shows up, it restarts and does the same thing everytime.
I tried to install the factory image, "sailfish" for Pixel 8.1.0, using the following command:
flash-all
it gave me an error message. It said I need to unlock the bootloader.
Of course, I tried to unlock the bootloader using the following command:
fastboot flashing unlock
It also gave me an error message, it said:
FAILED (remote: oem unlock is not allowed)
I don't know what else should I do. I tried to find a solution for my problem, but there is no clear answer.
One of the common solution is to enable the USB debugging/OEM unlocking from the developer settings. But, again, I can't even turn on my phone and use it normally.
The only thing that I can access to is the bootloader screen.
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
KittyRgnarok said:
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
Click to expand...
Click to collapse
You are totally right. I'll contact them to RMA my phone.
hamooz92 said:
You are totally right. I contact them to RMA my phone.
Click to expand...
Click to collapse
Good luck. Update the thread with the results cuz I'm curious if they will rma a phone bricked like that
Hi there:
I’ve got a second-hand Pixel 1 last week, I unlocked, installed TWRP and rooted yesterday, but I unrooted today because some reasons.
I did a wrong decision, I erased the phone by System Settings, and locked it.
After I locked it, when I boot it, it only have Google logo flash for about 0.1second then gone. I tried to flash the factory images from Google, but it requires unlock to flash it.
I even can’t unlock it now because I can’t get into the System to turn on “Allow unlock OEM loader”, so it got failed. I used fastboot OEM unlock and fast flashing unlock, they both doesn’t work.
I don’t really want to send the phone back to Google US because I doesn’t live in America, so it’s not really easy and really expensive to send it, and I also really need this phone because the battery of my old phone is almost dead. And the Google Support Team in my country/region says that I can’t send to the repair center locally because they only accept Pixel 3/3XL/3a/3aXL/4/4XL
Thanks the suggestions from you guys!
I have a similar issue.
I unlocked the bootloader via ADB but I couldn't even get a copy of TWRP to work at all. The phone also eventually stopped working on the stock install too but taking the option it presented of doing a full wipe and reset fixed at least THAT part.
Still can't get TWRP or Lineage up on it :/
Reboot to fastboot mode and flash stock recovery image (according to your os version).
Sorry for making another thread so soon, but I've got new issues now. TL;DR, I'm just trying to get my Moto G7 Power to detect my sim card at *all* anymore. I've been told that installing an OTA will make the phone detect the sim card again, but... I can't re-lock my bootloader.
I've spent pretty much all day looking for ways to re-lock it, but not a single one has worked. I always get the same "Still waiting for signed boot.img" message, even when I try fixes that worked for others. At this point, I give up on trying to re-lock. I just rooted using a guide here and connected to WiFi.
The next best thing would be for me to find another way to install OTAs. I've heard Magisk used to be able to hide your bootloader status and let you do that, but can't anymore, so...
1. Is there a way for me to install official android updates manually? If so, how?
2. If there is, *where* do I find the updates?
T-Mobile [PCO29.114-54-2]
XT1955-5
Tsukomasi said:
Sorry for making another thread so soon, but I've got new issues now. TL;DR, I'm just trying to get my Moto G7 Power to detect my sim card at *all* anymore. I've been told that installing an OTA will make the phone detect the sim card again, but... I can't re-lock my bootloader.
I've spent pretty much all day looking for ways to re-lock it, but not a single one has worked. I always get the same "Still waiting for signed boot.img" message, even when I try fixes that worked for others. At this point, I give up on trying to re-lock. I just rooted using a guide here and connected to WiFi.
The next best thing would be for me to find another way to install OTAs. I've heard Magisk used to be able to hide your bootloader status and let you do that, but can't anymore, so...
1. Is there a way for me to install official android updates manually? If so, how?
2. If there is, *where* do I find the updates?
T-Mobile [PCO29.114-54-2]
XT1955-5
Click to expand...
Click to collapse
Retus one u need to flash do u have the bat file? Try flashing the modem non -hlos.bin in fastboot mode
You can install OTAs with unlocked bootloader, but you'll need to unroot your device first
Sorry for being 2 weeks late, but you look like you're in the exact same position I once was. Flashing an official update for my channel, available at https://mirrors.lolinet.com/firmware/moto/ocean/official/ was what solved it for me, for whatever reason. (my SIM also wasn't recognized at all, nor did I have any IMEIs outside of bootloader. Also, the option to enable OEM unlocking never became available to me, despite instantly being available when I solved it)
We're technically able to install OTAs with unlocked bootloaders? But for some reason mine throws up an error at step 3/6 every time, so I'm dependant on Lolinet to install them.
On relocking bootloader, you had to re-flash boot.img, run the command 3 times, re-flash and run the command again or something, I was also going to try that on one of my threads, but since I couldn't enable OEM unlocking.
Hyoretsu said:
Sorry for being 2 weeks late, but you look like you're in the exact same position I once was. Flashing an official update for my channel, available at https://mirrors.lolinet.com/firmware/moto/ocean/official/ was what solved it for me, for whatever reason. (my SIM also wasn't recognized at all, nor did I have any IMEIs outside of bootloader. Also, the option to enable OEM unlocking never became available to me, despite instantly being available when I solved it)
We're technically able to install OTAs with unlocked bootloaders? But for some reason mine throws up an error at step 3/6 every time, so I'm dependant on Lolinet to install them.
On relocking bootloader, you had to re-flash boot.img, run the command 3 times, re-flash and run the command again or something, I was also going to try that on one of my threads, but since I couldn't enable OEM unlocking.
Click to expand...
Click to collapse
Every OTA zip first verifies your entire system by checksums. Is there any modified partition the verifier fails and the update process ends with an error.
WoKoschekk said:
Every OTA zip first verifies your entire system by checksums. Is there any modified partition the verifier fails and the update process ends with an error.
Click to expand...
Click to collapse
Probably my Magisk then, but meh
Hi everyone, to add some background I am fairly familiar with flashing this device as I have had it for 3 years and have done a lot of tinkering with it. However this does not mean I am good, and I have definitely soft bricked this phone a lot over the years, but today I think I finally hard bricked it.
Basically, I was using stock MIUI but with TWRP recovery and wanted to add my card to Google Pay, however it said my device was not secure (or something) so I thought it must be because I don't have fully stock MIUI. So I decided to see some way to return the stock recovery, and after doing 5 minutes of research I saw that I could flash the stock ROM and then through fastboot run "fastboot oem lock" which would reset it to stock. However I definitely did something wrong because after rebooting into recovery it says "The system has been destroyed, Press power button to shutdown", and the phone will not boot normally anymore.
You might now suggest that I should unlock my bootloader again through Mi account, but the problem is that I wasn't logged into my Mi account, so I think this is impossible. I have tried running "fastboot oem unlock", but that obviously returns an error when I tried.
Is there any hope to recover this device or is it gone forever? I would appreciate any advice. If you need more info please just ask.
Thanks!
futiiile said:
Hi everyone, to add some background I am fairly familiar with flashing this device as I have had it for 3 years and have done a lot of tinkering with it. However this does not mean I am good, and I have definitely soft bricked this phone a lot over the years, but today I think I finally hard bricked it.
Basically, I was using stock MIUI but with TWRP recovery and wanted to add my card to Google Pay, however it said my device was not secure (or something) so I thought it must be because I don't have fully stock MIUI. So I decided to see some way to return the stock recovery, and after doing 5 minutes of research I saw that I could flash the stock ROM and then through fastboot run "fastboot oem lock" which would reset it to stock. However I definitely did something wrong because after rebooting into recovery it says "The system has been destroyed, Press power button to shutdown", and the phone will not boot normally anymore.
You might now suggest that I should unlock my bootloader again through Mi account, but the problem is that I wasn't logged into my Mi account, so I think this is impossible. I have tried running "fastboot oem unlock", but that obviously returns an error when I tried.
Is there any hope to recover this device or is it gone forever? I would appreciate any advice. If you need more info please just ask.
Thanks!
Click to expand...
Click to collapse
hi, u can try to unlock again over mi unlock tool not over fastboot command. if u unlocked before your account is maybe still binded with that phone. so u can try unlock first..
Do u have stock mi recovery on it?
Dadovvv said:
hi, u can try to unlock again over mi unlock tool not over fastboot command. if u unlocked before your account is maybe still binded with that phone. so u can try unlock first..
Do u have stock mi recovery on it?
Click to expand...
Click to collapse
Thanks for responding, I will try this as soon as I can get a different phone to receive the SMS for the Mi account. As for the recovery, I'm not really sure what exactly it is because as I said, when I try to boot recovery it just says, "The system has been destroyed".
Hi, I've found that tutorial, but for other Redmi model, still maybe helpful:
Derenk said:
Hi, I've found that tutorial, but for other Redmi model, still maybe helpful:
Click to expand...
Click to collapse
this is not helpful since u have locked bootloader, video is fake, it is just flashing fastboot rom by cmd nothing else.
Had this same problem a few months ago, just try to unlock the phone again using mi unlock. After unlocking quickly install a custom recovery and you should be good.
Thanks for the suggestions guys, I'm in the process of trying to unlock with mi unlock however it says my account is suspended when I try to log in, I will be trying to recover it but I hope it will not cause any issues with unlocking the phone if I change the phone number as part of the recovery process.
Hello again, it would seem that I will not be able to unlock the Mi account that I used to unlock the device originally so I think I am out of options unfortunately. I will look into buying a new phone.
futiiile said:
Hello again, it would seem that I will not be able to unlock the Mi account that I used to unlock the device originally so I think I am out of options unfortunately. I will look into buying a new phone.
Click to expand...
Click to collapse
u can try to open your phone there are pins which u can use to unlock by bridgeing them by wire or something metal then u can try to flash normally dont know if your phone got that option try to find graphics or videos for your phone maby u wll need service account for miflash with more options for flashing
Hi everyone, I got it unlocked by some guys on Telegram as recommended by @NOSS8!