I got hold of this perseus which has no mobile signal because previous owner deleted EFS partition by mistake. There is no IMEI, that's why it's not registering on the mobile network. Then again, its bootloader got locked by installing latest stock MIUI 11 global through MiFlashTool. So, I can't get to the point of repairing the IMEI with the stock recovery.
When I try to unlock bootloader it says to authorize the device from developer option, but that authorization requires SIM connectivity. Without sending SMS or without using mobile data it can't authorize the device and it won't let me unlock bootloader.
So here I am stuck with a flagship level phone without any signal. Everything else like wifi & bluetooth seems to be working fine.
Any suggestions from the great minds of xda?
Any method to write IMEI with the bootloader locked?
I've been looking for two days on how to solve this. Seems like there's not a lot to do unless I can unlock the bootloader. Even the EDL mode is locked. I turned to Miracle Tool for Xiaomi but their website says servers are currently not working. Then there's Chimera Tool, but it's too expensive to buy for just one phone.
Then I found out there are two more ways of getting to EDL mode. One is, opening up the device and shorting JTAG pins to boot into EDL, which is commonly known as test point method. And the other is, using an EDL cable which I can easily make at home.
Now I'm going to make an EDL cable to see if I can get into EDL mode successfully. If I can, then I will be able to repair the IMEI with other softwares. Although I don't have a QCN file for the MIX 3 yet, I'll concentrate on getting to EDL mode first.
:fingers-crossed:
EDL cable method don't work on these newer phones anymore. And these are also EDL-locked so test point method needs an authorized xiaomi account to access using EDL. If you google "Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts" then you'll find an excellent article that points out the issue in this new security system. Because of this my phone is now network-dead and can never be fixed from Bangladesh.
If anyone finds any solution to this problem in future please do let me know here. Thank you.
Background: After a night of searching I was unable to find a solution for this. I'm a newbie in the phone tech, but I did root couple of them, back in the days, with stock recovery and with TWRP. The first owner of this phone said it was working well until this happened.
Problem: I got this phone in the state where it's stuck on Nokia logo. Developer mode is not enabled, therefore OEM is not unlocked as well, and I'm only left with a stock recovery with an option to sideload update from ADB, and a Fastboot (Download) mode. I haven't been able to find a trusted firmware and even if I did I don't think it would work without OEM unlock...
Any ideas?
And, oh, I'm using Linux.
Thanks
This post is more like an explanation.
So my phone got bricked today, stuck at logo. I managed to access recovery and format data, but its stuck at formating data for more than 6 hour.
The only choice left is to unlock bootloader and flash firmware. Now here's the bull**** part.
When i try press fastboot oem unlock it says failed, device state locked. Device state can be set to unlock only through one method, by booting>going into settings>developer options>turning on oem unlocking. Doing this set your device in unlocked device state and thus allow it to unlock bootloader through fastboot. But, if your device got bricked and can't get into phone and your oem unlocking was off (average person will not set it to on) then you're ****ed, cuz without it you cannot unlock bootloader, thus you cannot install twrp or flash firmware.
This is so dumb, not even adb can set the device state to unlock. Read the last paragraph - (https://source.android.com/devices/bootloader/locking_unlocking)
There are so many post like these but no answer. so this post is for those guyz.
guess, i'll use feature phone for rest of my life
That an Android device's bootloader is locked by default isn't dumb, it has good reasons.
BTW: Flashing device's Stock ROM doesn't require device's bootloader got unlocked before.
tried flashing stock rom using adb sideload and fastboot. both failed. adb states that it cannot as it is a downgrade. fastboot says that device state is locked.
Yes, im aware that it is present for a good reason, but someone who's phone doesnt boot up has no way to unlock bootloader or do anything.
I'm not sure that I have the same problem but I have Samsung sm-t500 on the download mode says : device state lock and Im searching for FRP software but I think it won't happen because I tried too to connect via ADB and still can't connect.. But mine is still not bricked.. I will be very happy if you can give me some advice
I've just got Realme GT2 PRO (RMX3300) (China ROM) and I need to flash the global ROM on it. but with all of my knowledge and hours and days wasted trying to flash the global ROM I am still unable to.
my main problem is that the phone doesn't have fastboot or bootloader !!!, I honestly never seen a phone that doesn't have a bootloader, and accessing it is necessary to flash a ROM or Unlocking the bootloader
here are some of the things i tried:
1- turning off the phone then holding the VOLUME DOWN and POWER BUTTON (AS SHOWN IN THE PICTURE) only puts me in recovery mode
2- using commands such adb reboot bootloader just restart the phone and shows a weird Chinese text for a split second (AS SHOWN IN THE VIDEO)
3- tried installing DEEP TESTING app but it gives me this error (AS SHOWN IN THE PICTURE)
I am honestly very desperate at this point and I am willing to pay anyone who manages to fix this issue
Tl;dr : can't go into bootloader/fastboot
Mr.pizza said:
my main problem is that the phone doesn't have fastboot or bootloader !!!, I honestly never seen a phone that doesn't have a bootloader, and accessing it is necessary to flash a ROM or Unlocking the bootloader
Click to expand...
Click to collapse
Each computer so also every Android phone ( regardless of brand / model ) has a bootloader. Whether Google's Fastboot tool is supported or not on Android phone depends on brand / model: e.g. Samsung does NOT support it whereas Realme does.
See also here:
How to Unlock Bootloader of Realme GT2 Pro? – (Easy Method)
Do you want to Unlock the Bootloader of Realme GT2 Pro? We have shared the Easiest Method.
androidcatch.com
I upgraded to android 12. Oem unlock is not visible. I went back to android 11 and it still doesn't show. help
hhhhhhhhheeelllpp
And i search on recovery mode tap bootloader but i see black screen
is there no one to answer on huge xda? interesting
I think you can just use the official OEM unlock too app to one-step unlock the BL....
asus bootloader unlock tool apk. I tried maybe 20 times and it didn't work
yurishouse said:
I think you can just use the official OEM unlock too app to one-step unlock the BL....
Click to expand...
Click to collapse
I did not understand anything.
OEM unlock does not visible in developer options. I cannot enter the bootloader in the recovery menu. asus unlock tool.apk doesn't work.
i regret buying an asus phone
Robocop36 said:
I did not understand anything.
OEM unlock does not visible in developer options. I cannot enter the bootloader in the recovery menu. asus unlock tool.apk doesn't work.
i regret buying an asus phone
Click to expand...
Click to collapse
This device does not have OEM unlock. Contact ASUS to try and resolve the issue with the unlock app but I suspect you have a converted phone that is getting rejected by the ASUS side. Attempting too fix it yourself will involve amending some device parameters, I think someone has added some notes somewhere on the forums here..
I made a comment on asus zentalk. I've been waiting for a week, no answer. There are 20 moderators, but one person is not responding. a disgraceful place.
Hey man i went to the internet cafe yesterday to install raw firmware. I downloaded win10 asus qualcom usb drivers , downloaded usb minimal android sdk, pressed the volume up power button, the computer did not see my phone on the start screen, I tried many times and it didn't work.
The computer sees the phone without entering the start screen. I even copied 40 movies to the phone. but every time I press the volume up/power button the computer does not see the phone when the start screen comes up.
Andrologic said:
This device does not have OEM unlock. Contact ASUS to try and resolve the issue with the unlock app but I suspect you have a converted phone that is getting rejected by the ASUS side. Attempting too fix it yourself will involve amending some device parameters, I think someone has added some notes somewhere on the forums here..
Click to expand...
Click to collapse
If I try this, will the computer see my phone on the start screen?
ASUS Android Bootloader Interface Drivers Download for Windows 10, 8.1, 7, Vista, XP
Download the latest drivers for your ASUS Android Bootloader Interface to keep your Computer up-to-date.
www.driverscape.com
hhhhhhhheeeeeellppppp
It had HTC, Samsung, Xiaomi. I switched to ASUS. maybe my version is cn but the chinese changed it to ww! I didn't know it was like this i wouldn't have bought this phone had I known.
How do I get out of this job? I risk losing imei and more. maybe my device will be hard bricked. Flashing raw software takes a lot of effort. first of all, my computer doesn't see my device on the start screen, I couldn't even take a step. I unlocked the bootloader hundreds of times on my previous phones. I rooted hundreds of times , I installed custom roms hundreds of times,. but I could not progress even one step on the Asus phone.
Robocop36 said:
If I try this, will the computer see my phone on the start screen?
ASUS Android Bootloader Interface Drivers Download for Windows 10, 8.1, 7, Vista, XP
Download the latest drivers for your ASUS Android Bootloader Interface to keep your Computer up-to-date.
www.driverscape.com
Click to expand...
Click to collapse
Suggest using the orginal Andrid driver directly from Google. There is no specific ASUS drivers needed for this device although the one in your link may work too. And yes, you do need to sort out your driver before you can flash from PC to the device with Fastboot commands.
Andrologic said:
Suggest using the orginal Andrid driver directly from Google. There is no specific ASUS drivers needed for this device although the one in your link may work too. And yes, you do need to sort out your driver before you can flash from PC to the device with Fastboot commands.
Click to expand...
Click to collapse
Ok
Hi, your device seems to be a converted chinese version (with Tencent Games on the back) so you need to use this method to spoof the region if your phone and force the bootloader unlock: https://forum.xda-developers.com/t/...the-bootloader-of-your-rog-phone5-5s.4371255/
Saying and complaining ain't gonna help you out.
Lost people don't wanna reply as this is covered many times and can be found with search option on this forum.
Anyway his is relevant info for you :
1: The usb c port needed to use to flash etc in bootloader mode is on the side, NOT the bottom one.
2 : if option 1 this Still not working add device manual in driver section of computer, then is driver problem.
3: adb drivers/software/map with adb commands etc needs to be present on computer, or commands will not be executed correctly and give error.
4: of you have a Chinese phone CN FW that is flashed with the WW firmware, you will get problems, only way to solve this is to use correct firmware on device and upgrade.
This is also covered in a big topic on this forum.
5: of you need to go to a internet cafe do to flashing and install firmware, and you had Samsung xaomi etc and can't work this out yourself or Ith search option, o ask myself if you should mess with the phone in the first place,
When it goes wrong, it is bad phone, crap etc.... While it is user error. No hard feelings.
Hope you know enough now and get it fixed
Sending from Rog 5 ultimate android12 fw ww91 unlocked and rooted.
Read this : https://forum.xda-developers.com/t/...the-bootloader-of-your-rog-phone5-5s.4371255/
1: i was plugging it into the bottom usb c port not the side usb c port I'll try it when I have free time. thank you all so much