Related
Hi friends
Any have CWM or TWRP for Alcatel pop4?
Recovery Alcatel pop 4
I am also waiting for this topic . Please help.
Twrp for Alcatel Pop 4
I managed to port twrp 3.0.2 from the Huawei y560 to the Alcatel Pop 4 by watching a youtube video (Sorry I cannot link it I only just joined XDA but google is your friend), using kingroot to gain temp root access, using dd if=/dev/block/bootdevice/by-name/recovery of=/storage/xxxx-xxxx/recovery.img to dump my recovery to my sd card, then when I finished porting after watching the video and following the instructions, I flashed the ported twrp image it using Kernel Auditor from Google Play from my internal emulated/0 directory while having temp root access and it worked for me.
If you manage to find the video on how to port twrp and attempt it just be wary of bugs and always make a backup.
Edit: https://drive.google.com/open?id=0B6EQd1aL0EmWX3I2WEFuVmdUcUk - the link for the recovery if anyone wants to flash it or improve it.
Hi..
Nice working guy..i flash using nandroid manager..
tq so much
Great, thank you. I can install Recovery with Flashify. I have my Alcatel pop 4 with root, xposed and recovery. Thanks, thanks, thanks.
luispelau said:
Great, thank you. I can install Recovery with Flashify. I have my Alcatel pop 4 with root, xposed and recovery. Thanks, thanks, thanks.
Click to expand...
Click to collapse
Hi friend...
I need xposed any link to download?
Me funcionó v86 sdk21 . He instalado antes de tener el recovery de una forma difícil a través de ADB con un programa para instalar otra cosa. Trata de ver si se instala a través del recovery.
http://dl-xda.xposed.info/framework/sdk21/arm/
Si no instala a través del recovery luego le explico como lo hice yo.
Quisiera pedirle un favor . He tenido un problema con la recuperación y ha corrompido mi sistema. Usted me puede enviar una carpeta con el recoger del system y sólo del a través de algún enlace para que pueda recuperarlo. Gracias.
To me it worked sdk21 v86 . I installed before having a difficult recovery way through adb with a program to install something else. Try to see if you install it through recovery .
http://dl-xda.xposed.info/framework/sdk21/arm/
If you do not install through recovery cone then I explain I did.
I would ask a favor. I had a problem with the recovery and has corrupted my system . You can send me a your -Recovery system and only your system via some link so it can recover. Thank you.
basodiodoh said:
Hi friend...
I need xposed any link to download?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 - this is what worked for me since I am now using Magisk for Systemless root and am using their Systemless Xposed from the link provided.
Can this work on Pop 4+?
Kingroot could not root Pop 4+
anyone have custom rom or cm for alcatel pop 4
???
Please Help Me
luispelau said:
Great, thank you. I can install Recovery with Flashify. I have my Alcatel pop 4 with root, xposed and recovery. Thanks, thanks, thanks.
Click to expand...
Click to collapse
Brither help me please ... make a backup of you rom through twrp and upload it in some cloud drive like mega or mediafare .. and give e the link ... i beg you .. i firgot to take a backup .. please bro . :crying:
I beg you
basodiodoh said:
Hi..
Nice working guy..i flash using nandroid manager..
tq so much
Click to expand...
Click to collapse
bro please make a backup of your rom by twrp recovery and upload it in any cloud storage like mega , dropbox , mediafire etc .. and give the link to me ..... i forgot to take backup now i am unable to open my phone.
Need TWRP image for alcatel pop 4 plus
Can anybody compile and share good twrp image for alcatel pop 4 plus phone?
I have phone with unlocked bootloader.
Hi
sorry to ask but how would i install it, i tryied adb on windows but i can't get it to work its just saying (Waiting for Device)
I have installed all the drivers and i have tryied booting into fastboot but it just reboots my phone.
I have the alcatel pop 4 5051x
Kinda new to android.
thanks
Edit: I now managed to flash TWRP and SuperSu with xposed. and it is running fine. Thanks
luispelau said:
Great, thank you. I can install Recovery with Flashify. I have my Alcatel pop 4 with root, xposed and recovery. Thanks, thanks, thanks.
Click to expand...
Click to collapse
How did you rooted your POP4? I tried with Kingroot, but all the time the mobile restart, and when he back, isn't rooted anymore.
hit321 said:
How did you rooted your POP4? I tried with Kingroot, but all the time the mobile restart, and when he back, isn't rooted anymore.
Click to expand...
Click to collapse
I'm going through the same problem
nikito67 said:
I'm going through the same problem
Click to expand...
Click to collapse
I could not get my pop +4 rooted with kingo root or any of the other one click roots out there could anyone help me
Hi everyone, Kingroot has worked well for me every time I've needed it. But I absolutely do not like having it installed. No confidence inspires me. To start during the root process is already done system app without getting root or so says, whatever you do behind only Kingroot knows. And always, always, is always restarting the phone. But it is the only "One click root" that works for me.
I recommend;
- have prepared "Flashify" or similar, and the zip that comment at the beginning of the post.
- Insist on Kingroot until you get root, and wait a few minutes.
- Open Flashify grant permissions and install the recovery image.
- When finished, from the same app reboot in recovery and verify that it installed TWRP 3.0.2.0.
- Restart system, return to Kingroot and again get root.
- Once achieved, without leaving the app go to options and uninstall Kingroot.
- And now if, finally restart in recovery and install SuperSU.zip.
Then download it if you wish;
- xposed-v87-sdk23-arm
- XposedInstaller_3.1.1
- xposed-uninstaller-20160829-arm
View attachment 4211745
Greetings and luck.
To permanently root the Alcatel Pop 4 with either SuperSU or Magisk you will need to get access to temporary root with KingRoot so you can flash TWRP and install one of the root managers I just mentioned. I recommend flashing with Flashify. That's what I used. I haven't tested it with Magisk so i'd use SuperSU if I were you.
Download TWRP and SuperSU or Magisk on your phone first then flash TWRP with Flashify then reset your device with TWRP and install one of those root managers and your all finish rooting. KingRoot is very unstable with the Pop 4 so if it reboots and you lose temp root before you get a chance to flash, just reroot the device with KingRoot then flash.
This is a response to JordieSnipezHD's post.
Links
KingRoot
https://kingroot.net/
TWRP 3.0.2-0 for AP4 5051X
https://uploadfiles.io/x9h18
SuperSU
http://www.supersu.com/download
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hello will this (twrp) work on 5051T pop 4
---------- Post added at 02:37 PM ---------- Previous post was at 02:34 PM ----------
ht2000 said:
To permanently root the Alcatel Pop 4 with either SuperSU or Magisk you will need to get access to temporary root with KingRoot so you can flash TWRP and install one of the root managers I just mentioned. I recommend flashing with Flashify. That's what I used. I haven't tested it with Magisk so i'd use SuperSU if I were you.
Download TWRP and SuperSU or Magisk on your phone first then flash TWRP with Flashify then reset your device with TWRP and install one of those root managers and your all finish rooting. KingRoot is very unstable with the Pop 4 so if it reboots and you lose temp root before you get a chance to flash, just reroot the device with KingRoot then flash.
This is a response to JordieSnipezHD's post.
Links
KingRoot
https://kingroot.net/
TWRP 3.0.2-0 for AP4 5051X
https://uploadfiles.io/x9h18
SuperSU
http://www.supersu.com/download
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Will the twrp recovery work with pop 4 5051T???
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
Hello fellas
Finally i catch OREO from Z2 Play and posting for all , it was a hard work of 3 days to scripting and get a valid serial number
I am not responsible for any brick in the device and only do the procedures if you are sure of what you are doing .
This will not avoid your warranty (if you have locked bootloader) and you will still be available to get automatic OTA from your device.
Warning:
* You need to have february patch from Nougat and buildnumber (NPSS26.118-19-1-6) to install OTA.
* If you have a different buildnumber or your device is branded to any carrier, you need to install a fresh nougat compatible with this OTA.
* Dont try ota update with custom rom, root, magisk or whatever. Install fresh nougat first.
* I recommend to make a backup of all yours data (they might be lost in process)
* Make a backup of your EFS partition.
* You cant downgrade to NOUGAT again, your IMEI and SIMCARD will be not available due partition and bootloader compatibility.
* If you brick your device, erase all your userdata, cache, system from device and install a fresh nougat to update OTA again, cause if not you can get stuck in bootloop.
* Be sure adb/fastboot will recognize your device using (fastboot devices or adb devices)
Download:
Stock NOUGAT NPS26.118.19-1-6
Motorola Drivers
Standalone ADB/FASTBOOT (thanks XDA/ GOOGLE)
Download OTA
Steps for installing OTA:
1. Connect your device in USB and install Motorola Drivers (I recommend dont try to install drivers first)
2. Download adb/fastboot and extract it (i suggest c:\adb for beginners)
3. Download OTA (dont extract) and place it in adb folder
4. Make a factory reset (recommended)
5 Be sure you have atleast 50% of your battery
6. Shutdown your phone, enter in recovery mode then hold power and press volume down for 1 second and release both.
7. Choose apply update from adb
8. In command prompt goto adb folder, then execute command: adb sideload Blur_Version.27.21.26.albus.retail.en.US.zip
It may take a while for install, so please be patient.
If i forget anything please tell me to i fix the post.
If you have got an OTA from another country (india, europe and others...) and you dont know how to catch it, please be free to contact me , so we can release it together and help others !
Thanks Junior Passos
Good job @raphamfc. Thanks.
Unable to download "Stock NOUGAT NPS26.118.19-1-6", and I've had a few others try as well; no luck. It gets to about 0.2/1.9GB and fails.
Worked for me
Moto z2 Play
hello it turns out that it tries to degrade nougat and it turns out that now I have been stuck for security downgrade so can I fix this to reinstall oreo?
there is not a method to flash it?
My update but i'm not really sure why. I have the NPSS26.118-19-1-6 build, installed as Junior Passos suggested, everything works fine. But it displays an error when trying to sideload de OTA. Could it be because my bootloader is unlocked?
Thank you guys, you are far way better support than Motorola itself.
Mod edit: OP quote removed
---------- Post added at 01:53 AM ---------- Previous post was at 01:47 AM ----------
The error i'm getting says: E2004: oem partition fails to recover... oem has been remounted R/W and has changed the partition contents... Partition contents should not be changed for successful updates; reflash devide to enable OTA updatesE:Error in /sideload/package.zip (Status 7).
I'm going to try reflashing 7.1.1 and then sideloading the OTA to 8.0
Sanefc said:
My update but i'm not really sure why. I have the NPSS26.118-19-1-6 build, installed as Junior Passos suggested, everything works fine. But it displays an error when trying to sideload de OTA. Could it be because my bootloader is unlocked?
Thank you guys, you are far way better support than Motorola itself.
Click to expand...
Click to collapse
IT WORKED! Thanks!!!!!
Sanefc said:
My update but i'm not really sure why. I have the NPSS26.118-19-1-6 build, installed as Junior Passos suggested, everything works fine. But it displays an error when trying to sideload de OTA. Could it be because my bootloader is unlocked?
Thank you guys, you are far way better support than Motorola itself.
---------- Post added at 01:53 AM ---------- Previous post was at 01:47 AM ----------
The error i'm getting says: E2004: oem partition fails to recover... oem has been remounted R/W and has changed the partition contents... Partition contents should not be changed for successful updates; reflash devide to enable OTA updatesE:Error in /sideload/package.zip (Status 7).
I'm going to try reflashing 7.1.1 and then sideloading the OTA to 8.0
Click to expand...
Click to collapse
Hello, I am currently in version NPSS26.118-19-22. must I downgrade in NPSS26.118-19-1-6 version to flash the OTA?
the OTA file says enUS: does it work in europe?
Sorry for my English, I'm French.
----------
Bonjour, je suis actuellement en version NPSS26.118-19-22. Est ce que je suis obligé de redescendre en version NPSS26.118-19-1-6 pour flasher la OTA?
le fichier OTA indique en.US : est ce qu'il fonctionne en europe?
désolé pour mon anglais je suis Français.
miniyouki said:
Hello, I am currently in version NPSS26.118-19-22. must I downgrade in NPSS26.118-19-1-6 version to flash the OTA?
the OTA file says enUS: does it work in europe?
Sorry for my English, I'm French.
----------
Bonjour, je suis actuellement en version NPSS26.118-19-22. Est ce que je suis obligé de redescendre en version NPSS26.118-19-1-6 pour flasher la OTA?
le fichier OTA indique en.US : est ce qu'il fonctionne en europe?
désolé pour mon anglais je suis Français.
Click to expand...
Click to collapse
If you check your ro.build.version.full (via adb shell, and command: getprop ro.build.version.full) you'll see that your phone is also .en.US. In my case I'm on retapac (pacific software channel) and I have the version Blur_Version.27.21.26.albus.retail.en.US.
Try to check that, and if you see en.US, don't worry aobut the version.
I also downgraded to NPSS26.118-19-1-6 to install Oreo OTA.
thank's a lot for your answer : it's write :
Blur_Version.26.286.28.albus.retail.en.US
So must I downgrade?
It works with the Mexican variant XT1710-06, first you have to install the nougat ROM with the February patch following the steps in the the Junior pasos trheat. Also, I don't know if there's an error in your instructions but in order to do the sideload, in the recovery you have to use the Vol+ button to access the menu. That's what I did in my phone.
Do you have all stock? Locked bootloader?
SinkyChan17 said:
Unable to download "Stock NOUGAT NPS26.118.19-1-6", and I've had a few others try as well; no luck. It gets to about 0.2/1.9GB and fails.
Click to expand...
Click to collapse
I'll try to post a Google drive Link for you
NikioXD said:
hello it turns out that it tries to degrade nougat and it turns out that now I have been stuck for security downgrade so can I fix this to reinstall oreo?
there is not a method to flash it?
Click to expand...
Click to collapse
If you downgrade your new version from nougat , you don't need to mess with bootloader or partition. Just flash the others (logo, modem, system, oem and so on )
you will be available to upgrade to Oreo since your build is correctly
Sanefc said:
My update but i'm not really sure why. I have the NPSS26.118-19-1-6 build, installed as Junior Passos suggested, everything works fine. But it displays an error when trying to sideload de OTA. Could it be because my bootloader is unlocked?
Thank you guys, you are far way better support than Motorola itself.
---------- Post added at 01:53 AM ---------- Previous post was at 01:47 AM ----------
The error i'm getting says: E2004: oem partition fails to recover... oem has been remounted R/W and has changed the partition contents... Partition contents should not be changed for successful updates; reflash devide to enable OTA updatesE:Error in /sideload/package.zip (Status 7).
I'm going to try reflashing 7.1.1 and then sideloading the OTA to 8.0
Click to expand...
Click to collapse
doesn't have any problem you have locked or not. Just use a compatible nougat, enable debugging mode and don't forgot to remove password + fingerprint from cellphone, cuz he will show device is encrypted.
miniyouki said:
thank's a lot for your answer : it's write :
Blur_Version.26.286.28.albus.retail.en.US
So must I downgrade?
Click to expand...
Click to collapse
No, your version is a old one, you will upgrade to 26.291-7
ok where can i find this version ?
raphamfc said:
I'll try to post a Google drive Link for you
Click to expand...
Click to collapse
Sorry I never responded! It worked perfectly after I waited a few days and now I'm not only on Oreo, but my IMEI is back *AND* My NFC works! Perfect! Thanks so much for your hard work
Is Magisk working for anyone? With installed Magisk v16.4 my device isn't booting anymore since Oreo, it just stays on the "Your device has been unlocked and can't be trusted." screen after a short vibrate.
Boots again after I sideloaded the uninstaller.
https://androidfilehost.com/?fid=890278863836283331
Anyone got the OTA in Europe?
Unfortunately Installed Wrong Codename ROM On My poco f1
after that my device goes in to fastboot mode
and i cannot access recovery mode because fastboot everywhere
if i press volume up + power button = fastboot mode
if i reboot = fastboot mode
if i plug in to charger = fastboot mode
then i flashed mi global stable build from miflash
still device booting in to fastboot mode automatically
after that when i flashed miui 9 device booted up successfully then i updated to miui 10 oreo from system update
but when i try to update miui 10 oreo to pie from ota/twrp/fastboot device automatically booting in to fastboot mode
after that i tried android q dp4 gsi guess what device booted android q gsi successfully
Tested All pie custom roms also same issue
it means i cant install pie
dont know what is happening exactly
DOWNLOAD
"beryllium-9.6.27-9.0-vendor-firmware" AND PUT IT on sdcard/usbotg and FLASH it via TWRP from
https://mirror.akhilnarang.me/MIUI/beryllium/
then flash any pie rome + GAPPS (if needed) +magisk19.3(if you wana root) and reboot
the device will boot
Xiaomi Poco uses Modified Vendor image ! that why it needed to be flashed saperatedly!
check and let me know!
edit1
if you cannot access recovery! BOOT into recovery via fastboot command line (while Poco is connected in Fastboot mode to your PC) and your PC have all driver installed. Open Minimal adb and fastboot
fastboot device // to check connection
fastboot boot ..... and Drag twrp from desktop and DROP it on CMD window ... then ENTER,
your POCO will BOOT, while its on Yellow LOGO, try to put USB OTG drive so that Twrp can READ its contents for you to Flash! , usb otg plugged AFTER twrp boot usually don't get red! ... OR better put flashable zips in sd card using any adaptor
I suffer from the same problem and applied all your steps but go to put fastboot .
please solve this
hekoo1 said:
I suffer from the same problem and applied all your steps but go to put fastboot .
please solve this
Click to expand...
Click to collapse
please xplain more
1. did you flash vendor (latest) ?
2. what rom you are flashing?
3. miui works?
plz explain
yasuhamed said:
please xplain more
1. Did you flash vendor (latest) ?
2. What rom you are flashing?
3. Miui works?
Plz explain
Click to expand...
Click to collapse
1. I flashed vendor 9.6.27-9.0 via recovery
2. I want flash miui 10.3.5 latest
3. Miui android 8.1 working . Android 9 not working
hekoo1 said:
1. I flashed vendor 9.6.27-9.0 via recovery
2. I want flash miui 10.3.5 latest
3. Miui android 8.1 working . Android 9 not working
Click to expand...
Click to collapse
THERE IS NO NEED TO FLASH VENDOR if you going to flash ANY MIUI!
make sure you have correct build/version of MIUI 10.3.5,
some times, if DATA partitions is CORRUPT then click on FORMAT data, type YES and it will wipe the WHOLE device! encryptions will be reset! then place MIUI10.3.5 and check!
remember, to take backups!
if miui 9 has worked then this means the downloaded miui10 is not the correct one!
No I can not.
When installing any system MIUI ANDROID 9 PIE the phone is rebooted to FASTBOOT
---------- Post added at 09:05 AM ---------- Previous post was at 08:55 AM ----------
YasuHamed said:
THERE IS NO NEED TO FLASH VENDOR if you going to flash ANY MIUI!
make sure you have correct build/version of MIUI 10.3.5,
some times, if DATA partitions is CORRUPT then click on FORMAT data, type YES and it will wipe the WHOLE device! encryptions will be reset! then place MIUI10.3.5 and check!
remember, to take backups!
if miui 9 has worked then this means the downloaded miui10 is not the correct one!
Click to expand...
Click to collapse
No I can not.
When installing any system MIUI ANDROID 9 PIE the phone is rebooted to FASTBOOT
PLEASE SOLVE THIS
hekoo1 said:
No I can not.
When installing any system MIUI ANDROID 9 PIE the phone is rebooted to FASTBOOT
---------- Post added at 09:05 AM ---------- Previous post was at 08:55 AM ----------
No I can not.
When installing any system MIUI ANDROID 9 PIE the phone is rebooted to FASTBOOT
PLEASE SOLVE THIS
Click to expand...
Click to collapse
I know this is a longshot but, bro, did you manage to solve the issue? I'm in the same situation and trying to find a solution. Opened a new thread but no help from anywhere... Anyone? Guys?
[QUOTE = "crimsonFay, postagem: 83995307, membro: 10638959"]
Eu sei que é uma hipótese remota, mas, mano, você conseguiu resolver o problema? Estou na mesma situação e tentando encontrar uma solução. Abriu um novo tópico, mas sem ajuda de lugar nenhum ... Alguém? Rapazes?
[/CITAR]
eu tmb estou a meses nessa situação, acho que só flash edl auth l resolver
For People Stuck On Oreo Firmware (Poco F1)
I have seen many people facing this issue where they flashed a OxygenOS rom of different phone ( Due to a idiot youtuber said it can be flashed on all devices ) I recently recieved a POCO F1, with same condition where i cannot update MIUI over...
forum.xda-developers.com
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