Hi, I was intending to restore my lenovo y90 to it's original state after root by flashing back the stock boot.img to boot partition by using flashboot and lock back the bootloader by command fastboot flashing lock after that using QFIL to flash the stock cn rom. Everything was going well till after flashing of the stock CN rom the screen show firmware corrupted and boot to fast boot mode, from there it kept stuck in fastboot and when I tried to unlock the bootloader using command fastboot flashing unlock it show FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed. Now I am stuck with unable to flash stock rom or install any recovery. When I choose recovery will only boot loop back to fastboot. Very much appreciate any help.
skuraieh said:
Hi, I was intending to restore my lenovo y90 to it's original state after root by flashing back the stock boot.img to boot partition by using flashboot and lock back the bootloader by command fastboot flashing lock after that using QFIL to flash the stock cn rom. Everything was going well till after flashing of the stock CN rom the screen show firmware corrupted and boot to fast boot mode, from there it kept stuck in fastboot and when I tried to unlock the bootloader using command fastboot flashing unlock it show FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed. Now I am stuck with unable to flash stock rom or install any recovery. When I choose recovery will only boot loop back to fastboot. Very much appreciate any help.
Click to expand...
Click to collapse
You shouldn't lock back bootloader before downgrade because google implement anti roll back. As what I read in China website once you lock back you cant downgrade anymore. There only one choice is to bring to service center. There only one qfil firmware for y90 which is 563. So I assume your version is higher than 563. Only unlock bootloader able to downgrade and flash qfil
I don't believe that is how the anti-roll-back feature works @darkidz555 . Considering the phone launched with android 12 the .563 firmware should fix his issue. You can find the QFIL package here and it appears you have to pay 20 rmb for it. Maybe someone already has it and would be kind enough to offer it here on xda?
&(*) said:
I don't believe that is how the anti-roll-back feature works @darkidz555 . Considering the phone launched with android 12 the .563 firmware should fix his issue. You can find the QFIL package here and it appears you have to pay 20 rmb for it. Maybe someone already has it and would be kind enough to offer it here on xda
I own y90 and this is how google anti rollback work for y90 and I already have qfil firmware you don't need to pay you just go to zui website and forum all the Chinese people share around the firmware and have step by step guide for root , downgrade , qcn , persist and etc in their WeChat group with all the firmware sharing inside the group as well. The Chinese people explain very well regarding this issue ONCE YOU LOCK BOOTLOADER AND FLASH QFIL THERE NO WAY TO SAFE YOUR DEVICE BECAUSE OF GOOGLE ANTI ROLLBACK. maybe Lenovo did something themself that why they never plan to release y90 for global.
Click to expand...
Click to collapse
@skuraieh ,
Have you attempted to wipe data? Plug in USB cable to side port and type: fastboot reboot fastboot , it will reboot into fastbootd and select wipe data and see if it boots.
&(*) said:
@skuraieh ,
Have you attempted to wipe data? Plug in USB cable to side port and type: fastboot reboot fastboot , it will reboot into fastbootd and select wipe data and see if it boots.
Click to expand...
Click to collapse
I am now stuck in fastboot mode with no wipe data option, and yes I have purchase the firmware for 20rmb and went through a lot of Hussle to download it as it require Baidu account as it use the cloud service. I would like to attached the firmware to help others as well but the files are 8gb zip file not sure how to attached it here
Use Google drive or make an account on Androidfilehost to share the firmware. I notice you posted that you have a Sahara error when trying to flash through QFIL, if that is the case, then you need to install the correct Qualcomm drivers. Upload the firmware first, that way it can be reviewed to see if it is in fact for an L71061 (Y90).
skuraieh said:
Hi, I was intending to restore my lenovo y90 to it's original state after root by flashing back the stock boot.img to boot partition by using flashboot and lock back the bootloader by command fastboot flashing lock after that using QFIL to flash the stock cn rom. Everything was going well till after flashing of the stock CN rom the screen show firmware corrupted and boot to fast boot mode, from there it kept stuck in fastboot and when I tried to unlock the bootloader using command fastboot flashing unlock it show FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed. Now I am stuck with unable to flash stock rom or install any recovery. When I choose recovery will only boot loop back to fastboot. Very much appreciate any help.
Click to expand...
Click to collapse
The real way flash y90 QFIL is using flat build select ddr file and select context.xml and then download. But since you lock your bootloader if possible try to unlock before QFIL else you will be hard Brick. Y90 can't be flash using normal meta build and select ddr and rawprogram0 and patch0. You must flash using context.xml. I've been back and forth downgrade and update multiple time can say more than 20x.
Thanks for the advice but the problem for me now is that I cannot unlock boot loader. Previously when boot loader was unlock I can easily flash the ROM.
skuraieh said:
Thanks for the advice but the problem for me now is that I cannot unlock boot loader. Previously when boot loader was unlock I can easily flash the ROM.
Click to expand...
Click to collapse
That what the info I get from Chinese y90 WeChat group. If you lock your bootloader then flash QFIL firmware while bootloader is lock there no other way to unbrick need to bring to service center because of google anti rollback. One question when flash QFIL firmware did it fully flash until system ownself reboot or Sahara error while flashing. If you fail to flash then it might have a chance to unbrick your device. If fully flash then even then Chinese y90 group also no way to unbrick. Your last choice is either reboot to fastbootd not normal fastboot is fastbootD and wipe data hope it boot else I cant help much. Try fastboot flash sn.img and then fastboot oem unlock-go again hope it help good luck
Thanks
darkidz555 said:
That what the info I get from Chinese y90 WeChat group. If you lock your bootloader then flash QFIL firmware while bootloader is lock there no other way to unbrick need to bring to service center because of google anti rollback. One question when flash QFIL firmware did it fully flash until system ownself reboot or Sahara error while flashing. If you fail to flash then it might have a chance to unbrick your device. If fully flash then even then Chinese y90 group also no way to unbrick. Your last choice is either reboot to fastbootd not normal fastboot is fastbootD and wipe data hope it boot else I cant help much. Try fastboot flash sn.img and then fastboot oem unlock-go again hope it help good luck
Click to expand...
Click to collapse
Thanks for the advise, yes I manage to fully flash the ROM till it auto restart using qfil when I lock the boot loader. I will try the fastbootd and see hope it works
skuraieh said:
Thanks
Thanks for the advise, yes I manage to fully flash the ROM till it auto restart using qfil when I lock the boot loader. I will try the fastbootd and see hope it works
Click to expand...
Click to collapse
Be it work or not work please update here at least other user get the idea.
This is nearly similar with your problem I guess chinese brand tend to make their own stuff. Lenovo did it differently by bricking your device if you flash edl firmware with bootloader lock
Back in July, Xiaomi rolled out MIUI 10 Global Beta 8.7.5 for eight Xiaomi devices. When users installed the update on their Xiaomi Redmi Note 5 Pro, they unknowingly flashed a build with anti-rollback protection enabled. Users who didn’t like MIUI 10 Global Beta found a nasty surprise when they tried to re-install the latest MIUI 9 Global Stable ROM: their phones were bricked! This wasn’t the kind of brick that you could fix by restoring a TWRP backup, flashing a new ROM, or using MiFlash to restore to a factory image. This is a hard, unrecoverable brick that requires the use of EDL mode to fix. But EDL mode isn’t accessible unless you have an authorized account, so many users were left with no way to fix their phone except sending it in to an authorized service center or paying to use someone’s account with EDL access. In this article, we’re going to explain everything you need to know about Xiaomi’s new anti-rollback protection so you can avoid bricking your new phone.
skuraieh said:
Hi, I was intending to restore my lenovo y90 to it's original state after root by flashing back the stock boot.img to boot partition by using flashboot and lock back the bootloader by command fastboot flashing lock after that using QFIL to flash the stock cn rom. Everything was going well till after flashing of the stock CN rom the screen show firmware corrupted and boot to fast boot mode, from there it kept stuck in fastboot and when I tried to unlock the bootloader using command fastboot flashing unlock it show FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed. Now I am stuck with unable to flash stock rom or install any recovery. When I choose recovery will only boot loop back to fastboot. Very much appreciate any help.
Click to expand...
Click to collapse
I know it is kind odd but I am on the path to root my y90... I have no ideia where to look at it. I see people commenting about chinese group but would you kindly point me to the root files needed (maybe twrp build too) not sure if there is a magisk port or whatever.
Thanks in advance
cardonarico said:
I know it is kind odd but I am on the path to root my y90... I have no ideia where to look at it. I see people commenting about chinese group but would you kindly point me to the root files needed (maybe twrp build too) not sure if there is a magisk port or whatever.
Thanks in advance
Click to expand...
Click to collapse
In order to root u need the china firmware and need magisk to create a modified boot.img.
Ok, I have the firmware, question is, will it work ?
I am king worried about brick my phone, do you tried that before ? did it work fine ? I ave been doing this for a while on other brands but lenovo seems to be a complete different beast
cardonarico said:
Ok, I have the firmware, question is, will it work ?
I am king worried about brick my phone, do you tried that before ? did it work fine ? I ave been doing this for a while on other brands but lenovo seems to be a complete different beast
Click to expand...
Click to collapse
It does work but remember to enable developer option and USB debugging and unlock boot loader and not to lock it back before doing the root.
darkidz555 said:
A maneira real do flash y90 QFIL está usando o arquivo ddr de seleção de compilação plana e selecione context.xml e, em seguida, faça o download. Mas desde que você bloqueie seu bootloader, se possível, tente desbloquear antes do QFIL, senão você ficará com o hard Brick. Y90 não pode ser flash usando meta build normal e selecione ddr e rawprogram0 e patch0. Você deve fazer o flash usando context.xml. Eu fui e voltei de downgrade e atualização várias vezes pode dizer mais de 20x.
Click to expand...
Click to collapse
Olá amigo, sou brasileiro e uso o Google tradutor, poderia fazer um vídeo ensinando como fazer root e instalar o TWRP no Lenovo Legion y90, estou aguardando meu aparelho chegar e não tem idioma português do Brasil para isso, eu acredito que um módulo de tradução ajudaria muito, e com Root e TWRP eu poderia realizar esse procedimento!!!
darkidz555 said:
You shouldn't lock back bootloader before downgrade because google implement anti roll back. As what I read in China website once you lock back you cant downgrade anymore. There only one choice is to bring to service center. There only one qfil firmware for y90 which is 563. So I assume your version is higher than 563. Only unlock bootloader able to downgrade and flash qfil
Click to expand...
Click to collapse
企业微信文档
企业微信文档-空白页
doc.weixin.qq.com
企业微信文档
企业微信文档-空白页
doc.weixin.qq.com
cardonarico said:
I know it is kind odd but I am on the path to root my y90... I have no ideia where to look at it. I see people commenting about chinese group but would you kindly point me to the root files needed (maybe twrp build too) not sure if there is a magisk port or whatever.
Thanks in advance
Click to expand...
Click to collapse
企业微信文档
企业微信文档-空白页
doc.weixin.qq.com
企业微信文档
企业微信文档-空白页
doc.weixin.qq.com
Translate and read carefully
cardonarico said:
Ok, I have the firmware, question is, will it work ?
I am king worried about brick my phone, do you tried that before ? did it work fine ? I ave been doing this for a while on other brands but lenovo seems to be a complete different beast
Click to expand...
Click to collapse
Yeah it worked, just follow the instructions in the wechat group.
Am currently rooted. Also note the Ramdisk yes or no in magisk to know whether to flash recovery or boot.img. in the wechat group the boot.img already provided for all roms released till date. Just patch and flash. Oem should be unlocked in develioer setting, then Bootloader must be unlocked in fastboot, before proceeding never lock back boot loader. As I mentioned before read the instructions carefully in the wechat groups.
https://doc.weixin.qq.com/doc/w3_Af0Alwb2ADI1SPrVvXuRMSe1k7YCa?scode=AOoATwelAA81ct055JAf0Alwb2ADI. ( This is for rooting)
https://doc.weixin.qq.com/doc/w3_Af0Alwb2ADIf1c8AEgvSQKFdc0JIx?scode=AOoATwelAA8M2GMdFmAf0Alwb2ADI. ( This is for flashing rom).
Translate the page
Related
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
_____________________________________________________________________________________________
UPDATE: The cell phone was completely downloaded. I plugged it into the computer and was able to enter Fastboot mode. So again I have TWRP for OREO.
But I still have a boot loop of "Error MODE". Any idea how to fix it?
TWRP 8 Oreo https://ibb.co/nEn5HS
Error MODE https://ibb.co/mrErrn
Aspiranteh said:
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock oem xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
Sorry bad english.
Click to expand...
Click to collapse
try to flash stock recovery then try force upgrade method.
h30_u10 said:
try to flash stock recovery then try force upgrade method.
Click to expand...
Click to collapse
Edit:
I can flash the recovery stock however, I don't know if in android OREO I can install full firmware through a folder (dload) on the SD card. Is there a similar way as in Nougat and earlier versions of android?
Try to flash your rom with twrp and install magisk before trying to boot into rom. Magisk patch boot.img and remove many security/error check when booting to rom.
rhaavin said:
Try to flash your rom with twrp and install magisk before trying to boot into rom. Magisk patch boot.img and remove many security/error check when booting to rom.
Click to expand...
Click to collapse
I'll give it a try. The problem is that the Rom Oreo I have is not flash for TWRP. I have searched but I still can't find an Oreo ROM that can be flashed by TWRP.
I found this method: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
that I think can work. However, it is for Mate 9, so I have to replace the files with those of Mate 10 lite and rename them as if they were Mate 9. Although I'm not sure what I should extract from Update.app to rename.
If someone could guide me, I'd be very grateful.
If that doesn't work, I will try this other method I found by browsing the forums. [ Chuckles]
https://forum.xda-developers.com/showpost.php?p=75628230&postcount=71
Any contribution is welcome.
Translated with www.DeepL.com/Translator
I stucked on the same or very similar fastboot screen, phones OS was oreo, here is why it happened:
I tried to use command fastboot flash recovery TWRP3.1.1.img
It will always show Failure message.
Then on this kind XDA forum I came to know that the recovery location is changed in oreo to
recovery_ramdisk I flashed with: fastboot flash recovery_ramdisk TWRP3.1.1.img
And thus reached the same fastboot error screen you have posted.
Workaround was: Get the update.app file from the update zip files (I used HWOTA method
to upgrade to Oero when my device was already soft bricked). So used update extractor
to pull out UPDATE.APP file form the biggesst update zip file from HWOTA folder,
but first u have to go to settings and disable header check sum option otherwise it will show error.
So I pulled out the proper stock recovery file named like: recovery_ramdisk.img
I used command: fastboot flash recovery_ramdisk revcovery_ramdiskimg
Now I got the stock recovery that I can use to wipe data and do factory reset.
So if you can come to this point, may be after factory reset you would be able to get it back.
Good luck.
Fix Error (SOLVE)
I can say from experience that the same thing happened to me, and the only thing you have to do is wait until your phone has a 0% charge, leaving the screen turned on with the error.
When that happens, connect the original cable to the PC and connect it in Fasboot mode, unlock the bootloader if you do not have it, then install the firmware of it ... with the HWOTA tool that you will see in one of the posts in this section ... you will have to have the three corresponding files of the same one ... the UPDATE, DATA, DATAPUBLIC and follow the steps in the post of HWOTA ... and you will relive your team.
Greetings ... I hesitate to answer for the difference of time and my work ... Greetings from Panama
Aspiranteh said:
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
_____________________________________________________________________________________________
UPDATE: The cell phone was completely downloaded. I plugged it into the computer and was able to enter Fastboot mode. So again I have TWRP for OREO.
But I still have a boot loop of "Error MODE". Any idea how to fix it?
TWRP 8 Oreo https://ibb.co/nEn5HS
Error MODE https://ibb.co/mrErrn
Click to expand...
Click to collapse
usman400 said:
I stucked on the same or very similar fastboot screen, phones OS was oreo, here is why it happened:
I tried to use command fastboot flash recovery TWRP3.1.1.img
It will always show Failure message.
Then on this kind XDA forum I came to know that the recovery location is changed in oreo to
recovery_ramdisk I flashed with: fastboot flash recovery_ramdisk TWRP3.1.1.img
And thus reached the same fastboot error screen you have posted.
Workaround was: Get the update.app file from the update zip files (I used HWOTA method
to upgrade to Oero when my device was already soft bricked). So used update extractor
to pull out UPDATE.APP file form the biggesst update zip file from HWOTA folder,
but first u have to go to settings and disable header check sum option otherwise it will show error.
So I pulled out the proper stock recovery file named like: recovery_ramdisk.img
I used command: fastboot flash recovery_ramdisk revcovery_ramdiskimg
Now I got the stock recovery that I can use to wipe data and do factory reset.
So if you can come to this point, may be after factory reset you would be able to get it back.
Good luck.
Click to expand...
Click to collapse
I also uploaded to OREO by HWOTA like you, I managed to do it without problems, all functional. Then I don't remember why but I decided to give wipes and that's when my problem started.
Yes, recovery_ramdisk was already in consideration.
I even flashed:
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash kernel kernel.img
fastboot flash system system.img
fastboot reboot
but I can't get it to start just throw that "MODE ERROR" at me, I don't think system is completely installed :/ /
emorenoebultron said:
I can say from experience that the same thing happened to me, and the only thing you have to do is wait until your phone has a 0% charge, leaving the screen turned on with the error.
When that happens, connect the original cable to the PC and connect it in Fasboot mode, unlock the bootloader if you do not have it, then install the firmware of it ... with the HWOTA tool that you will see in one of the posts in this section ... you will have to have the three corresponding files of the same one ... the UPDATE, DATA, DATAPUBLIC and follow the steps in the post of HWOTA ... and you will relive your team.
Greetings ... I hesitate to answer for the difference of time and my work ... Greetings from Panama
Click to expand...
Click to collapse
Yes, I really think this is the solution but it's only posted HWOTA and not HWOTA8 for Mate 10 lite... If there was only one HWOTA8 for our equipment, I'm sure I could fix it .
Aspiranteh said:
I also uploaded to OREO by HWOTA like you, I managed to do it without problems, all functional. Then I don't remember why but I decided to give wipes and that's when my problem started.
Yes, I really think this is the solution but it's only posted HWOTA and not HWOTA8 for Mate 10 lite... If there was only one HWOTA8 for our equipment, I'm sure I could fix it .
Click to expand...
Click to collapse
hmmm since I am all set with Oreo update and its working and I am not a very advanced user in flashing etc.
So am not going to any further thing until proper oreo update comes
But I was thinking at a point, why not go through existing HWOTA script, change the commands where recovery
is referred, (change recovery to recovey_ramdisk in any fastboot command found inside script), then running it to
try luck.
Also I think TWRP for mate 10 lite for Oreo version was made available a few days ago in this forum, search it
usman400 said:
hmmm since I am all set with Oreo update and its working and I am not a very advanced user in flashing etc.
So am not going to any further thing until proper oreo update comes
But I was thinking at a point, why not go through existing HWOTA script, change the commands where recovery
is referred, (change recovery to recovey_ramdisk in any fastboot command found inside script), then running it to
try luck.
Also I think TWRP for mate 10 lite for Oreo version was made available a few days ago in this forum, search it
Click to expand...
Click to collapse
Forgive my ignorance but what would be the script to edit, I downloaded the HWOTA again to modify it but I don't really know which file to modify. :confuso:
** @vovan1982 Hi, excuse me. I saw you post HwOTA for Mate 10 lite, do you know if there are any options for HwOTA8? Thank you very much in advance!
Aspiranteh said:
Forgive my ignorance but what would be the script to edit, I downloaded the HWOTA again to modify it but I don't really know which file to modify. :confuso:
** @vovan1982 Hi, excuse me. I saw you post HwOTA for Mate 10 lite, do you know if there are any options for HwOTA8? Thank you very much in advance!
Click to expand...
Click to collapse
If you can enter to trwp8, I can try to give you my backup of oreo mate 10. The problem for the script is, I think, the recovery push by vovan1982 is not comptatible with the aero installed, and when you are in twrp8, usb cable don't work!
gmbengue said:
If you can enter to trwp8, I can try to give you my backup of oreo mate 10. The problem for the script is, I think, the recovery push by vovan1982 is not comptatible with the aero installed, and when you are in twrp8, usb cable don't work!
Click to expand...
Click to collapse
If I have access to Twrp8, if you could share your backup with me I would be very grateful! :fingers-crossed:
Aspiranteh said:
If I have access to Twrp8, if you could share your backup with me I would be very grateful! :fingers-crossed:
Click to expand...
Click to collapse
I'm in L21. like I see, your model is L03. If you confirm that it's good I'll try to upload it. If someone can help for what to backup. It's too big (ramdisk, kernel, product, product image, cust, cust image,system, vendor, vendor image, version and version image)
gmbengue said:
I'm in L21. like I see, your model is L03. If you confirm that it's good I'll try to upload it. If someone can help for what to backup. It's too big (ramdisk, kernel, product, product image, cust, cust image,system, vendor, vendor image, version and version image)
Click to expand...
Click to collapse
If you please. If that's what you ask in MediaFire, there are 10 GB free to upload to the cloud. I know your help will help someone else at some point. . Thx.
file name is shell inside the folders find it or edit the .bat file to know where is the shell located
but if this is something new 4u then ask some one with little knowledge of MS DOS commands or shell scripts to edit it for u
Aspiranteh said:
If you please. If that's what you ask in MediaFire, there are 10 GB free to upload to the cloud. I know your help will help someone else at some point. . Thx.
Click to expand...
Click to collapse
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Lords, I have news for you. After many attempts I couldn't fix my "ERROR MODE", so I blocked the Bootloader and went to the shop to make my warranty effective... The technician believed my history that the phone was blocked after an update that appeared to me through OTA and will enforce my warranty because the phone presented "Factory Errors"... XD. Well, that's it, I've got my cell phone working again. Thank you all for your help.
gmbengue said:
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Click to expand...
Click to collapse
Maybe if you upload the backup you can help someone else in the future. Thank you very much for your willingness to help me. :good::fingers-crossed:
Urgent ordi 8.0 failed
gmbengue said:
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Click to expand...
Click to collapse
Bonjour
J'ai exactement le même problème.
Tu pourrais me donné le backup de ton mate 10 ton envie , s'il te plait.
Je serrais usurper heureux si tu pouvais m'aider.
Merci d'avance.
Je m'excuser ne parle pas anglais .
Up
RobotGuerrier said:
Bonjour
J'ai exactement le même problème.
Tu pourrais me donné le backup de ton mate 10 ton envie , s'il te plait.
Je serrais usurper heureux si tu pouvais m'aider.
Merci d'avance.
Je m'excuser ne parle pas anglais .
Click to expand...
Click to collapse
XDA Forum rules
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator.
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Arseon said:
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Click to expand...
Click to collapse
Go to TWRP and restore your system backup.
kilroystyx said:
Go to TWRP and restore your system backup.
Click to expand...
Click to collapse
But I didn't install a custom recovery. So no TWRP
Arseon said:
But I didn't install a custom recovery. So no TWRP
Click to expand...
Click to collapse
So, then try flash same system partition via fastboot.
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
What your build ?
If this phone with OREO or with NOUGAT / Android 8.x or 7.x ?
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Arseon said:
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Click to expand...
Click to collapse
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
kilroystyx said:
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
Click to expand...
Click to collapse
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Arseon said:
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Click to expand...
Click to collapse
It seems like you are doing well, but have you read the instructions carefully? They recommend when something fail.
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
AND very important : do not relock the bootloader !
ONLY if bootloader 'unlockt' you can self-repair !
JamesBott said:
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
Click to expand...
Click to collapse
Mine is ANE-AL00 8.0.0.131(C675). I used ANE-AL00C00B131 (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2370/g1789/v138744/f1/full/filelist.xml ) to flash
JamesBott said:
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
Click to expand...
Click to collapse
Sadly no. Both bootloader and frp are locked.
JamesBott said:
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
Click to expand...
Click to collapse
Since bootloader and frp locked, adb commands are not working. Hence I'm using DCPheonix to flash the file. But without luck. It's still botting to eRecovery only
your phone is C675, you flash C00 : no correct
now is inside your phone a 'mix'
i think, you can no self-repair - sorry
@Arseon, my opinion your system partition is a mess due to xposed installation fail.
The solution for this case is restore system partition, it worked for me in the past.
In some cases we can get lucky install a clean system partition even if it is from other region code, because the main differences between regions are located in the other partitions
But what I learning is that system from C00 region don’t follow this standard because at least is missing google apps.
With DCPheonix did with get lucky and flash all files or just the first 4 and stop in the PACKAGE_TYPE?
same situation
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Edit: I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
alvavaca said:
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Click to expand...
Click to collapse
This thread can help you a lot => HuRUpdater
kilroystyx said:
This thread can help you a lot => HuRUpdater
Click to expand...
Click to collapse
Thks for your help, I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Arseon said:
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
Click to expand...
Click to collapse
In pretty sure you are flashing the wrong firmware, try to push your version with dc-unlocker in fastboot and download the excatly matching firmware. Good luck
well, i have all of this+one more tougher stuff..
Well, I tried to install a custom ROM on my P20 Lite (ane-lx1) via TWRP aand when I failed I ended up into a bootloop, but the thing that got me a headache after a full day of forum research is that when I attempted to install the custom ROM the TWRP wanted a .img file, not a .zip file, so I rebooted after I alreday wiped out everything, I made a backup into the phone, BUT I cant access it because.. the TWRP freezes every time at the TeamWin logo.....the only thing that is accessible now its the fastboot&rescue mode and I'm out of juice and desperated...the bootloader is enabled...i think i preety much killed my phoen and my brain trying to get an android stock experience...i really have to get some sleep,well..thank you for your attention, if you have any suggestions that would pick me up from this mess I would be very greatfull, i'll see what i had left to do as soon as i'm able to...for now, have a good night/day/afternoon, whatever side of the world you're from
Edit:
I left the phone all night into bootloobing and after it got FULLY discharged, I dont know exactly how but the TWRP hasn't popped out, instead after this I was able to get into eRecovery and now it is downloading the 146(C432) version. I guess that I got lucky
Recently because of an error when it was flashing my phone got bricked. I tried to solve the problem by doing these steps:
1. I made a backup of another Doogee N20 phone (working phone, same firmware version as mine, but it has a locked Bootloader (If someone wonders why I don't unlock the phone's Bootloader directly, it's because the phone is not mine. )
2. I formatted the phone via SP Flash Tool.
3. I flashed the backup preloader.bin via Miracle Box (When I flash it via SP Flash Tool, at the end of flashing gives me an error) .
But when I try to flash everything except the preloader via SP Flash Tool, it gives me this error: STATUS_SEC_IMG_TYPE_MISMATCH
I read in this thread (forum.hovatek.com/thread-439.html) that the error may be because of the preloader.bin which was taken from a phone with a locked Bootloader.
If so, is there anyone who knows where I can get the latest version of the stock ROM? (Version of my firmware: DOOGEE_N20_Android9.0.0-20200228), (On the internet I found only the old firmware version, and it is not supported by this phone).
If not, tell me what I can do!
Thanks in advance!
Modified:
I fixed the problem:
1. I found an updated Stock ROM on internet (rom.oscarmini.com/doogee-n20/).
2. I formatted the phone via SP Flash Tool.
3. I flashed the preloader.bin via SP Flash Tool.
4. I flashed the entire Stock Rom except preloader.bin via SP Flash Tool.
5. Done (Boot normally).
Official Doogee N20 and Doogee N20 firmware (probably first original firmware
IosifMihaescu said:
Recently because of an error when it was flashing my phone got bricked. I tried to solve the problem by doing these steps:
1. I made a backup of another Doogee N20 phone (working phone, same firmware version as mine, but it has a locked Bootloader (If someone wonders why I don't unlock the phone's Bootloader directly, it's because the phone is not mine. )
2. I formatted the phone via SP Flash Tool.
3. I flashed the backup preloader.bin via Miracle Box (When I flash it via SP Flash Tool, at the end of flashing gives me an error) .
But when I try to flash everything except the preloader via SP Flash Tool, it gives me this error: STATUS_SEC_IMG_TYPE_MISMATCH
I read in this thread (forum.hovatek.com/thread-439.html) that the error may be because of the preloader.bin which was taken from a phone with a locked Bootloader.
If so, is there anyone who knows where I can get the latest version of the stock ROM? (Version of my firmware: DOOGEE_N20_Android9.0.0-20200228), (On the internet I found only the old firmware version, and it is not supported by this phone).
If not, tell me what I can do!
Thanks in advance!
Modified:
I fixed the problem:
1. I found an updated Stock ROM on internet (rom.oscarmini.com/doogee-n20/).
2. I formatted the phone via SP Flash Tool.
3. I flashed the preloader.bin via SP Flash Tool.
4. I flashed the entire Stock Rom except preloader.bin via SP Flash Tool.
5. Done (Boot normally).
Click to expand...
Click to collapse
Hey man
The real issue if no one currently has posted the verified images
I will hopefully be having a new Doogee N20 Doogee Y9 plus forum where if allowed I will be posting solutions with official stock-verified firmware will post link as soon as possible and sorry for any delays caused
i need help, i was trying to reinstall the rom stock of my doogee n20 then there was an error and now it doesn't give the life signal, it doesn't turn on, it only gives the signal when connecting to the pc via the usb cable, but it keeps connecting and disconnecting, HELP ME!
thalesmuniz said:
i need help, i was trying to reinstall the rom stock of my doogee n20 then there was an error and now it doesn't give the life signal, it doesn't turn on, it only gives the signal when connecting to the pc via the usb cable, but it keeps connecting and disconnecting, HELP ME!
Click to expand...
Click to collapse
Try this:
1. Download this Stock ROM (rom.oscarmini.com/doogee-n20/).
2. Format the phone via SP Flash Tool.
3. Flash only the preloader.bin via SP Flash Tool.
4. Flash the entire Stock Rom except preloader.bin via SP Flash Tool.
5. Done (Boot normally).
IosifMihaescu said:
Try this:
1. Download this Stock ROM (rom.oscarmini.com/doogee-n20/).
2. Format the phone via SP Flash Tool.
3. Flash only the preloader.bin via SP Flash Tool.
4. Flash the entire Stock Rom except preloader.bin via SP Flash Tool.
5. Done (Boot normally).
Click to expand...
Click to collapse
___________________________________________________________
what do you mean by this line,
'' 2. Format the phone via SP Flash Tool ''
.how do you do it? because every attempt I make to the red bar and infinite count, which cell phone drivers, where do I find them?
thalesmuniz said:
___________________________________________________________
what do you mean by this line,
'' 2. Format the phone via SP Flash Tool ''
.how do you do it? because every attempt I make to the red bar and infinite count, which cell phone drivers, where do I find them?
Click to expand...
Click to collapse
First you need to select the scatter file of the downloaded ROM in SP Flash tool! (If you not choose the scatter file before going to format, it fails!) After that go into format section and tap start.
thalesmuniz said:
___________________________________________________________
what do you mean by this line,
'' 2. Format the phone via SP Flash Tool ''
.how do you do it? because every attempt I make to the red bar and infinite count, which cell phone drivers, where do I find them?
Click to expand...
Click to collapse
hi, did you manage to fix this problem?
I have a n20 that does not turn on, only gives signal on the pc, I try to format it by the sp flash tool, but it is only the red bar.
Sorry for bad English
dansnakeeater said:
hi, did you manage to fix this problem?
I have a n20 that does not turn on, only gives signal on the pc, I try to format it by the sp flash tool, but it is only the red bar.
Sorry for bad English
Click to expand...
Click to collapse
First, you need to select the scatter file of the downloaded ROM in the SP Flash tool! (If you do not choose the scatter file before going to format, it fails!) After that go into the format section and tap start.
IosifMihaescu said:
Primeiro, você precisa selecionar o arquivo scatter da ROM baixada na ferramenta SP Flash! (Se você não escolher o arquivo scatter antes de formatar, ele falhará!) Depois disso, vá para a seção de formatação e toque em iniciar.
Click to expand...
Click to collapse
Tam aqui aparece a barra vermelha e nao da certo, ja tentei como voce exemplificou no post anterior
Diego1323 said:
Tam aqui aparece a barra vermelha e nao da certo, ja tentei como voce exemplificou no post anterior
Click to expand...
Click to collapse
Hi, could you write in English? Because I can't understand exactly what you mean using Google Translate. Thanks.
flairepathos.info said:
Official Doogee N20 and Doogee N20 firmware (probably first original firmware
Hey man
The real issue if no one currently has posted the verified images
I will hopefully be having a new Doogee N20 Doogee Y9 plus forum where if allowed I will be posting solutions with official stock-verified firmware will post link as soon as possible and sorry for any delays caused
Click to expand...
Click to collapse
Hi so the fix for the doogee y9 plus brickedd comes in 2 forms
the normal brick and doogee n20 firmware variant to fix the doogee y9 plus after bricking if n20 firmware refusing flash is to
search google for doogee y9 plus fimware (in chinese, copy and paste some website need you to have account with them) there will be eea version the official firmware rollout version which will work with spflasher to unbrick your device
So if the posted method doesnt work search this in chinese(google translate) on google "doogee y9 plus firmware"
there will be a site i bilieve arabic? "halab ...."
there will be official songxlin eea, user, and russia firmware(user works best) (they work for y9 plus devices blocked from flashing n20 firmware )
Note: This process is shown for OnePlus Nord 2 and work for any MTK device just replace files as per your model you need to Serch for that)
Credits @Raygen @TheWing
After relocking bootloader you can do safety net pass check to confirm by using following app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettes
Download Re LiveDVD mtk. Client ( this is ready mtk client ubuntu os no need to Install python, drivers ready to go iso)
re_livedvdV3.iso
drive.google.com
Download Rufus for windows 32/64bit)
https://github.com/pbatard/rufus/releases/download/v3.17/rufus-3.17.exe
Note:Relocking has been done on OOS 11.1 v13 so stock boot img of v13, vbmeta from update zip of v13 is required, recovery must be given below.
Your need to replace files as per oxygen os version you are using.
FOLLOWING are images of DN2101 A13 OOS UPDATE IMAGES EXCEPT RECOVERY IMAGE IT WILL WORK IN ANY PHONE, U NEED YOUR AS PER YOUR REGION I WILL UPDATE THREAD AFTER COLLECTING ALL HERE
Boot img (This is stock A13 indian, other regions must use there current OOS version boot img)( other mtk devices must use there boot img here)
https://forum.xda-developers.com/attachments/boot-img.5460945/
Stock recovery(in zip unzip it you will get img file this will work for any region)( other mtk devices must use there recovery img here)
https://forum.xda-developers.com/attachments/recovery_stock-zip.5464685/
Vbmeta:must have correct vbmeta of current OOS Rom. Version (from stock A13 indian update.zip if U r using EU, OR GLOBAL region NORD replace it with the current OOS version you are for which you want to relock)(other mtk devices must use there vbmeta img here)
vbmeta.img
drive.google.com
All files for EU DN2103 ON A12 UPDTAE :
EU varient v12 files:
Boot. Img:
https://forum.xda-developers.com/attachments/boot_stock_a12-img.5461083/
Vbmeta. Img/
vbmeta.img
drive.google.com
Recovery same link for all)
recovery_stock.zip
drive.google.com
Terminal emulator commands :
1) BOOT TO FASTBOOT connect phone to pc in on condition)
adb reboot fastboot
2)to relock bootloader in terminal emulator connect phone to pc in fastboot mode and type)
fastboot flashing lock
MTK client commands:
1)Flash boot img:
python mtk w boot boot.img
2) Flash recovery img:
python mtk w recovery recovery.img
3) Flash Vbmeta :
python mtk w vbmeta vbmeta.img
wifi is not working. everything working after relock bootloader but wifi is not working
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
Factory reset u r phone and reboot see
pankspoo said:
Factory reset u r phone and reboot see
Click to expand...
Click to collapse
i did it. but it's not working
farhansaeeddnp3021 said:
i did it. but it's not working
Click to expand...
Click to collapse
Update yourbphone to latest v14
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
NetSoerfer said:
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
Click to expand...
Click to collapse
Your device will go in to boot img corrupt after that.......
PLEASE NOTE: This isnt working if you are on a custom rom! My Bootloader ist broken and locked and I have to figure out how to fix this ****.
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
7tyjupiter said:
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
Click to expand...
Click to collapse
Check YASNAC app from play store if it's showing safety net check passed your locked.
While installation of OTA what's errors u r getting.
After locking OEM unlock not grates off actually now it's available to unlock again with switchable tab
Sorry for crossposting a lot today, but I am really stuck and it seems that this may be the tool I need. I am on A15, cannot lock bootloader and cannot update.
So, to be sure, for this to work I need the boot.img, recovery.img and vbmeta.img for A15 stock rom? If yes, where can I get those files?
I found the files! Thank you for this guide! It worked perfectly. I really thought my phone was completely bricked. Coming from a Pixel, the root/restore process on this thing is a complete nightmare!!
https://forum.xda-developers.com/attachments/boot-img.5460945/
this link says like this
Oops! We broke the matrix. Someone call Neo!You do not have permission to view this page or perform this action.
Ok. So I think if f-ed up big time! only message I get now is a big red "!" and: "the current image have been destroyed please flash te correct image....
HELP!
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
lachatol said:
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
Click to expand...
Click to collapse
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
exis_tenz said:
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
Click to expand...
Click to collapse
I want to lock the botloader, I don't want root anymore. I just need to be sure that if I service the phone for reinstallation to the original firmware, then the bootloader will be locked. Will be? thank you for answer
No worries, it'll be locked after a factory flash!
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
extranoob said:
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
Click to expand...
Click to collapse
If u gets wifi issue just flash boot image of OOS version u r using via fastboot
Hi everyone, sorry for my bad english but i sure we can help me to find a PIXEL EXPERIENCE fluid rom for my Xiaomi Mi 11 Lite 5G (8+128).
I searched the entire internet to find the rom but none of that are good for myself.
FCsperimentx said:
Hi everyone, sorry for my bad english but i sure we can help me to find a PIXEL EXPERIENCE fluid rom for my Xiaomi Mi 11 Lite 5G (8+128).
I searched the entire internet to find the rom but none of that are good for myself.
Click to expand...
Click to collapse
you have to take GSI rom here..
You can check my personal PE 12.0 build, been using it for 2 weeks and it works alright not 100% perfect.
Releases · aurotones/renoir
Contribute to aurotones/renoir development by creating an account on GitHub.
github.com
Ho un grosso problema sul mio dispositivo: quando provo a installare una rom personalizzata lo smartphone si blocca sul bootloop e I install again the stock miui con MIFlashTool.
I tried everything but the smartphone still have this problem.
FCsperimentx said:
Ho un grosso problema sul mio dispositivo: quando provo a installare una rom personalizzata lo smartphone si blocca sul bootloop e I install again the stock miui con MIFlashTool.
I tried everything but the smartphone still have this problem.
Click to expand...
Click to collapse
i updated install instructions. Also don't forget you must be on MIUI 12.5.7 firmware base.
I downloaded MIUI 12.5.7 but everything is the same.
Now when i write .\adb reboot fastboot the phone reboot itself on FASTBOOTD.
I tried everything but nothing just change because the xiaomi’s stuck on bootloop.
FCsperimentx said:
I downloaded MIUI 12.5.7 but everything is the same.
Now when i write .\adb reboot fastboot the phone reboot itself on FASTBOOTD.
I tried everything but nothing just change because the xiaomi’s stuck on bootloop.
Click to expand...
Click to collapse
You downloaded MIUI 12.5.7 is a good start but you could have alternatively download and flash only the firmware base which is only about 100MB. Also I see the instructions were not 100% clear, hope this will be clear enough for you. Also before you do, backup your files!
1. You supposed to go into bootloader, not fastboot.
Code:
adb reboot bootloader
2. Flash boot.img and vendor_boot.img files through fastboot command on your PC.
Code:
fastboot flash boot_ab ./boot.img
fastboot flash vendor_boot_ab ./vendor_boot.img
3. Now you need to go into recovery mode. It should say pixel experience recovery on top of the screen.
Code:
fastboot reboot recovery
4. Select Apply update -> Apply from ADB.
5. Now sideload the zip file through adb command on your PC
Code:
adb sideload ./PixelExperience_renoir-***.zip
6. You may need to format your data so it will boot properly.
Above commands are examples but might be different on your type of operating system you're using, so take them as example, not the exact command that will guaranteed to work.
If you're still having problem then, there's underlying problem that i'm not aware of and hope someone else will help you to flash it.
Hi, I don't get it I tried everything can't make it work. I finally flashed vendor_boot, and booted on TWRP 3.6.1_11-0 in order to manage to side load on Renoir, and I get this error all time (with the 12 and 12 plus official release of pixel experience) as on the picture.
Could you help me, it's been 6 month I don't manage to installé any pixel experience on this phone. First time I' m stuck with a smartphone ever ... Official/gsi nothing works, I only manage to flash the MIUI ROM and lineage os....
I'm desperate .
Eightkiller said:
Hi, I don't get it I tried everything can't make it work. I finally flashed vendor_boot, and booted on TWRP 3.6.1_11-0 in order to manage to side load on Renoir, and I get this error all time (with the 12 and 12 plus official release of pixel experience) as on the picture.
Could you help me, it's been 6 month I don't manage to installé any pixel experience on this phone. First time I' m stuck with a smartphone ever ... Official/gsi nothing works, I only manage to flash the MIUI ROM and lineage os....
I'm desperate .
Click to expand...
Click to collapse
TWRP doesn't support Android 12 yet, you need LineageOS or Pixel Experience recovery to sideload.
Edit: Follow instructions here: https://wiki.pixelexperience.org/devices/renoir/install/
aurotones said:
TWRP doesn't support Android 12 yet, you need LineageOS or Pixel Experience recovery to sideload.
Edit: Follow instructions here: https://wiki.pixelexperience.org/devices/renoir/install/
Click to expand...
Click to collapse
Thx for your answer the problem is I can't manage to boot on pixel experience recovery as shown in the tutorial. It says ok when I flash but I can only get to fastboot. And when I just try to fastboot boot 'myrecovery.img', it just rebbotsyto fastboot. That's why I tried to boot on TWRP which works without any trouble :s
Eightkiller said:
Thx for your answer the problem is I can't manage to boot on pixel experience recovery as shown in the tutorial. It says ok when I flash but I can only get to fastboot. And when I just try to fastboot boot 'myrecovery.img', it just rebbotsyto fastboot. That's why I tried to boot on TWRP which works without any trouble :s
Click to expand...
Click to collapse
TWRP will never work but while you're on TWRP your base should be on V12.5.7.0.RKIEUXM, flash that first in TWRP and then maybe try flash boot.img and vendor_boot.img and go to recovery mode. Without it you will never be able to install. Please give me details what your phone is, is it 5G variant with renoir codename?, is it global or china?, did it had MIUI 12.5 or 13?, these informations are necessary.
aurotones said:
TWRP will never work but while you're on TWRP your base should be on V12.5.7.0.RKIEUXM, flash that first in TWRP and then maybe try flash boot.img and vendor_boot.img and go to recovery mode. Without it you will never be able to install. Please give me details what your phone is, is it 5G variant with renoir codename?, is it global or china?, did it had MIUI 12.5 or 13?, these informations are necessary.
Click to expand...
Click to collapse
It had MIUI 12.x and it is a "eu" phone, I tried to flash the V12.5.7.0.RKIEUXM (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0) from twrp it's not working with the same errors messages. I don't really know what to do, i managed to put back my 12.6 beta stock miui from "xiaomi.eu_multi_MI11Lite5G_21.7.7_v12-11-fastboot" version.
When i'm stuck i'm forced to install this back to not be stuck on fastboot loop. I found a "renoir_eea_global_images_V12.5.7.0.RKIEUXM_20220105.0000.00_11.0_eea" fastboot version but the installation is not working (would you have one working from my config ?).
I also tried to flash the firmware (fw_renoir_miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0 ~104mo) which gave me an "orange" fastboot instead of the fastboot with the funny character. And tried to install the recovery from pixel after but still stuck on fastboot.
Hope it will help you a bit more to help me
Eightkiller said:
It had MIUI 12.x and it is a "eu" phone, I tried to flash the V12.5.7.0.RKIEUXM (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0) from twrp it's not working with the same errors messages. I don't really know what to do, i managed to put back my 12.6 beta stock miui from "xiaomi.eu_multi_MI11Lite5G_21.7.7_v12-11-fastboot" version.
When i'm stuck i'm forced to install this back to not be stuck on fastboot loop. I found a "renoir_eea_global_images_V12.5.7.0.RKIEUXM_20220105.0000.00_11.0_eea" fastboot version but the installation is not working (would you have one working from my config ?).
I also tried to flash the firmware (fw_renoir_miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0 ~104mo) which gave me an "orange" fastboot instead of the fastboot with the funny character. And tried to install the recovery from pixel after but still stuck on fastboot.
Hope it will help you a bit more to help me
Click to expand...
Click to collapse
i feel like your partition is messed up by TWRP so my advice is clean flash V12.5.7.0 fastboot rom with method of "flash_all.bat" on windows, "flash_all.sh" on linux i forgot the filenames but there's also method with lock in the name which you should avoid and then never touch or install TWRP as it's a bit unstable even with Android 11 roms, now you flash boot.img and vendor_boot.img provided by Pixel Experience through bootloader that only spells fastboot, no extra letter at the end.
This is important, Rebooting into bootloader and fastboot is different, when you do 'adb reboot fastboot' it will show fastbootd with orange text which something you should avoid, instead do 'adb reboot bootloader' or by vol down + power button and flash those 2 files.
If you still having problems try changing your boot slot by
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
And then
Code:
fastboot reboot recovery
If you still having problems, then head over to this telegram group and get help from ROM maintainer: https://t.me/arixelogroup
The Official build Pixel Experience is now available for renoir
It works perfectly on my device
PE for renoir
RGB39 said:
The Official build Pixel Experience is now available for renoir
It works perfectly on my device
PE for renoir
Click to expand...
Click to collapse
Attention that, Don't flash miui13 before flashing pe, or your wlan won't work.
aurotones said:
i feel like your partition is messed up by TWRP so my advice is clean flash V12.5.7.0 fastboot rom with method of "flash_all.bat" on windows, "flash_all.sh" on linux i forgot the filenames but there's also method with lock in the name which you should avoid and then never touch or install TWRP as it's a bit unstable even with Android 11 roms, now you flash boot.img and vendor_boot.img provided by Pixel Experience through bootloader that only spells fastboot, no extra letter at the end.
This is important, Rebooting into bootloader and fastboot is different, when you do 'adb reboot fastboot' it will show fastbootd with orange text which something you should avoid, instead do 'adb reboot bootloader' or by vol down + power button and flash those 2 files.
If you still having problems try changing your boot slot by
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
And then
Code:
fastboot reboot recovery
If you still having problems, then head over to this telegram group and get help from ROM maintainer: https://t.me/arixelogroup
Click to expand...
Click to collapse
Thx, but that's what i'm trying to do since yesterday, but i don't manage to fresh install 12.5.7.0 with the fastboot rom i found (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0
I always get errors when i run the flash_all.bat, saying that my rom is more recent than the one i'm trying to flash. I tried to delete the "if statement" checking for the versions, but seems to mess up with the "directories name" after.
Would you have some link or place where i can get a working 12.5.7.0 with fastboot install ? I'll try it properly from this one.
Thanks in advance.
Eightkiller said:
Thx, but that's what i'm trying to do since yesterday, but i don't manage to fresh install 12.5.7.0 with the fastboot rom i found (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0
I always get errors when i run the flash_all.bat, saying that my rom is more recent than the one i'm trying to flash. I tried to delete the "if statement" checking for the versions, but seems to mess up with the "directories name" after.
Would you have some link or place where i can get a working 12.5.7.0 with fastboot install ? I'll try it properly from this one.
Thanks in advance.
Click to expand...
Click to collapse
Use XiaoMiFlash
Download Official Xiaomi Mi Flash Tool All Versions
xiaomimiflashtool.com
or fastboot v29.0.5
Download Platform Tools for Android SDK Manager
Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net
mitanyan98 said:
Use XiaoMiFlash
Download Official Xiaomi Mi Flash Tool All Versions
xiaomimiflashtool.com
or fastboot v29.0.5
Download Platform Tools for Android SDK Manager
Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net
Click to expand...
Click to collapse
Thx for your answer, as i was saying: same error with mi flash tool (look the screenshot)
And if i comment the "checking parts" inside the .bat files, i get directories error on windows: it does not seem to check properly my direcotries name
for example a line is like this:
fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
the %~dp0images seems to be my path, but it's not taken properly into accoutn, seems to have " quote problems with the path
Edit: I had to double quote " the path inside the script as my path was having spaces inside
Thx for you help, I managed to install it, the only problem was to properly install 12.5.7 After succeding that everything worked as it should
RGB39 said:
Attention that, Don't flash miui13 before flashing pe, or your wlan won't work.
Click to expand...
Click to collapse
So that's why... so many hours wasted trying to get Wi-Fi to work. I had the "fantastic idea" of flashing the official global miui (renoir_global_images_V13.0.4.0.SKIMIXM_20220412....) prior to installing DotOS and when wi-fi did not work, flashed Pixel Experience...
And I'm pretty sure flashing miui 12.x will trigger ARB and brick the phone. Right?