Hi,
I will release here my updated "boot.img" files for the Xperia XA Single Sim.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file, on 33.2.B.4.70 and upper "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
The Fastboot command is:
fastboot flash boot NAMEOFIMAGE.img
Click to expand...
Click to collapse
Releases for Marshmallow:
2016/07/31: From 33.2.A2.73 kernel sources and Ramdisk from 33.2.A.2.73 firmware. (Works up to 33.2.A.3.123)
https://mega.nz/#!s4ZR0Baa!irwu16tVxfM7nzX-B-DVaO7E6RErePHkxi3yVu45pac
2017/03/19: From 33.2.A.4.70 kernel sources and Ramdisk from 33.2.A.4.70 firmware.
https://mega.nz/#!g9h3SYgT!iUEpKOhUZQyEh5GVa2WxTgwxF0bhz9rCwYMcnPSNkr8
Releases for Nougat:
2017/07/18: From 33.3.A.0.131 kernel sources and Ramdisk from 33.3.A.0.131 FR firmware.
https://mega.nz/#!MlZkADRC!rvLdH400qLF3YG04beulKsGMpiDNooDRT7j5XgxNPCc
I neel help endelss loop
I tried to follow the guide.. I think the problem is the step 8
8. Flash recovery and boot with "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" commands (rename downloaded boot/recovery image if needed). The simplest way is to use fastboot from Flashtool in x10flasher folder, copy recovery and boot in it, open command prompt, flash them and then delete them.
I did an now my cellphone is in a endless loop , I think the problem is the boot.img my model is 3213
pls help me.
Kawaxi said:
I tried to follow the guide.. I think the problem is the step 8
8. Flash recovery and boot with "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" commands (rename downloaded boot/recovery image if needed). The simplest way is to use fastboot from Flashtool in x10flasher folder, copy recovery and boot in it, open command prompt, flash them and then delete them.
I did an now my cellphone is in a endless loop , I think the problem is the boot.img my model is 3213
pls help me.
Click to expand...
Click to collapse
F3213 is XA Ultra single sim. Boot.img from this thread are for the XA not Ultra. Try with the good one
rrvuhpg said:
F3213 is XA Ultra single sim. Boot.img from this thread are for the XA not Ultra. Try with the good one
Click to expand...
Click to collapse
yes, thankfully using the correct boot.img fixed the problem, that file is also in this forum.
However I can't seem to be able to continue with the guide to root the phone, I fail to run into TWRP mode no matter what, I have even tried with adb, coudl be that recovery.img is also the wrong version?
Any ideas?
Kawaxi said:
yes, thankfully using the correct boot.img fixed the problem, that file is also in this forum.
However I can't seem to be able to continue with the guide to root the phone, I fail to run into TWRP mode no matter what, I have even tried with adb, coudl be that recovery.img is also the wrong version?
Any ideas?
Click to expand...
Click to collapse
Probably, you have to flash the recovery for your model too. For the F3213 use the recovery from this rootpack (extract the zip file)
https://forum.xda-developers.com/xa-ultra/development/rootpack-xperia-xa-ultra-single-sim-t3446203
rrvuhpg said:
Probably, you have to flash the recovery for your model too. For the F3213 use the recovery from this rootpack (extract the zip file)
https://forum.xda-developers.com/xa-ultra/development/rootpack-xperia-xa-ultra-single-sim-t3446203
Click to expand...
Click to collapse
it worked !!! , thanks a lot my friend....
one question , does this version still have the problem with the camera when rooting?
How to recognize which .sin is a kernel.sin in FTF file ?
If I could ask a question how to find kernel.sin in my stock rom ftf file, after of course ftf is unpacked (7-zip) ?
I have a file called fotakernelxxx.sin but I don't see a file kernel.sin ? I assume that kernel.sin exists so how to find it ?
There are many files with .sin extension - which one should I pick ?
regards,
xperia xa no arranca
rrvuhpg said:
Hi,
I will release here my updated "boot.img" files for the Xperia XA Single Sim.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file, on 33.2.B.4.70 and upper "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
hola amigo disculpa la ignorancia pero ese archivo que pones para el xperia xa donde y como se instala?
tengo un grande problema con mi xperia xa casi nuevo me lo enviaron de usa y como todo fan de Sony cuando lo tuve el primer dia decidi flashearlo para poder rootearlo y desde ese entonces ya no puedo prenderlo al parecer cometi un error pero te dire que hasta el xperia companion no me soluciona ni tampoco poniendo una y otra vez un nuevo firmware con el falshtool. Micelular solo se queda en el logo del operador.
Click to expand...
Click to collapse
@erimi.rc in English please.
...
rrvuhpg said:
@erimi.rc in English please.
Click to expand...
Click to collapse
Hello friend excuse ignorance but that file you put for xperia xa where and how it installs?
I have a big problem with my xperia xa almost new I was sent from usa and like every fan of Sony when I had the first day I decided to flash it to be able to rootearlo and since then I can not turn it on apparently made a mistake but I'll tell you until The xperia companion does not fix me or put again and again a new firmware with falshtool. Micellular only remains on the operator's logo.
@rrvuhpg
Bro this is new update i am uploading FTF+FSC for you Android 7.0 for F3111 single sim
Please rooting boot.img and recovery.img
thanx you very much
here is upload: https://mega.nz/#F!jlZTlLzR!V57m-F4nGmnO3Yky-kmkWw
rrvuhpg said:
Hi,
Releases for Nougat:
2017/07/18: From 33.3.A.0.131 kernel sources and Ramdisk from 33.3.A.0.131 FR firmware.
https://mega.nz/#!MlZkADRC!rvLdH400qLF3YG04beulKsGMpiDNooDRT7j5XgxNPCc
Click to expand...
Click to collapse
I flashed ftf ...3.a.0.131, (CE5, uploaded here - https://drive.google.com/open?id=0B5E7sFT1phjobGpLR0lwZDJHQ1k), and rebooted, then used fastboot to flash boot img posted above, and recovery here - https://forum.xda-developers.com/xperia-xa/development/f3111-f3113-f3115-twrp-recovery-xa-t3639206 . I get no recovery, and phone won't boot. I'll try again, but just reporting, in case I'm missing something. Thanks
@rrvuhpg - tested again. Restored stock kernel with FT, and phone booted fine. Downloaded boot again, just to be sure, and flashed with fastbot. Flash OK, but phone won't boot. Just infinite boot animation. Any idea? Do you think it would be different because of CE customization? Thanks
levone1 said:
I flashed ftf ...3.a.0.131, (CE5, uploaded here - https://drive.google.com/open?id=0B5E7sFT1phjobGpLR0lwZDJHQ1k), and rebooted, then used fastboot to flash boot img posted above, and recovery here - https://forum.xda-developers.com/xperia-xa/development/f3111-f3113-f3115-twrp-recovery-xa-t3639206 . I get no recovery, and phone won't boot. I'll try again, but just reporting, in case I'm missing something. Thanks
@rrvuhpg - tested again. Restored stock kernel with FT, and phone booted fine. Downloaded boot again, just to be sure, and flashed with fastbot. Flash OK, but phone won't boot. Just infinite boot animation. Any idea? Do you think it would be different because of CE customization? Thanks
Click to expand...
Click to collapse
I think that you not followed the guide.
1. Don't upload firmwares please, read again step 3.
2. If you can't acces to recovery it's because you missed step 6
3. If you have a bootloop it's because you missed step 13
rrvuhpg said:
I think that you not followed the guide.
1. Don't upload firmwares please, read again step 3.
2. If you can't acces to recovery it's because you missed step 6
3. If you have a bootloop it's because you missed step 13
Click to expand...
Click to collapse
I'll check again, thanks...
---------- Post added at 05:45 AM ---------- Previous post was at 05:42 AM ----------
rrvuhpg said:
I think that you not followed the guide.
1. Don't upload firmwares please, read again step 3.
2. If you can't acces to recovery it's because you missed step 6
3. If you have a bootloop it's because you missed step 13
Click to expand...
Click to collapse
OK, I see that you are right. Sorry, I was hasty. I've been flashing for 3 years on Z phones and I thought I knew. thanks for your time.
rrvuhpg said:
I think that you not followed the guide.
1. Don't upload firmwares please, read again step 3.
2. If you can't acces to recovery it's because you missed step 6
3. If you have a bootloop it's because you missed step 13
Click to expand...
Click to collapse
Just want to report back success by following directions eek... Thanks again, and sorry for my doofusness...
PLS HELP
Kawaxi said:
I tried to follow the guide.. I think the problem is the step 8
8. Flash recovery and boot with "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" commands (rename downloaded boot/recovery image if needed). The simplest way is to use fastboot from Flashtool in x10flasher folder, copy recovery and boot in it, open command prompt, flash them and then delete them.
I did an now my cellphone is in a endless loop , I think the problem is the boot.img my model is 3213
pls help me.
Click to expand...
Click to collapse
I am stuck at bootloop...whihc is the correct boot.img? I dont find it anywhere, I have a sony experia xa ultra fs3213
Hi @rrvuhpg,
Can you tell me if for the kernel for the 4.70MM image you have done other changes in the code besides the one found in your github? I've asked about the same question in a private message. I want to upgrade to 4.70MM (currently on 3.81) and I want to be sure I want to be sure I can compile a bootable kernel. Thanks a lot!
Sent from the center of the galaxy
cojocar.andrei said:
Hi @rrvuhpg,
Can you tell me if for the kernel for the 4.70MM image you have done other changes in the code besides the one found in your github? I've asked about the same question in a private message. I want to upgrade to 4.70MM (currently on 3.81) and I want to be sure I want to be sure I can compile a bootable kernel. Thanks a lot!
Sent from the center of the galaxy
Click to expand...
Click to collapse
I answered to your PM this morning, check your inbox
can you upload that file again plz :c
plz can you relase
marchimillow :
33.2.A.3.105
NOUGAT
33.3.A.1.97_1302-4382_R3B
Related
Hi,
I will release here my updated "boot.img" files for the Xperia XA Dual Sim.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file, on 33.2.B.4.70 and upper "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
The Fastboot command is:
fastboot flash boot NAMEOFIMAGE.img
Click to expand...
Click to collapse
Releases for Marshmallow:
2016/12/26: From 33.2.B.3.123 kernel sources and Ramdisk from 33.2.B.3.105 FR firmware. (Works up to 33.2.A.3.123)
https://mega.nz/#!swQwHLZR!ar3qmGKlvTTESpmsra4haUYmQB_gnpjn7arMKy3WBIo
2017/03/14: From 33.2.B.4.70 kernel sources and Ramdisk from 33.2.B.4.70 MAA firmware.
https://mega.nz/#!YhREgQCL!yV8EEyhFw5Q5QUE5FGePtXW_08EecqhJHA_ppqsRka0
Releases for Nougat:
2017/07/18: From 33.3.A.0.131 kernel sources and Ramdisk from 33.3.A.0.131 FR firmware.
https://mega.nz/#!4poC2JpI!MnJEz36P0f-8g3CaXrNIi7fbR_tWfpN5uqYgwUuXQ6E
rrvuhpg said:
Hi,
I will release here my updated "boot.img" files for the Xperia XA Dual Sim.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file.
Releases:
12/26/2016: From 33.2.B.3.123 kernel sources and Ramdisk from 33.2.B.3.105 FR firmware.
https://mega.nz/#!swQwHLZR!ar3qmGKlvTTESpmsra4haUYmQB_gnpjn7arMKy3WBIo
Click to expand...
Click to collapse
Can you please help me convert the boot.sin and system.sin into an .img file? thanks
donedos said:
Can you please help me convert the boot.sin and system.sin into an .img file? thanks
Click to expand...
Click to collapse
Hi, you can use "Assayed Kitchen" (some steps are explained in it) and Flashtool for that you need, you will need "Carliv Image Kitchen" too. I will not make a step by step guide but you can ask me if you need in private message.
rrvuhpg said:
Hi, you can use "Assayed Kitchen" (some steps are explained in it) and Flashtool for that you need, you will need "Carliv Image Kitchen" too. I will not make a step by step guide but you can ask me if you need in private message.
Click to expand...
Click to collapse
Thanks for the reply. I'll check it out. ? ? ?
Has updated 7
rrvuhpg said:
Hi,
I will release here my updated "boot.img" files for the Xperia XA Dual Sim.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file, on 33.2.B.4.70 and upper "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
Releases:
2016/12/26: From 33.2.B.3.123 kernel sources and Ramdisk from 33.2.B.3.105 FR firmware. (Works up to 33.2.A.3.123)
https://mega.nz/#!swQwHLZR!ar3qmGKlvTTESpmsra4haUYmQB_gnpjn7arMKy3WBIo
2017/03/14: From 33.2.B.4.70 kernel sources and Ramdisk from 33.2.B.4.70 MAA firmware.
https://mega.nz/#!YhREgQCL!yV8EEyhFw5Q5QUE5FGePtXW_08EecqhJHA_ppqsRka0
Click to expand...
Click to collapse
Bro, i love you!
But, mod boot for android 7, please!
stuck in bootloop after flashing boot.img 2017/03/14 file 33.2.b.4.70 file for f3116 from the given link but still my phone doesnt boot up , please help
Is there a boot 33.3.A.1.97 for F3112? Thank you very much in advance.
jackdaniels2017 said:
Is there a boot 33.3.A.1.97 for F3112? Thank you very much in advance.
Click to expand...
Click to collapse
You tried with 33.3.A.0.131 boot before asking for a new one?
rrvuhpg said:
You tried with 33.3.A.0.131 boot before asking for a new one?
Click to expand...
Click to collapse
131st did not try. I'm afraid to get a brick.
How we relock bootloader loader in sony xperia xa ultra f3216
How we relock bootloader loader in sony xperia xa ultra f3216
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.
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 )
VERY IMPORTANT:
Please make sure your boot.img version matches the ROM version . that's mean if you update your device then you have to use patch boot.img from new recovery rom.never use the old one. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.(link in this post)
Then run this command
fastboot flash vbmeta vbmeta.img
fastboot flash boot patch-boot.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Shas45558 said:
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.
https://forum.hovatek.com/thread-32719.html
Go to method 3....log in to download vbmeta.img file.
Then run this command
fastboot flash boot patch-boot.img
fastboot flash vbmeta vbmeta.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Click to expand...
Click to collapse
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
nielsync said:
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
Click to expand...
Click to collapse
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Shas45558 said:
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Click to expand...
Click to collapse
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
nielsync said:
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
Click to expand...
Click to collapse
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Shas45558 said:
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Click to expand...
Click to collapse
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
nielsync said:
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
Click to expand...
Click to collapse
I use this version of magisk manager and it always work
Shas45558 said:
I use this version of magisk manager and it always work
Click to expand...
Click to collapse
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Thanks for the post. It helped me to root my redmi note 9.
nielsync said:
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Click to expand...
Click to collapse
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Shas45558 said:
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Click to expand...
Click to collapse
My issues was patching using the canary version of Magisk Manager which isn't stable enough and was probably not patching the boot image properly as opposed to Magisk Manager 7.5.1 which is the stable version. Nice explanation on the vbmeta.img file.
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
I guess this still doesn't unlock the bootloader, and what about system updates?
Kiwironic said:
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
Click to expand...
Click to collapse
Ok i do ir on top and bottom of the post and thanks for your advice:good::good:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
rizelgeorgel said:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
Click to expand...
Click to collapse
Download pbrp from official website.then extract it and you will get a .img file.flash it via fastboot mood and the cmd is
fastboot flash recovery pbrp.img
*Change pbrb.img according to your file name.
One big question..did you unlock your bootloader and root your device?
Thank you very much! I succeeded according to your advice!
shas hows pbrp?
regarding flashing?
mhark.moby said:
shas hows pbrp?
regarding flashing?
Click to expand...
Click to collapse
Pbrp is in beta testing....so it has some bug and there's no use to install..
Buenas tardes tengo problemas al cargar el parche de magisk en redmi 9. Cuando cargo el boot.img parchado de magisk el tlfn queda en bootloop estoy en la version 11.0.8 global.
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