Hello there,
My op2 doesn't boot... I tried to use recovery tool and it was successful but...
One time H2 OS animation came up but it locked and I did same again... This time it didn't even boot.
I went into recovery mode of Op2 and tried to sideload a rom but it failed at 92% for several times and several roms.
Sometimes I turn on the phone it only shows Linux's logo.
Do you think it's a hardware problem?
12parsa said:
Hello there,
My op2 doesn't boot... I tried to use recovery tool and it was successful but...
One time H2 OS animation came up but it locked and I did same again... This time it didn't even boot.
I went into recovery mode of Op2 and tried to sideload a rom but it failed at 92% for several times and several roms.
Sometimes I turn on the phone it only shows Linux's logo.
Do you think it's a hardware problem?
Click to expand...
Click to collapse
Try this: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Or do a full wipe and flash this rom and transfer for it through mtp on twrp from your pc: http://downloads.oneplus.net/oneplus-2/oneplus_2_oxygenos_3.0.2/
Or you can flash a stock rom through fastboot: http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
Dead oneplus2.
Hi guys and thanks to all xda community for helping us. I tried to upgrade from 2.0.2 to 3.0.2. But after the instalation my oneplus2 stucks into bootlogo(powered by android). Before i try to upgrade i forgot to enable on system oem unlocking. Now i'm not having access to recovery option,when i try to press volume- +power the op2 vibrate and flashes the screen till i stop pressing the power button,and when i try to enable oem via fastboot always get this message: <remote oem unlock is disabled>. I tried so many option but always getting this message: remote oem unlock is disabled. Please help me...
I finally fixed my OP2...
I used one of recovery tools and then I flashed TWRP v 3...
Then I wiped all data and installed new os
12parsa said:
I finally fixed my OP2...
I used one of recovery tools and then I flashed TWRP v 3...
Then I wiped all data and installed new os
Click to expand...
Click to collapse
so your both imei is back?
lockmunk said:
so your both imei is back?
Click to expand...
Click to collapse
No,
They're lost
12parsa said:
I finally fixed my OP2...
I used one of recovery tools and then I flashed TWRP v 3...
Then I wiped all data and installed new os
Click to expand...
Click to collapse
12parsa said:
No,
They're lost
Click to expand...
Click to collapse
you lost your imei but you can make call now?
whats your mean by "finally fixed"?
lockmunk said:
you lost your imei but you can make call now?
whats your mean by "finally fixed"?
Click to expand...
Click to collapse
I can't call because I can't connect to any network because of missing IMEI.
"Finally fixed" means It can boot and run without problem now.
12parsa said:
I can't call because I can't connect to any network because of missing IMEI.
"Finally fixed" means It can boot and run without problem now.
Click to expand...
Click to collapse
Follow this step and ur IMEI should back.
Run the following fastboot cmd
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Jyoti_re said:
Follow this step and ur IMEI should back.
Run the following fastboot cmd
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
i lost my IMEI slot 2..IMEI slot 1 already ok now.
lockmunk said:
i lost my IMEI slot 2..IMEI slot 1 already ok now.
Click to expand...
Click to collapse
After fastboot erase commands?
Jyoti_re said:
Follow this step and ur IMEI should back.
Run the following fastboot cmd
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
12parsa said:
After fastboot erase commands?
Click to expand...
Click to collapse
actually that command kills both my imei. but i recovered back my imei1 by reset through qualcomm unbrick method.
now only imei2 not recovered. now if i use the above commands, my imei1 not lost but imei2 still not back.
lockmunk said:
actually that command kills both my imei. but i recovered back my imei1 by reset through qualcomm unbrick method.
now only imei2 not recovered. now if i use the above commands, my imei1 not lost but imei2 still not back.
Click to expand...
Click to collapse
I also lost IMEI 2, after using these fastboot commands,
Did you find any solution ?
osr.arora said:
I also lost IMEI 2, after using these fastboot commands,
Did you find any solution ?
Click to expand...
Click to collapse
as for now, no solution. the IMEI2 shows 0. but if we put dual sim, it works
http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
This will definitely help
Sent from my ONE A2003 using XDA-Developers mobile app
lockmunk said:
as for now, no solution. the IMEI2 shows 0. but if we put dual sim, it works
Click to expand...
Click to collapse
I have dual sims inserted, & 2nd sim shows 0 network bars.
Related
As the title says.
Does anybody have any updated Radio / bootloader zips that I can flash via TWRP ?
I have an old Moto E Condor and I can't get the phone to recognize the Sim so was wondering if updating the radio / bootloader would help ?
I'm running out of ideas.
I have tried Android 6 & 7 tried different Sims.
I'm not sure how I would find out if it's a hardware issue rather than software ?
Any ideas ?
Thanks
Check this link for Radio file
https://forum.xda-developers.com/devdb/project/dl/?id=13877
I didn't got what bootloader you are talking about. But if you want latest twrp then check this link
https://dl.twrp.me/condor/twrp-3.1.0-0-condor.img.html
Ankit_29 said:
Check this link for Radio file
https://forum.xda-developers.com/devdb/project/dl/?id=13877
I didn't got what bootloader you are talking about. But if you want latest twrp then check this link
https://dl.twrp.me/condor/twrp-3.1.0-0-condor.img.html
Click to expand...
Click to collapse
Thanks mate.
I will give it a go
I had the same problem with my condor ,but flashing the "radio files" didn't help the case ,it always failed in my case ,so the best advice I can give you is to not flash isolated radio files ,but to backup your data and flash stock ROM for your device,trust me it'll save you a lot of headache
Akshay_92 said:
I had the same problem with my condor ,but flashing the "radio files" didn't help the case ,it always failed in my case ,so the best advice I can give you is to not flash isolated radio files ,but to backup your data and flash stock ROM for your device,trust me it'll save you a lot of headache
Click to expand...
Click to collapse
Thanks for that info.
You say that you had the same problem? Have you sorted it out now ?
When you flashed the stock ROM
Did you have to do this via fastboot ??
Thanks again
johnhux7 said:
Thanks for that info.
You say that you had the same problem? Have you sorted it out now ?
When you flashed the stock ROM
Did you have to do this via fastboot ??
Thanks again
Click to expand...
Click to collapse
Yes,my device is good as new,I'm writing this message from it so haha...you can find the appropriate stock ROM to flash here
https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
If you don't know which ROM to download, got to your phones settings >about phone>build number
And download the specific ROM with that build number,now be absolutely sure to not flash a KitKat ROM on a device that was upgraded to lollipop earlier, its absolutely essential as it 100% will brick your device,
As for your question, yes you will need to be in fastboot to flash the ROM,and the program that you'll need to flash the ROM with is called mfastboot-v2 you can find it here
https://forum.xda-developers.com/general/rooting-roms/using-mfastboot-exe-to-unbrick-motorola-t3203518
Now after downloading both the ROM and mfastboot ,extract both of them into the same folder of your PC ,after doing that ,go into that folder and hold shift+right mouse key and select "open new command window here" from the dialogue box ,now assuming that you have downloaded the drivers for your phone , switch off your phone ,go into mfastboot mode by holding power key + volume down key for about 5-7seconds, now connect your phone to the PC with the help of USB cable and in the command window type "mfastboot devices" if everyw is done correctly it will show your device's name in an alphanumeric format under "list of devices" after that follow these commands in the ORDER! that they are written and you will be good to go :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
NOTE:- number of sparsechunk files may be different for your version (check the files extracted from the ROM inside the same folder to see the order of numbers) so if the numbers are like 0,1,2,3,4 flash them in that order ,I have named it 1,2,3 in the command above for illustrations, good luck if you will do this correctly, you'll be back to a facotory version of your phone,with the imei problem fixed , another thing though, you'll lose your custom recovery so after you flash this stock ROM ,you'll have to flash the custom recovery again,
Cheers!!
Akshay_92 said:
Yes,my device is good as new,I'm writing this message from it so haha...you can find the appropriate stock ROM to flash here
https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
If you don't know which ROM to download, got to your phones settings >about phone>build number
And download the specific ROM with that build number,now be absolutely sure to not flash a KitKat ROM on a device that was upgraded to lollipop earlier, its absolutely essential as it 100% will brick your device,
As for your question, yes you will need to be in fastboot to flash the ROM,and the program that you'll need to flash the ROM with is called mfastboot-v2 you can find it here
https://forum.xda-developers.com/ge...ng-mfastboot-exe-to-unbrick-motorola-t3203518
Now after downloading both the ROM and mfastboot ,extract both of them into the same folder of your PC ,after doing that ,go into that folder and hold shift+right mouse key and select "open new command window here" from the dialogue box ,now assuming that you have downloaded the drivers for your phone , switch off your phone ,go into mfastboot mode by holding power key + volume down key for about 5-7seconds, now connect your phone to the PC with the help of USB cable and in the command window type "mfastboot devices" if everyw is done correctly it will show your device's name in an alphanumeric format under "list of devices" after that follow these commands in the ORDER! that they are written and you will be good to go :
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
NOTE:- number of sparsechunk files may be different for your version (check the files extracted from the ROM inside the same folder to see the order of numbers) so if the numbers are like 0,1,2,3,4 flash them in that order ,I have named it 1,2,3 in the command above for illustrations, good luck if you will do this correctly, you'll be back to a facotory version of your phone,with the imei problem fixed , another thing though, you'll lose your custom recovery so after you flash this stock ROM ,you'll have to flash the custom recovery again,
Cheers!!
Click to expand...
Click to collapse
Thanks so much for taking the time to write this for me.
I'm new to using fastboot I got spoiled by using ODIN with Samsung whist I was learning.
Just one question.
Do you put in each of those commands and press enter after each one ?
johnhux7 said:
Thanks so much for taking the time to write this for me.
I'm new to using fastboot I got spoiled by using ODIN with Samsung whist I was learning.
Just one question.
Do you put in each of those commands and press enter after each one ?
Click to expand...
Click to collapse
Yes!!...And wait till it returns as [OKAY],then move ahead with the next one
Sent from my Moto G (4) using Tapatalk
---------- Post added at 06:43 PM ---------- Previous post was at 06:39 PM ----------
Akshay_92 said:
Yes!!...And wait till it returns as [OKAY],then move ahead with the next one ...It's alright man,we all are new to some stuff at one point,do let me know if you come into a hiccup
Cheers!
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Sent from my Moto G (4) using Tapatalk
Akshay_92 said:
Yes!!...And wait till it returns as [OKAY],then move ahead with the next one
Click to expand...
Click to collapse
I though so.
Was just checking.
I'm going to have some fun doing this
Love learning some thing new
The Moto is my spare phone so I can practice on that before getting stuck into fastboot on my Honor 8
johnhux7 said:
I though so.
Was just checking.
I'm going to have some fun doing this
Love learning some thing new
The Moto is my spare phone so I can practice on that before getting stuck into fastboot on my Honor 8
Click to expand...
Click to collapse
[emoji1] yep absolutely,
Sent from my Moto G (4) using Tapatalk
Akshay_92 said:
[emoji1] yep absolutely,
Click to expand...
Click to collapse
Thank you so much for sharing your knowledge.
It's what I love about this XDA community
Few days ago, imei number on my brother's moto e xt1022 disappeared out of nowhere. Phone used to boot to working state but didn't accept any sim cards nor connect to WiFi. The bootloader was locked and phone was not rooted.
So I visited official motorala service centre. They "softwared" the phone (probably flashed stock firmware). After that, the imei no was replaced with new numbers. Bootloader was unlocked automatically. The phone booted once. But after I switched off to insert sim card and then tried to boot, its not getting past this screen. What should I do to restore the phone to its working condition? Please help.
ramsut said:
Few days ago, imei number on my brother's moto e xt1022 disappeared out of nowhere. Phone used to boot to working state but didn't accept any sim cards nor connect to WiFi. The bootloader was locked and phone was not rooted.
So I visited official motorala service centre. They "softwared" the phone (probably flashed stock firmware). After that, the imei no was replaced with new numbers. Bootloader was unlocked automatically. The phone booted once. But after I switched off to insert sim card and then tried to boot, its not getting past this screen. What should I do to restore the phone to its working condition? Please help.
Click to expand...
Click to collapse
Flash stock/custom ROM
ramsut said:
Few days ago, imei number on my brother's moto e xt1022 disappeared out of nowhere. Phone used to boot to working state but didn't accept any sim cards nor connect to WiFi. The bootloader was locked and phone was not rooted.
So I visited official motorala service centre. They "softwared" the phone (probably flashed stock firmware). After that, the imei no was replaced with new numbers. Bootloader was unlocked automatically. The phone booted once. But after I switched off to insert sim card and then tried to boot, its not getting past this screen. What should I do to restore the phone to its working condition? Please help.
Click to expand...
Click to collapse
Hmm....Well this is certainly not professional and quite unfortunate,on the part of the service center employees,but since I assume that it's no longer under warranty and they won't take back the Devi because it's unlocked now and also because they won't take responsibility for it ,the best you can do is flash stock ROM,I have explained that earlier in this thread ...
Cheers!! And let me know how it went
Sent from my Moto G (4) using Tapatalk
Akshay_92 said:
Hmm....Well this is certainly not professional and quite unfortunate,on the part of the service center employees,but since I assume that it's no longer under warranty and they won't take back the Devi because it's unlocked now and also because they won't take responsibility for it ,the best you can do is flash stock ROM,I have explained that earlier in this thread ...
Cheers!! And let me know how it went
Click to expand...
Click to collapse
I got the SIM working.
Followed your instructions.
Got the phone back to stock
All good thanks for your help
John
Hello,
1.Ive rooted my phone emui 4.1 with kingroot
2. I've flashed Official twrp 3.0.2
3. After booting in twrp I tried to clear cache but it unable to clear cache.
4. Then I've force rebooted to recovery then all partitions got unmounted (shocked)
5. So I flashed mm kang ROM then phone bricked so I thought that stock recovery may mount all partitions so I flashed stock recovery (back up)
6. Finally I'm unable to boot in stock recovery and ROM
7. What do u think guys? How to solve this issue ??
Any one faced same problem?
***Main thing is what ever I try to push a file from adb to phone in fastboot mode (ex- recovery,boot.IMG) it says "writing recovery failed:command not allowed". why I'm getting this error ?? I've unlocked bootloader too ***
Thank you!
.
Martin213 said:
Restore backup of stock rom if you able to boot in twrp.Did you try flash with huawei multitool?
Sent from Paris with love ?
Click to expand...
Click to collapse
I tried but partitions are unmounted so its not booting up,struck at Honor logo
How to solve this???
Pranav Kumar said:
How to solve this???
Click to expand...
Click to collapse
if bootloader works: download official image, use fastboot flash commands to flash all parts
otherwise
download official image from huawai, (update.app) copy to sd, boot phone with all 3 buttons pressed. it shold boot into some recovery.
endrancer said:
if bootloader works: download official image, use adb flash commands to flash all parts
otherwise
download official image from huawai, (update.app) copy to sd, boot phone with all 3 buttons pressed. it shold boot into some recovery.
Click to expand...
Click to collapse
I tired pushing recovery image to device but command says "writing recovery,failed (command not allowed)"
And I tried update.app in SD card in a folder dload tried 3button method also, but it is not booting in recovery right how it can take update?
Pranav Kumar said:
I tired pushing recovery image to device but command says "writing recovery,failed (command not allowed)"
And I tried update.app in SD card in a folder dload tried 3button method also, but it is not booting in recovery right how it can take update?
Click to expand...
Click to collapse
are you able to boot into bootloader? is "fastboot devices" command showing anything?
eddor1614 said:
are you able to boot into bootloader? is "fastboot devices" command showing anything?
Click to expand...
Click to collapse
Yes its showing
Pranav Kumar said:
Yes its showing
Click to expand...
Click to collapse
have you extracted BOOT, RECOVERY, SYSTEM and CUSTOM from huawei package?
eddor1614 said:
have you extracted BOOT, RECOVERY, SYSTEM and CUSTOM from huawei package?
Click to expand...
Click to collapse
Yes I tried but when file is being pushed to phone it says failed (command not allowed) repeats
Can you see "phone unlocked" on screen?
Yeah, sounds like locked bootloader.
Gsavas said:
Yeah, sounds like locked bootloader.
Click to expand...
Click to collapse
No bro I've unlocked bootloader
And I can see *phone unlocked" in fastboot mode
Gsavas said:
Yeah, sounds like locked bootloader.
Click to expand...
Click to collapse
have you tried flashing BOOT or SYSTEM partitions?
Pranav Kumar said:
No bro I've unlocked bootloader
And I can see *phone unlocked" in fastboot mode
Click to expand...
Click to collapse
You could try to reinstall drivers then or try a different pc.
Gsavas said:
You could try to reinstall drivers then or try a different pc.
Click to expand...
Click to collapse
Tried and I got same error(failed(command not allowed))
Do you have hisuite? If not try uninstalling drivers then install hisuite and try flashing with fastboot then. By the way does your device get recognised when you type "fastboot devices" command?
that's strange.
have you tried booting into second recovery?
eddor1614 said:
that's strange.
have you tried booting into second recovery?
Click to expand...
Click to collapse
Yes in eRecovery I can see "update recovery" after connecting to wifi it says "failed to get device info"
I ran out of options.
You might want to try all the same, using different UPDATE.APP version, like B180 or B200, using a different cable, different computer, etc.
Then next step will be Huawei support, it might be a memory/hardware problem.
Sorry man.
Need help.. cant turn on my Phone.. always stuck at android one Logo and fastboot (when i try hold volume up and power )
i rooted phone (adb,twrp,magisk) . Everything well good, but WIFI didn't work. Then i get in TWRP and maybe deleted partition A and B( ) i can't get through the Fastboot.
my mi a3 is V10.3.6.0.PFQMIXM version-- and cant Flash it with miflash tool, it says error : can not found file flash_all_lock.bat
now i cant find my device with Adb devices (its says List of devices attached)
pls help :/ thank you.
Go to nearest service centre
Going to a service center probably isn't a wise idea. You've rooted your phone - your warranty is gone.
I guess you don't have the right drivers installed OR, the stock rom you were trying to flash had some issues with the flash script. You might want to take a look at this post
Download the correct stock ROM for your device, the .tgz version & flash it with miflash tool. It's important to note that some versions of miflash tool don't work with Mi A series phones for unknown reasons.
Alternatively, if your recovery is working, then you can flash the recovery version of stock rom. It's all available on this forum.
evanB70 said:
Going to a service center probably isn't a wise idea. You've rooted your phone - your warranty is gone.
I guess you don't have the right drivers installed OR, the stock rom you were trying flash had some issues with the flash script. You might want to take a look at this post
Download the correct stock ROM for your device, the .tgz version & flash it with miflash tool. It's important to note that some versions of miflash tool don't work with Mi A series phones for unknown reasons.
Alternatively, if your recovery is working, then you can flash the recovery version of stock rom. It's all available on this forum.
Click to expand...
Click to collapse
thx m8
I flashed with Miflash( and writed flash_all_lock.bat), used version V10.3.4.0. and it worked.. wifi working. (my build number say it is V10.3.6) ?
ticmali said:
thx m8
I flashed with Miflash( and writed flash_all_lock.bat), used version V10.3.4.0. and it worked.. wifi working. (my build number say it is V10.3.6) ?
Click to expand...
Click to collapse
Glad to hear you're phone is working fine now :highfive: :highfive:
I think you somehow had your wifi / mobile data on & the phone downloaded the OTA & auto updated itself to the latest firmware, that is V10.3.6.0.
evanB70 said:
Glad to hear you're phone is working fine now :highfive: :highfive:
I think you somehow had your wifi / mobile data on & the phone downloaded the OTA & auto updated itself to the latest firmware, that is V10.3.6.0.
Click to expand...
Click to collapse
yes, I had mobile data on. thanks
hello,
i was trying to install havoc on mi fresh new mi a3 i got stocked in fastboot. tried everthing but it give a status as "pause" in miflash or bat command.. what to do?
error message in bat command for V10.3.4.0.PFQMIXM_20190815 as in https://drive.google.com/open?id=1oLmwpDsd8ICUPsty46osBReJdcckqvPE please hekp
Underraino said:
hello,
i was trying to install havoc on mi fresh new mi a3 i got stocked in fastboot. tried everthing but it give a status as "pause" in miflash or bat command.. what to do?
error message in bat command for V10.3.4.0.PFQMIXM_20190815 as in https://drive.google.com/open?id=1oLmwpDsd8ICUPsty46osBReJdcckqvPE please hekp
Click to expand...
Click to collapse
Set active slot to a first before flashing in MiFlash using command - "fastboot set_active a" (without quotations) in adb command.
Underraino said:
hello,
i was trying to install havoc on mi fresh new mi a3 i got stocked in fastboot. tried everthing but it give a status as "pause" in miflash or bat command.. what to do?
error message in bat command for V10.3.4.0.PFQMIXM_20190815 as in https://drive.google.com/open?id=1oLmwpDsd8ICUPsty46osBReJdcckqvPE please hekp
Click to expand...
Click to collapse
Try my Procedere,i try it Yesterday and works:
-set SLOT B and install twrp
-then boot to TWRP recovery and Flash TWRP.zip again
-reboot to twrp recovery (Check If you on SLOT B ...)
-wipe Cache,system,Data
-flash Rom HAVOC
-flash TWRP
-reboot in TWRP again,then...
Set SLOT A!
-flash Gapps
-flash FDE
-Format Data
-Reboot to to System and wait when HAVOC done
Reboot to TWRP then Flash and root Magisk 20.2 in SLOT A, Reboot...
Done!
tried flashing my mi a3 to stock now stuck in fastboot mode
I finally got miflash to recognize my phone by adding a new folder and naming it "log" and i tried flashing "laurel_sprout_global_images_V10.3.8.0.PFQMIXM_20191012.0000.00_9.0_d099f2839b" ; it said it was flashing and had green progress bar, but it went all the way to 100% after about 600 seconds and i just gave up after 1200 seconds. what am I missing?
mewcatchew said:
I finally got miflash to recognize my phone by adding a new folder and naming it "log" and i tried flashing "laurel_sprout_global_images_V10.3.8.0.PFQMIXM_20191012.0000.00_9.0_d099f2839b" ; it said it was flashing and had green progress bar, but it went all the way to 100% after about 600 seconds and i just gave up after 1200 seconds. what am I missing?
Click to expand...
Click to collapse
Just reboot your device when it finishes after 600 seconds. Miflash doesn't tell you that it successfully flashed it it just goes on forever. So just reboot and it will work.
Negative. still stuck in fastboot mode
mewcatchew said:
Negative. still stuck in fastboot mode
Click to expand...
Click to collapse
Change the active slot to 'a' and reboot.
garylawwd said:
Just reboot your device when it finishes after 600 seconds. Miflash doesn't tell you that it successfully flashed it it just goes on forever. So just reboot and it will work.
Click to expand...
Click to collapse
msatyanarayana said:
Change the active slot to 'a' and reboot.
Click to expand...
Click to collapse
it's unable as its in a locked state: 'FAILED (remote: 'Slot Change is not allowed in Lock State
I believe I need to get it into EDL mode. I have no problem taking off the back glass and shorting the pins to do so, but not sure what to do after that point... Set slot to active "a", flash it with miflash with a fastboot stock ROM? Also from what ive read, you can only put thw phone into edl mode once so it's a one shot deal.
mewcatchew said:
it's unable as its in a locked state: 'FAILED (remote: 'Slot Change is not allowed in Lock State
I believe I need to get it into EDL mode. I have no problem taking off the back glass and shorting the pins to do so, but not sure what to do after that point... Set slot to active "a", flash it with miflash with a fastboot stock ROM? Also from what ive read, you can only put thw phone into edl mode once so it's a one shot deal.
Click to expand...
Click to collapse
Try to unlock bootloader once again through fastboot and after that you can change the slot.
MarcusMario0605 said:
Set active slot to a first before flashing in MiFlash using command - "fastboot set_active a" (without quotations) in adb command.
Click to expand...
Click to collapse
this command is not working for me it is giving error of unknown command
msatyanarayana said:
Try to unlock bootloader once again through fastboot and after that you can change the slot.
Click to expand...
Click to collapse
it wont allow me to< says phone is in locked state
123123123...123 said:
this command is not working for me it is giving error of unknown command
Click to expand...
Click to collapse
C:\adb\fastboot.exe: unknown option -- set-active=a
how to solve this?
:crying:
---------- Post added at 11:09 AM ---------- Previous post was at 11:05 AM ----------
MarcusMario0605 said:
Set active slot to a first before flashing in MiFlash using command - "fastboot set_active a" (without quotations) in adb command.
Click to expand...
Click to collapse
on entering this command i am getting a whole lot of command suggestion as this command not working for me. can you tell me what i am doing wrong and what should i do to make it correct.
123123123...123 said:
C:\adb\fastboot.exe: unknown option -- set-active=a
how to solve this?
:crying:
---------- Post added at 11:09 AM ---------- Previous post was at 11:05 AM ----------
on entering this command i am getting a whole lot of command suggestion as this command not working for me. can you tell me what i am doing wrong and what should i do to make it correct.
Click to expand...
Click to collapse
managed to get into EDL mode by shorting the pinouts, but still cant flash stock ROM cuz apparently xiaomi has to authorize it (ie i dont have permission to unbrick it). This is the first and last xiaomi phone I'll ever buy - never had a phone where there was no option i had to unbrick it. going to ****in smash it to peices!
I felt sorry that no one did help these people,
go to fastboot and run windows commands in twrp folder and type as following :
- option one:
fastboot devices
./fastboot set_active b
./fastboot erase boot
./fastboot set_active a
./fastboot erase boot
fastboot flashing unlock (optional)
fastboot Flash boot [put twrp name].img or go to mi flash to install stock rom. or unzip the stock rom from bat file run it
or try the second option:
https://ibb.co/w6bcG5g
islam=salam=peace=paix
Hi All,
I've been crawling the web the past few days to find a solution to my problem and unfortunately I didn't...
I have a Asus Zenfone 3 Max ZC520TL MT6737M, I never did a custom OS installation before and didn't know anything about how phone works except the Linux kernel
After 2 or 3 weeks playing with custom rom and recovery, softbrick, fastboot and adb I finally successfully intalled a custom OS, I wanted lineageOS but only found an Himax image working properly (with bluetooth., etc) for my phone and TWRP as custom recovery.
I setted my parameters for all my applications and after inserting my SIM card the network was not working, I tried a factory reset from the phone and then I got stuck in twrp however the way I booted, I tried flashing the os again, the recovery again wiping/formatting data, I was still stuck in TWRP
Then I executed :
fastboot format:ext4 cache
fastboot format:ext4 boot
And now I can't boot nor in twrp nor in fastboot, I can't access the bootloader using power and volume up, and my phone bootloop
Is there a way to get to fastboot to reinstall the recovery and then from here the os or is my phone hardbricked with no future, ready for trash?
Thank you
rominail said:
then I executed :
fastboot format:ext4 boot
Click to expand...
Click to collapse
You completely destroyed phone's boot-loader, what is comparable to a computer's BIOS.
What do you expect? IMO phone is case for the e-waste.
rominail said:
Hi All,
I've been crawling the web the past few days to find a solution to my problem and unfortunately I didn't...
I have a Asus Zenfone 3 Max ZC520TL MT6737M, I never did a custom OS installation before and didn't know anything about how phone works except the Linux kernel
After 2 or 3 weeks playing with custom rom and recovery, softbrick, fastboot and adb I finally successfully intalled a custom OS, I wanted lineageOS but only found an Himax image working properly (with bluetooth., etc) for my phone and TWRP as custom recovery.
I setted my parameters for all my applications and after inserting my SIM card the network was not working, I tried a factory reset from the phone and then I got stuck in twrp however the way I booted, I tried flashing the os again, the recovery again wiping/formatting data, I was still stuck in TWRP
Then I executed :
fastboot format:ext4 cache
fastboot format:ext4 boot
And now I can't boot nor in twrp nor in fastboot, I can't access the bootloader using power and volume up, and my phone bootloop
Is there a way to get to fastboot to reinstall the recovery and then from here the os or is my phone hardbricked with no future, ready for trash?
Thank you
Click to expand...
Click to collapse
You NEVER format your boot partition as ext4 it's a raw boot.img which holds the kernel and ramdisk. You should really do research and follow instructions alittle better than that.. unfortunately I don't think your device can be saved and if you flashed aboot or sbl1/2/3 then your SOL
Thanks
Thank you for your answers!
I don't know why I did that (sometimes I have crazy bad ideas), I didn't see that on internet
rominail said:
Thank you for your answers!
I don't know why I did that (sometimes I have crazy bad ideas), I didn't see that on internet
Click to expand...
Click to collapse
That's okay! Please so make sure you do some research if your new to the custom OS scene.. it's always good to learn new things
maybe you can flash again like from the factory by using the default flashing and ROM tools.
BryanHafidz said:
maybe you can flash again like from the factory by using the default flashing and ROM tools.
Click to expand...
Click to collapse
If your in a Qualcomm chipset and you have an EDL programmer that works for your device I have custom tools in my cloud storage to create an EDL firmware if you don't ready have one. If your on MTK then there is Sugar MTK or SP flash tool that can work. If your an another one you may be out of luck as it seems nobody has been able to restore those chipsets
EDIT: I do have a whole zip file of programmers and one that I use for my LG Zone 2 (msm8x10.mbn)
TheExploitedOne said:
You NEVER format your boot partition as ext4 it's a raw boot.img which holds the kernel and ramdisk. You should really do research and follow instructions alittle better than that.. unfortunately I don't think your device can be saved and if you flashed aboot or sbl1/2/3 then your SOL
Click to expand...
Click to collapse
we have the same problem but I didn't do like you.
I entered these commands
*fastboot flash recovery boot.img (I'm stupid lol)
*fastboot flash boot boot.img
*fastboot reboot*
mahirab23 said:
we have the same problem but I didn't do like you.
I entered these commands
*fastboot flash recovery boot.img (I'm stupid lol)
*fastboot flash boot boot.img
*fastboot reboot*
Click to expand...
Click to collapse
What seems to be going on after the flash?
TheExploitedOne said:
What seems to be going on after the flash?
Click to expand...
Click to collapse
the biggest problem is i have reset the phone and i am stuck with this message: "to start android enter your password". I entered the correct password but another message appears with a reset phone option.
Since the recovery.img file is no longer in the system, the phone keeps making this loop.
mahirab23 said:
the biggest problem is i have reset the phone and i am stuck with this message: "to start android enter your password". I entered the correct password but another message appears with a reset phone option.
Since the recovery.img file is no longer in the system, the phone keeps making this loop.
Click to expand...
Click to collapse
If you can get into fastboot run the following:
fastboot erase recovery
fastboot erase userdata
fastboot format:ext4 userdata
Then reflash your recovery
TheExploitedOne said:
If you can get into fastboot run the following:
fastboot erase recovery
fastboot erase userdata
fastboot format:ext4 userdata
Then reflash your recovery
Click to expand...
Click to collapse
I can't get into fastboot.
another solution?????
mahirab23 said:
I can't get into fastboot.
another solution?????
Click to expand...
Click to collapse
Can you access EDL mode?
TheExploitedOne said:
Can you access EDL mode?
Click to expand...
Click to collapse
thank you for your attention and suggestions.
I haven't tried this method yet.
I'm not good with EDL mode
Can SP tools and MiracleBox help me?
mahirab23 said:
thank you for your attention and suggestions.
I haven't tried this method yet.
I'm not good with EDL mode
Can SP tools and MiracleBox help me?
Click to expand...
Click to collapse
MiracleBox and QPST yes
TheExploitedOne said:
MiracleBox and QPST yes
Click to expand...
Click to collapse
good !!!: o: o
can you develop the method with Miracle Box and QPST ? please!!!
mahirab23 said:
good !!!: o: o
can you develop the method with Miracle Box and QPST ? please!!!
Click to expand...
Click to collapse
I have the tools needed in my cloud I can make into a zip file. You'll need to also do some research on your part but I can also write a readme file too so you have a basic understanding. Just give me a few to get the link
EDIT:
Here you go this has all you'll need for flashing your device in EDL as well as create the firmware if needed
https://mega.nz/file/rc8CVIiB#qnM3_ZzrvCJtp_M7Y9ZftZqDtGgWeN0tqFrLlT30pws
TheExploitedOne said:
MiracleBox and QPST yes
Click to expand...
Click to collapse
thank you
I finally managed to reset the phone thanks to SoftwareDownload
thank you really. you are really kind and available:bien::bien::bien:
mahirab23 said:
thank you
I finally managed to reset the phone thanks to SoftwareDownload
thank you really. you are really kind and available:bien::bien::bien:
Click to expand...
Click to collapse
Absolutely good sir! I'm glad that I can help
TheExploitedOne said:
If your in a Qualcomm chipset and you have an EDL programmer that works for your device I have custom tools in my cloud storage to create an EDL firmware if you don't ready have one. If your on MTK then there is Sugar MTK or SP flash tool that can work. If your an another one you may be out of luck as it seems nobody has been able to restore those chipsets
EDIT: I do have a whole zip file of programmers and one that I use for my LG Zone 2 (msm8x10.mbn)
Click to expand...
Click to collapse
Thank you for your help, unfortunately it's a mediatek
Hi all,
I'm starting to lose hope to get that thing working, despite following many tutorial, so I'm seeking a little help.
I got a Huawei P20 Lite because of battery issue that I fixed because it's a good training for me.
I fixed the battery and I also took the opportunity to Unlock it with the 2 pins and the PotatoNV tool. That part worked great and I'm now Phone and FRP Unlocked but them it went a little downhill and I may have soft-bricked it.
I'm used to Xiaomi phone where it's easy: unlock the bootloader, flash TWRP or OrangeFox, flash ROM, wipe thing and enjoy.
But here, I had to learn to flash a recovery_ramdisk and boot into it. The issue I had with TWRP is I can't seem to "format" Data, the partition is in F2FS and it stay stuck at "Done". So I tried multi tutorial, multi recovery version (TWRP and "stock") and multiple ROM with always issue to the point that now, it stay stuck at the TWRP logo or stuck at the warning when using the stock e-recovery.
I'm trying to understand the exact process to get it to work because following the Lineage tutorial, I get stuck at the wiping of Data and trying to find the right recovery and ROM so I not only can get the phone working but also be able to do update if it's possible on this phone.
I try to reuse the phone instead of putting it in recycle.
Thank for your help!
Hockpold said:
I'm trying to understand the exact process
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
-Alf- said:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
Click to expand...
Click to collapse
It stay stuck at the warning when using the eRecovery, so while I can send it, I can't Wipe Data/Factory Reset and through TWRP it also get stuck.
Hockpold said:
It stay stuck at the warning when using the eRecovery, so while I can send it, I can't Wipe Data/Factory Reset and through TWRP it also get stuck.
Click to expand...
Click to collapse
I don't know what the problem is, it works for me and you are the first one to have this problem.
Btw, it's not an eRecovery, it's Recovery .
Follow instructions in OP and use stock Recovery EMUI 9.1.
-Alf- said:
I don't know what the problem is, it works for me and you are the first one to have this problem.
Btw, it's not an eRecovery, it's Recovery .
Follow instructions in OP and use stock Recovery EMUI 9.1.
Click to expand...
Click to collapse
Where can I find the stock recovery? The other post it's either TWRP or the eRecovery.
Hockpold said:
Where can I find the stock recovery? The other post it's either TWRP or the eRecovery.
Click to expand...
Click to collapse
Are you sure?
-Alf- said:
To remove Magisk reinstall stock recovery_ramdisk via TWRP or fastboot , download Here
Click to expand...
Click to collapse
-Alf- said:
Are you sure?
Click to expand...
Click to collapse
Yeah, this one stay stuck at the yellow warning. I still have access to fastboot without issue.
Hockpold said:
Yeah, this one stay stuck at the yellow warning. I still have access to fastboot without issue.
Click to expand...
Click to collapse
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results .
-Alf- said:
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results .
Click to expand...
Click to collapse
Alright, here:
* get-build-number:
ANE-LX1 9.1.0.373(C109E7R1P3)
* get-product-model
ANE-LX1
* vendorcountry
orange/all
*oeminforead-CUSTOM_VERSION
ANE-LX1-CUST 9.1.0.7(C109)
*oeminforead-SYSTEM_VERSION
ANE-LX1 8.0.0.155(C109)
You might wanna take a look at my guide.
[GUIDE] [EMUI9] P20 Lite Basics
Special key combos: Power + Vol+ = Recovery Mode While USB connected, Power + Vol+ = Erecovery Mode While USB connected, Vol- = Fastboot Plug USB while holding down Vol+ + Vol- = Download Mode Power + Vol+ + Vol- = Force Dload Flashing Any GSI...
forum.xda-developers.com
Alright, seem like it worked.
I still have the issue that made me into this mess where I can't connect to a password protected Wi-Fi network (and the option to force to stay connected doesn't seem on CAOS unlike Lineage) but at least the rest is working, thank you.
Hockpold said:
I can't connect to a password protected Wi-Fi network
Click to expand...
Click to collapse
It should work with stock Kernel...
-Alf- said:
It should work with stock Kernel...
Click to expand...
Click to collapse
Does https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/ should also work or only the stock one?
Hockpold said:
Does https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/ should also work or only the stock one?
Click to expand...
Click to collapse
Yes, if you started from
TureX said:
Emui version < 9.1.0.300
Click to expand...
Click to collapse
-Alf- said:
Yes, if you started from
Click to expand...
Click to collapse
Alright, so just a fastboot flash kernel phenix.img or should I also do a factory reset (or reflash something else after)?
-Alf- said:
Yes, if you started from
Click to expand...
Click to collapse
HI!
This wifi problem has been fixed, I will release an img as soon as possible.
Cheers
Hockpold said:
Alright, so just a fastboot flash kernel phenix.img or should I also do a factory reset (or reflash something else after)?
Click to expand...
Click to collapse
if you have TWRP installed select Wipe > Advanced wipe > Dalvik/ART Cache, nothing else.
TureX said:
HI!
This wifi problem has been fixed, I will release an img as soon as possible.
Cheers
Click to expand...
Click to collapse
Oh!
That's very nice to hear, I'll be finally able to give a new life to this phone.