Dear all,
I bought Mi Pad 4 and it was running well, and I want to update the ROM. The device is comes with Locked bootloader.
I unlocked my Mi Pad 4 using MI Unlock. And when I try to relock it using "fastboot oem lock" command, it become suddenly comes with black screen with written: "The system has been destroyed. Press power button to shutdown".
So I entered the fastboot mode and try some command/solutions:
- My device status is locked:
E:\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
finished. total time: 0.006s
- I can't unlock it using Mi Unlock:
- Flashing using MiFlashalso not allowed since it is still locked:
- I tried to unlock using fastboot, also failed:
E:\adb>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.003s
- The faastboot screen in my mi pad is only for around 10 Second. After that it goes to "The System has been Destroyed" stage...
Any help is appreciated, because I cant use it anymore...
Why did you even want to close the BL again?!? I dont understand anyone who does that.
And AFAIK you can flash an original Image from Xiaomi even with locked BL. But I have never done it and the guide shows a working phone..
http://en.miui.com/thread-835254-1-1.html
You need the Mi-Flash Tool. And these damn Indian people with their fake titles on youtube.. The title is english and the freaking video is hindi or whatever.. SO ANNOYING!!!
Hi, the tutorial you gave is for 'normal' xiaomi phone, where it boot normally (even its BL is locked).
In my case, I cant load the BL (It said: Destroyed). The only thing I can do is restart to fastboot state, and after 20 seconds it goes again to Destroyed state.
Ok, so I have read some other threads and what seems the "only" solution is to unlock the bootloader again.. But the other people had no problem running "oem unlock".. And you get an error, what is kinda strange.
What happens in MiUnlock? Error?
Hi, I think the main problem is current status is "The System has been Destroyed", therefore it cannot load the BL.
Meanwhile, the BL is in Locked status. So it need to be un-locked first, so I can load the new ROM.
MIUnlock is error, it said: "Current account is not bound to this device", which is strange, because previously I unlocked using it before.
I assume MIUnlock said this because the status of "System destroyed"...
Never lock if there is not 100% Xiaomi official rom inside, and better use MiFlash with "clean all and lock" option for locking.
Thanks for your suggestion. Will do that after I fix this problem..
I think you have a bricked device.. Some devices have this "test-pins", where you can enable some debug-bridge and there you could flash it (mi5 or redmi5 was that in that thread). I dont know if the Pad4 has such Pins and you would have to open the whole device.. (its not something you can access from the outside).
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Noted on that, but too risky for me to open the case..
Any other solution would be really appreciated.
thE_29 said:
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Click to expand...
Click to collapse
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
P.Kosunen said:
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
Click to expand...
Click to collapse
Yup, and I cant do that since cannot load the BL, because it's "Destroyed" right now..
Up.
Does anyone have the solution on this?
Thanks.
Seemed "bricked" to me, welcome to the bricked world dude, I have had 2 beautiful paper holder on my desk.
mac_erot said:
Up.
Does anyone have the solution on this?
Thanks.
Click to expand...
Click to collapse
The only solution was already posted several times -> open device, find test-pins, use them and flash ROM. And yet, you still ignore it everytime. THERE is no other solution for bricked devices.
And: NEVER close the bootloader again on NON official ROMs.
2 ways to try out...
1st run
"fastboot flashing unlock"
2nd
"fastboot oem reboot EDL"
Or this link if the command doesn't work
https://www.google.com/amp/s/forum....e-how-to-reboot-to-edl-fastboot-t3394292/amp/
go to service centre they will be able to restore the device using edl i hope
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Looks like it is straightforward to remove the back cover. Perhaps you can find the EDL test points on the motherboard?
https://www.youtube.com/watch?v=RZpj0k9HKTQ
Is there no possibility to enable USB Debugging without entering the miui surface?
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Edl with test points should work, try some different ones, maybe the ones you are trying are wrong
---------- Post added at 06:47 AM ---------- Previous post was at 06:47 AM ----------
Also, try to run fastboot erase vbmeta
Related
Hi all,
As a result of some attempts to restore stock rom for KIWI-UL00. I ended up in a pretty bad state :
1. The phone reboots perpetually.
2. Putting a 64gb sd card with stock rom gets the recovery to 5% and then phone gets into the reboots cycle. I actually do not know if the dload/UPDATE.APP is being picked up or the wrong boot flashed in is kicking in.
3. The phone is unlocked, but as a result of the flashing I got FRP lock??? Here is what I see in fastboot mode on the phone screen:
PHONE is Unlocked
FRP Lock
4. Any attempt to flash in a new BOOT, SYSTEM or RECOVERY with fastboot ends up with error:
./fastboot flash recovery ~/Downloads/split_updata.pl/kiw_ul00_B239_Unicom/RECOVERY.img
target reported max download size of 266338304 bytes
sending 'recovery' (55968 KB)...
OKAY [ 1.768s]
writing 'recovery'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Undefined error: 0))
finished. total time: 1.769s
My thinking is that FRP lock is causing denying fastboot, but have no idea how to remove it. Without being able to flash in the correct stock recovery, I don't think I will be able to install the stock rom ever.
There are a lot of stuff written about FRP lock out there, but they assume working phone. In my case, I only have access to fastboot, not even adb!
Any ideas appreciated,
Thanks.
But u still can get it into fastboot right? Isnt it possible to use adb then to root it and put twrp on it and after that put custom firmware on it to get it booted up properly again. And after that installing a stock image again?
Dafriss said:
But u still can get it into fastboot right? Isnt it possible to use adb then to root it and put twrp on it and after that put custom firmware on it to get it booted up properly again. And after that installing a stock image again?
Click to expand...
Click to collapse
fastboot has very limited capabilities (I guess because of the FRP lock?) Some commands work, like this:
./fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) Root State: ROOT
(bootloader) Bootloader WidevineKey: WidevineKey_VALID
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.011s]
finished. total time: 0.011s
but other like erase or flash fail with the same error.
Do you know how to use ADB when the device is in fastboot mode? I currently get this:
./adb devices
List of devices attached
My thinking is that in order for DB to work the device need to be put in recovery mode, something I cannot achieve.
The only other mode i can put the phone in is by holding the UP and POWER it gets into something that has "eRecovery", but the rest is all in Chinese . There are 3 menus you can select with the volume and power (no screen touch). The first one leads to wifi discovery and but nothing after that. The other two top level menus lead to restart - again they are in Chinese, not sure what they do.
hrstoyanov said:
fastboot has very limited capabilities (I guess because of the FRP lock?) Some commands work, like this:
./fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) Root State: ROOT
(bootloader) Bootloader WidevineKey: WidevineKey_VALID
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.011s]
finished. total time: 0.011s
but other like erase or flash fail with the same error.
Do you know how to use ADB when the device is in fastboot mode? I currently get this:
./adb devices
List of devices attached
My thinking is that in order for DB to work the device need to be put in recovery mode, something I cannot achieve.
The only other mode i can put the phone in is by holding the UP and POWER it gets into something that has "eRecovery", but the rest is all in Chinese . There are 3 menus you can select with the volume and power (no screen touch). The first one leads to wifi discovery and but nothing after that. The other two top level menus lead to restart - again they are in Chinese, not sure what they do.
Click to expand...
Click to collapse
Isnt eRcovery from EMUI itself to save bricked phones? Like booting in new software or something? Maybe there are some video's about it on youtube???
I had some sort of the same issue but never had problems with frp lock before, i actually used a video from xda to get my honor 5x working again. I'll look for the link so you can see if the same steps work for you!
---------- Post added at 01:01 AM ---------- Previous post was at 12:59 AM ----------
Maybe thid will work when you make a walk around the rebooting parts
Dafriss said:
Isnt eRcovery from EMUI itself to save bricked phones? Like booting in new software or something? Maybe there are some video's about it on youtube???
I had some sort of the same issue but never had problems with frp lock before, i actually used a video from xda to get my honor 5x working again. I'll look for the link so you can see if the same steps work for you!
---------- Post added at 01:01 AM ---------- Previous post was at 12:59 AM ----------
Maybe thid will work when you make a walk around the rebooting parts
Click to expand...
Click to collapse
I saw the video, thanks. However, as you noticed in the video, not only phones boot ok, but when in fastboot mode, his phone reads:
Phone Unlocked
FRP Unlocked
When FRP is unlocked you can do all sorts of things with fastboot. I am not that lucky :crying:
hrstoyanov said:
I saw the video, thanks. However, as you noticed in the video, not only phones boot ok, but when in fastboot mode, his phone reads:
Phone Unlocked
FRP Unlocked
When FRP is unlocked you can do all sorts of things with fastboot. I am not that lucky :crying:
Click to expand...
Click to collapse
relax buddy, try dload method with any other version of stock firmware,
and if it doesnt help,
first find a rollback update.app package for your particular variant, first flash it
then , go back to lollipop firmware with the same dload method,.
you should be booted to lollipop firmware,
than, go on to developer options and enable oem unlock option
start from there..
thilak devraj said:
relax buddy, try dload method with any other version of stock firmware,
and if it doesnt help,
first find a rollback update.app package for your particular variant, first flash it
then , go back to lollipop firmware with the same dload method,.
you should be booted to lollipop firmware,
than, go on to developer options and enable oem unlock option
start from there..
Click to expand...
Click to collapse
The problem is that the "dload/update.app on sdcard" method only works if the phone has stock recovery and I blew that one off.
In order to flash in the stock recovery, i need the FRP lock removed, otherwise fastboot gives me the above errors . See my problem?
the eRecovery seems more hopeful. But is all in Chinese. I got to the first step where it finds my wireless network. I put the password for the WIFI
and it starts doing omething, but fails with big red exclamation mark and tones of thing written in chinese...
hrstoyanov said:
The problem is that the "dload/update.app on sdcard" method only works if the phone has stock recovery and I blew that one off.
In order to flash in the stock recovery, i need the FRP lock removed, otherwise fastboot gives me the above errors . See my problem?
the eRecovery seems more hopeful. But is all in Chinese. I got to the first step where it finds my wireless network. I put the password for the WIFI
and it starts doing omething, but fails with big red exclamation mark and tones of thing written in chinese...
Click to expand...
Click to collapse
how could you actually blow up recovery dude??
thilak devraj said:
how could you actually blow up recovery dude??
Click to expand...
Click to collapse
I think I flashed in the wrong HUAWEI recovery image - I used the latest stock rom for KIWI-L24, but my phone is KIWI-UL00.
I would love to be able to put the right one in, but the FRP Lock issue is preventing me. I don't understand how can the phone be unlocked but have a FRP lock??? See the FASTBOOT commands I used in earlier in this thread.
hrstoyanov said:
I think I flashed in the wrong HUAWEI recovery image - I used the latest stock rom for KIWI-L24, but my phone is KIWI-UL00.
I would love to be able to put the right one in, but the FRP Lock issue is preventing me. I don't understand how can the phone be unlocked but have a FRP lock??? See the FASTBOOT commands I used in earlier in this thread.
Click to expand...
Click to collapse
I'm having the same problem since 4months ago. Fed up of trying myself anymore so I Brought it to many phone shops but no one can repair. Might want to consider replacing the Mother board. anyone with solution pls help! Stupid FRP locked
hrstoyanov said:
I think I flashed in the wrong HUAWEI recovery image - I used the latest stock rom for KIWI-L24, but my phone is KIWI-UL00.
I would love to be able to put the right one in, but the FRP Lock issue is preventing me. I don't understand how can the phone be unlocked but have a FRP lock??? See the FASTBOOT commands I used in earlier in this thread.
Click to expand...
Click to collapse
rexaze said:
I'm having the same problem since 4months ago. Fed up of trying myself anymore so I Brought it to many phone shops but no one can repair. Might want to consider replacing the Mother board. anyone with solution pls help! Stupid FRP locked
Click to expand...
Click to collapse
FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options
Have you tried booting up TWRP from download mode and see if that works?
Fastboot boot TWRP.img
Sent from my KIW-L24 using Tapatalk
From aboot.img
{
"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"
}
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
2. Putting a 64gb sd card with stock rom gets the recovery to 5% and then phone gets into the reboots cycle. I actually do not know if the dload/UPDATE.APP is being picked up or the wrong boot flashed in is kicking in.
.[/QUOTE]
This part of your post makes it sound like at least one part of recovery is still functioning. (I think there are 2 recoveries on the 5x, but I don't know the details).
I also had the "stuck at 5%" problem when trying to use the "dload" method. Here was my experience:
1) Using 64gb SD card (Class 10 or something fancy)
I was never able to do a stock recovery. Despite many tries after reformatting the card, recovery process always terminated at approximately 5% ending in a reboot without applying the update (which in your case would probably be a bootloop since the existing system is bad).
2) Using 8gb SD card (An old card, class 2)
This worked the first time. I was literally about ready to throw this phone away and send an angry message to Honor, and only tried this out of desperation. I've used it multiple times since, and dload recovery always works with this card.
My conclusion was that this phone cannot seem to read all SD cards properly. I'm not sure if the problem is capacity (over 32gb??), speed class, or brand. Try another card and it may save you. To be safe, it's probably best to be a smaller size, lower speed class card.
dpredster said:
Have you tried booting up TWRP from download mode and see if that works?
Fastboot boot TWRP.img
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
Thank you so much, this worked for me
lukedunk said:
2. Putting a 64gb sd card with stock rom gets the recovery to 5% and then phone gets into the reboots cycle. I actually do not know if the dload/UPDATE.APP is being picked up or the wrong boot flashed in is kicking in.
.
Click to expand...
Click to collapse
This part of your post makes it sound like at least one part of recovery is still functioning. (I think there are 2 recoveries on the 5x, but I don't know the details).
I also had the "stuck at 5%" problem when trying to use the "dload" method. Here was my experience:
1) Using 64gb SD card (Class 10 or something fancy)
I was never able to do a stock recovery. Despite many tries after reformatting the card, recovery process always terminated at approximately 5% ending in a reboot without applying the update (which in your case would probably be a bootloop since the existing system is bad).
2) Using 8gb SD card (An old card, class 2)
This worked the first time. I was literally about ready to throw this phone away and send an angry message to Honor, and only tried this out of desperation. I've used it multiple times since, and dload recovery always works with this card.
My conclusion was that this phone cannot seem to read all SD cards properly. I'm not sure if the problem is capacity (over 32gb??), speed class, or brand. Try another card and it may save you. To be safe, it's probably best to be a smaller size, lower speed class card.[/QUOTE]
this might be one of my chances.. i trieda 32gig card.. so ill try a 8gig.. if this works im gonna kiss all of you guys.. looking for a solution sincetwo days.. with a hour sleepbreak... thnks for the tip for themoment.
Sent from my HUAWEI HUAWEI GRA-L09 using XDA Labs
maxprzemo said:
From aboot.img
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
Click to expand...
Click to collapse
can u explain a bit more
---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------
dpredster said:
Have you tried booting up TWRP from download mode and see if that works?
Fastboot boot TWRP.img
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
how ?
Hello!! sorry for the bump, but I have exactly the same problem. Bootloader unlock, but FRP LOCK
Phone is bricked.
Updateapp fails to install at 5%
Any solution? Totally stuck.
---------- Post added at 08:57 PM ---------- Previous post was at 08:55 PM ----------
maxprzemo said:
From aboot.img
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
Click to expand...
Click to collapse
what's this about? aboot?
maxprzemo said:
From aboot.img
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
Click to expand...
Click to collapse
I am having the same problem (boot = unlocked, frp = lock) and here's what I get from those commands:
-----------------------
D:\_TEMP\Portables\ADB Tools>fastboot oem frp-unlock
...
FAILED (remote: oem_frp_check_password failed! Error = -1)
finished. total time: 0.013s
-----------------------
Whatever the FRP-Check Password is, I don't have it. I tried the OEM unlocker Code as well as the (former) google password (ok, just a stupid try).
donschmidto said:
From aboot.img
I am having the same problem (boot = unlocked, frp = lock) and here's what I get from those commands:
-----------------------
D:\_TEMP\Portables\ADB Tools>fastboot oem frp-unlock
...
FAILED (remote: oem_frp_check_password failed! Error = -1)
finished. total time: 0.013s
-----------------------
Whatever the FRP-Check Password is, I don't have it. I tried the OEM unlocker Code as well as the (former) google password (ok, just a stupid try).
Click to expand...
Click to collapse
Relock bootloader and unlock again. This way u can unlock frp
My Redmi Note 5A Prime came with unlocked bootloader with a fake rom. so I flashed official developer fastboot rom. After that my IMEI broke and bootloader locked. Unable to open diag mode. Unable to add MI Account on the phone. I search the internet but sadly couldn't find anything. what I have found needs unlocked bootloader. Can anyone please help me to unlock the bootloader?
You have to apply here: http://en.miui.com/unlock/ in order to unlock your bootloader (can take a bit to get verified)
In addition add the phone number you apply with to your mi clound & login to your mi account on your phone.
Download the software for windows --> login --> connect your phone via fastboot --> hit unlock.
If it still does not work, please go ahead and flash the latest china developer rom on your phone and try everything again.
Good luck and please tell me if it worked
you can unlock unofficial bootloader with edl mode:
http://en.miui.com/thread-2049615-1-1.html
Thanks a lot for this solution ada12, it looks promissing.
I suppose that what they mean on your link by "REBOOT YOUR PHONE TO EDL MODE ( Testpoint )" is that i need to unmount the phone like in this video, right?
I havn't tried the hardware method yet, and when I try to use myflash with what is in RNote5_unlock.zip it says it cannot find the file flash_all.bat. So I tried different things:
- used the bach scripts contained in ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but it fails saying cannot find the file tz.mbn... for sure it's not there
- added what was in the zip to the folder ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but then i get the same error that i have been getting for the past several hours "Flash tz error" in mi flash...
What am I doing wrong?
Today, when I try to access the thread on the miui forum i get this error message :/
Sorry, you don't have the permission to access this thread.
[ Xiaomi MIUI Official Forum Home ]
Can you still see it ada12?
parpagnas said:
Thanks a lot for this solution ada12, it looks promissing.
I suppose that what they mean on your link by "REBOOT YOUR PHONE TO EDL MODE ( Testpoint )" is that i need to unmount the phone like in this video, right?
I havn't tried the hardware method yet, and when I try to use myflash with what is in RNote5_unlock.zip it says it cannot find the file flash_all.bat. So I tried different things:
- used the bach scripts contained in ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but it fails saying cannot find the file tz.mbn... for sure it's not there
- added what was in the zip to the folder ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but then i get the same error that i have been getting for the past several hours "Flash tz error" in mi flash...
What am I doing wrong?[/QUOTE
You try different rom to flashing,I mean your device is RN5A Prime(Ugg)not Ugglite
Sent from my ugg using XDA Labs
Click to expand...
Click to collapse
[Help] Flash global rom my redmi note 5a that i recently bought is tampered
can you please help me to flash a global rom ? i bought a redmi note 5a but i found out that my rom is tampered not global. after searching i found out that i need to unlock the bootloader. but it sucks at 99% . anyone please help me.
godexgaming said:
can you please help me to flash a global rom ? i bought a redmi note 5a but i found out that my rom is tampered not global. after searching i found out that i need to unlock the bootloader. but it sucks at 99% . anyone please help me.
Click to expand...
Click to collapse
Did you try bounding mi account?If yes try 3 day to try agains to UBL and dont forget to visit mi community,in there many guides to UBL your devices,good luck..
Sent from my ugg using XDA Labs
godexgaming said:
can you please help me to flash a global rom ? i bought a redmi note 5a but i found out that my rom is tampered not global. after searching i found out that i need to unlock the bootloader. but it sucks at 99% . anyone please help me.
Click to expand...
Click to collapse
I had the same problem - the phone came with a 'fake' global rom installed and it was impossible to bind the phone and account. The way I got around it was to flash the latest Chinese stable rom (it isn't possible to flash the global rom while the bootloader is locked) onto the phone and then I was able to bind the phone and account. Once I got to this stage I was then able to request unlock permission which now takes 360 hours (15 days). Once the 15 days have elapsed the bootloader can be unlocked and you are then free to install the latest global rom.
To fix IMEI problem:
1.) Reboot to fastboot mode
2.) Run command: fastboot erase modemst1
3.) Run command: fastboot erase modemst2
4.) IMEI fixed!
For bootloader unlock,if you cant add Mi account to your phone,it is problem,becouse you have to submit phone to unlock request (via developer mode).
Try this: Go to Developer settings,check "Allow OEM unlock" option and then try add MiAccount via next option "Mi unlock status"
lazynkox said:
To fix IMEI problem:
1.) Reboot to fastboot mode
2.) Run command: fastboot erase modemst1
3.) Run command: fastboot erase modemst2
4.) IMEI fixed!
For bootloader unlock,if you cant add Mi account to your phone,it is problem,becouse you have to submit phone to unlock request (via developer mode).
Try this: Go to Developer settings,check "Allow OEM unlock" option and then try add MiAccount via next option "Mi unlock status"
Click to expand...
Click to collapse
I agree with everything here, good job. Just want to add something to "unlock bootloader": if you recieve some error "it can't be added", download a VPN with the location in china. There is one app (at least) where you can create an fake account (e.g. 10 minute mail) and have 1 day of premium. Point it onto china and try to add your mi account again, that should do the trick.
Good luck and have fun ^^ ask if you have some problems!
---------- Post added at 02:11 PM ---------- Previous post was at 02:03 PM ----------
parpagnas said:
Thanks a lot for this solution ada12, it looks promissing.
I suppose that what they mean on your link by "REBOOT YOUR PHONE TO EDL MODE ( Testpoint )" is that i need to unmount the phone like in this video, right?
I havn't tried the hardware method yet, and when I try to use myflash with what is in RNote5_unlock.zip it says it cannot find the file flash_all.bat. So I tried different things:
- used the bach scripts contained in ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but it fails saying cannot find the file tz.mbn... for sure it's not there
- added what was in the zip to the folder ugglite_global_images_8.4.12_20180412.0000.00_7.1_global but then i get the same error that i have been getting for the past several hours "Flash tz error" in mi flash...
What am I doing wrong?
Click to expand...
Click to collapse
The answer is: NANOMACHINES, SON!
Just kidding, you have to point onto the root folder, if the system can't find the "flash.bat" you might be one folder too deep. If you get an error message during flashing then you might have a problem in terms of compatibility.
I still don't know yet, what the NSF means by mentioning the computer system with the "blue face for an interface" as an solution to xiaomis bootloader incompatibility issue. It seems suspicious, that some valuable forum posts have gone missing... wondering what the NSF is up to.
:highfive:
md.safayat said:
My Redmi Note 5A Prime came with unlocked bootloader with a fake rom. so I flashed official developer fastboot rom. After that my IMEI broke and bootloader locked. Unable to open diag mode. Unable to add MI Account on the phone. I search the internet but sadly couldn't find anything. what I have found needs unlocked bootloader. Can anyone please help me to unlock the bootloader?
Click to expand...
Click to collapse
Hi to all. i have problem with redmi note 5a after remove micloud wifi and bluetooth unaviable. i try many official roms, but no luck. Please help to resolve this problem.
lazynkox said:
To fix IMEI problem:
1.) Reboot to fastboot mode
2.) Run command: fastboot erase modemst1
3.) Run command: fastboot erase modemst2
4.) IMEI fixed!
For bootloader unlock,if you cant add Mi account to your phone,it is problem,becouse you have to submit phone to unlock request (via developer mode).
Try this: Go to Developer settings,check "Allow OEM unlock" option and then try add MiAccount via next option "Mi unlock status"
Click to expand...
Click to collapse
How will you run these commands on a locked bootloader? And no erasing modemst1-2 won't fix imei's.
Hello I have a redmi note 4x completely briked..the phone has the bootloader blocked, when I turn it on it restarts and never gets to load the system, I have already flash by testpoint many rom, Miui developer, Global Stable and still in the same, The phone in fastboot mode and Revory (the original of the phone) does not restart, and during the flash by testpoint it is also maintained and never disconnected, I say this because I have read some cases that this happens. At the beginning of the problem he always came to show the three points that he is loading MIUI but there is a reboot, this is not anymore the case, now it never comes, sometimes it stays on when I leave it for a long time restarting but stuck only on the logo MI .... someone knows how to solve this problem, I can not send it to any technical service or anything in my country that does not exist ... greetings
I'm no expert, but I would go online and unlock the bootloader. Then follow this: http://c.mi.com/thread-334-1-0.html There might be other ways, but this one will work, even if getting Xiaomi to unlock the bootloader takes time.
Unlock bootloader, it takes 3 days for Xiaomi to approve it. Install twrp recovery, wipe everything and install some aosp rom.
ac00995 said:
Unlock bootloader, it takes 3 days for Xiaomi to approve it. Install twrp recovery, wipe everything and install some aosp rom.
Click to expand...
Click to collapse
I can not do that the phone don't loader the OS..
Not sure but I think you should install adb and fastboot on pc and then Connect your phone then try "fastboot devices" and if it shows you some device, it means that your device is plugged in properly then try "fastboot oem unlocking" command this would unlock your bootloader, well the big problem is that all these commands are with respect to the Linux pc, there are something similar to do with windows and worse thing is that xiaomi have different method for unlocking the bootloader as shown in other post
Bhanu_p_mishra said:
Not sure but I think you should install adb and fastboot on pc and then Connect your phone then try "fastboot devices" and if it shows you some device, it means that your device is plugged in properly then try "fastboot oem unlocking" command this would unlock your bootloader, well the big problem is that all these commands are with respect to the Linux pc, there are something similar to do with windows and worse thing is that xiaomi have different method for unlocking the bootloader as shown in other post
Click to expand...
Click to collapse
Thanks for your answer, but for unlock the bootloader of a Xiaomi Phone you need first apply and ask permissions with a mi account , after that use a sofware name Mi Unlock with the account login on the phone and on the MI Unlock software. Is the only way in Xiaomi's Phone. The big problen here is I can't get into the Android System I can't put my account in the phone for unlock the bootloader.
michelhdz9045 said:
Thanks for your answer, but for unlock the bootloader of a Xiaomi Phone you need first apply and ask permissions with a mi account , after that use a sofware name Mi Unlock with the account login on the phone and on the MI Unlock software. Is the only way in Xiaomi's Phone. The big problen here is I can't get into the Android System I can't put my account in the phone for unlock the bootloader.
Click to expand...
Click to collapse
I know that brother that's why I suggest you to use fastboot and adb as it works on some basic android phones and it is a kind of general method but I haven't tried it on mi phones
---------- Post added at 03:02 PM ---------- Previous post was at 02:54 PM ----------
Bhanu_p_mishra said:
I know that brother that's why I suggest you to use fastboot and adb as it works on some basic android phones and it is a kind of general method but I haven't tried it on mi phones
Click to expand...
Click to collapse
Have you tried any fastboot rom to unbrick your device, I have read your post where you have mentioned about flashing some ROMs but have not seen fastboot rom
you may use wipedata option in recovery mode, if you done have already backed up your data or you can sacrifise the data on phone,it will load the original recovery rom,than upgrade rom.....
michelhdz9045 said:
Hello I have a redmi note 4x completely briked..the phone has the bootloader blocked, when I turn it on it restarts and never gets to load the system, I have already flash by testpoint many rom, Miui developer, Global Stable and still in the same, The phone in fastboot mode and Revory (the original of the phone) does not restart, and during the flash by testpoint it is also maintained and never disconnected, I say this because I have read some cases that this happens. At the beginning of the problem he always came to show the three points that he is loading MIUI but there is a reboot, this is not anymore the case, now it never comes, sometimes it stays on when I leave it for a long time restarting but stuck only on the logo MI .... someone knows how to solve this problem, I can not send it to any technical service or anything in my country that does not exist ... greetings
Click to expand...
Click to collapse
Try flashing fastboot stock rom
I had same problem couple of days ago , i had custom rom installed on my redmi note 4 nd while i was reverting back to stock miui rom from my twrp backup i messed up nd ended up bricking my phone. I tried everything but gained nothing. In the end i tried flashing fastboot rom with mi flash tool and it worked. But i had my bootloaders unlock.dont know if it works with locked bootloader. I guess u should give a shot . Gud luck
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
marceloariel said:
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
Click to expand...
Click to collapse
Thanks for the reply. I actually tried this as well but it did not work. MiFlash just appears to be running the flash_all_lock.bat script on Windows and it failed because the bootloader was not already unlocked according to its debug logs when I ran it. I should have mentioned that above.
Not sure if it will help but did you try a factory reset?
Press and hold the Power+Volume Down buttons untill you see the android with the no command. Press and hold the Power button. Press and release the Volume Up button once then release the Power button. Then you should see some recovery options.
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
sensig said:
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
Click to expand...
Click to collapse
The issue is caused by fastboot rom containing dummy system_b image and flashing script "forgetting" to force partition A as active. If a phone has B as an active partition and someone uses flash_all_lock.bat script, the phone's screwed. No idea what brought Xiaomi to this "brilliant" idea, not only there is a higher chance to brick the phone, but the zip file is also unnecessarily larger.
With locked bootloader it isn't possible to switch active partition anymore, so the phone is a (semi)brick. EDL mode is usually used to reflash locked bootloaders.
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
There are two commands for setting active partition, depending on the fastboot version. It's either old
fastboot set_active a
or newer
fastboot --set-active=a
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
if you open flashing script file (.bat or .sh) in a text editor, you will see that fastboot is flashing system.img to system_a partition and system_other.img to system_b partition. That system_other.img is a dummy image and is not bootable. You either:
Option 1: Set active partition to A before running any stock flashing script.
Option 2: Replace system_other.img to system.img in the script.
Option 3: Force partition A after flashing userdata.img and before any lock or reboot command.
dephekt said:
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
Click to expand...
Click to collapse
I am in the same exact position with my Mi A3... did you ever resolve this and if so how?
mewcatchew said:
I am in the same exact position with my Mi A3...
Click to expand...
Click to collapse
What causes led to this behavior ?
htn711 said:
What causes led to this behavior ?
Click to expand...
Click to collapse
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
Click to expand...
Click to collapse
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting).
Click to expand...
Click to collapse
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
garylawwd said:
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
Click to expand...
Click to collapse
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
---------- Post added at 02:40 PM ---------- Previous post was at 02:30 PM ----------
htn711 said:
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
Click to expand...
Click to collapse
Did you read my posts? I get "locked state error" with fastboot commands. I can reboot bootlader in fastboot, and it tjust reboots into fastboot - thats just about all i can do. It wont let me change anything, can only get info and reboot...
mewcatchew said:
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
Click to expand...
Click to collapse
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
garylawwd said:
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
Click to expand...
Click to collapse
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
Ya I wouldn't go trusting some random Russian site either. I don't think there is anything you can do without either
A) going into edl and using a verified mi account
B) bringing it to a service centre (which nobody wants to do)
In fastboot you can't get any commands to work now right? Your device is fully locked again?
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
That Russian site is run by the XDA guy from what I understood. There are other paid services which have Xiaomi service accounts, I only pointed you to the cheapest "verified" eshop. Just Google another one if you don't trust Russians. All of them will need to connect to your PC over Teamviewer and do the flashing, you will just follow the instructions (connect the phone, reboot it etc.).
ahsvanz
try
C:\ADB >fastboot devices
C:\ADB >fastboot OEM device-info
etc
replacing
C:\ADB with where ever you fastboot file is located
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
have you tried the code above ??
cant you just download the official original firmware and flash that ? im not familiar with the oneplus flashing techniques, ive always had samsungs except for the htc evo 3d back in the day
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
slimmynine said:
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
Click to expand...
Click to collapse
how does the one plus flash firmware ? for samsung we use a tool called odin, do you not have a similar tool for your device ?
I don't recall having any toolkit like that, but in order for the toolkit to work.. do you need to have an unlocked bootloader?
Cause the main issue is that I can't unlock it.
i dont think so, if your flashing an official firmware, but for your device i cant be sure of that
?
did you try running your commands as an su , is your device rooted ? you could try sideloading an update.zip maybe
what does it say when you flash this command ? true, true false ?
C:\ADB>fastboot OEM device-info
maybe this will help https://forum.xda-developers.com/t/...us-2-back-to-stock-100.3269543/#post-64279667
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
yeah i think some phone makers lock down the bootloader, like its unlocked but when i try to flash a gsi it says device locked state
jamsandpeabug said:
alcatel has a program to download and install firmware but the device is not listed, cannot find fw on the net
Click to expand...
Click to collapse
OK try
c:\adb
Adb fastboot oem device-info
Replacing
C:\adb
With where ever your fastboot is located
Just to check if your device is showing is oem locked or unlocked, it will display with a true or false option. I can't really advise to much as I don't have experience with that device
You could also try
fastboot oem unlock_critical
Not sure if that will work for your device though
Idk what else to recommend, are you stuck at boot ? Can u boot into recovery mode ? Do u have an ext sd card slot
OT-6025D | GSMSERVERPRO
gsmserverpro.com
Is that your firmware
Alcatel 1s Flash File Download [Stock ROM or Firmware
You can Download latest flash file and flash tools for Alcatel 1s phone here. Original stock ROM or Firmware available for free.
mobilereset99.com
Have youlooked at that
if you can confirm your phone has a mtk chipset use mtkclient to bootloader unlock it https://github.com/bkerler/mtkclient
otherwise youre out of luck
But
jamsandpeabug said:
im not stuck at boot, i want to flash gsi but it says device is in locked state even with oem unlocked in dev options, adb debugging enabled etc , and just wont let me flash.. its starts flashing and then fails due to locked state
Click to expand...
Click to collapse
If the flashing starts, and fails, the os would be overwritten and you wouldn't be able to boot. So what you mean is the process trys to start but fails, right yh then I don't know what else I can say to try and help, let's hope mtkclient is an avenue you can pursue
MOD ACTION:
Thread closed since OP has no content.