Related
Hi,
I'm having a problem installing TWRP on my doogee X5, in order to root the device. I have tried to flash the recovery with sp flash tool, and every time I try, I can boot to the boot mode menu, select "recovery" and see the doogee logo for a while, then a black screen, then the doogee logo again, following into a normal boot.
This is the X5, not the X5 pro.
firmware on phone: "DOOGEE-X5-B-Android5.1-2016.03.18"
Any help?
PS: I don't want to use kingroot to root the phone, as I also want xposed.
I'm looking for a solution to that very problem too. Let's see if someone comes to help!
Exactly the same goes here too. Probably there's not an updated TWRP for V18 which I am using. I have not the slightest idea who could help us.
Rooting Doogee X5 / TWRP install
Here's what worked for me, thought I'd share this.
Out of the box was on version 18 and wanted to root , so i blindly installed King Root which did work, i then installed Supeer SU me which changed the king root to super user. After that over a week i read that TWRP 3.0.2 worked for one person so using Flashify i flashed the recovery image , after changing it to recovery.img and it worked . Such luck right, i went on to read the forums as im in love with this device , Wakefield helpful was NEEDROM.com , you need to register but there are many roms and tools for mediatek 6580soc . Out of curiosity i downloaded some rar. File roms ACS different fish tools. The best to use if you've only got oneX5 is SP flash tool. Also look for mediatek vcom drivers which auto installs the correct drivers. There are easy to follow you tube videos fur flashing using SP Flash tool. The latest version had been updated for simplicity. the process basically is ( load .bin file in its respective area,( from Flash tool) and load scatter.txt in its box ( from rar. File) the whole interface will polemist populate plug go to format hit start plug in turned off phone without battery, it'll give red then yellow bar and a check, then unplug hi to firmware screen and choose to start dload only except bootloader, start , plug wait for coloured bars and check your done. i even had gotten errors due to a faulty dload and repeated the process till i got it. I understand that not all have the patience for this, therefore i suggest using flash tool of king root messes up though that's rare.
An alternative to supersu me is to root with king root then install twrp with flashify then you can uninstall / repack king root and flash Updateroot.Script available by someone on needrom. That includes super user and busy box. Then installxposed. Etc.
* Each process in the above proven tuturial has been obtained online from other sites not just xda. I've chosen 5.1 as an idealOS for me, I can't say the route to take fur Marshmallow.
This is for -b and non b only version 18, and 19. All others take your own chances but it's resilient chip so have fun.
(SOLVED just flash DOOGEE-X5-HOT2-6.0.zip and the twrp from the rom is installed and works after rebooting in recovery mode.) after flashing CWM recovery
Listed: 10/28/2016 11:16 pm
ROM Version: 6.0 / 5.1 to my doogeex5 (flashing succeed) i got an green android logo with an error sighn(see picture)and some chinese letters...
in normal boot no problem,also upgrading to android 6 (flashed) gave no problem...
how to get new recovery(flashing other recovery`s gave same output exept the chinese sighns disapeard)
kingroot V4.80 couldnt root my doogeex5 after 27%rooting it says cant root device
also doesnt the system update in `my device` recognice the memory card ...no sd card inserted...
any suggestions?
I have a similar problem. Unlocking the boot loader works fine, but i can't seem to find a working twrp file for my phone.
I have an X5 pro (x5pro-android5.1-r17-2015.07.01). I tried different twrp recoverys from needrom and i can flash them to the device, but if i try to boot into recovery i only get the robot with the red warning triangle. Rest of the phone works fine, but i'd like to get a working custom recovery.
Can anyone help me?
So i rooted my phone with kingroot and i wanted to install a custom recovery without breaking the device how should i move next ? My X5 is an old motherboard version android 5.1 V15-2015.11.02 and that was the last official fota update for me. Is there any ofgicial upgrade suitable for my model like android 6.0 ? Two more things. My battery goes down rapidly and i dont know if its battery or chargers problem what should i do ?
http://www.needrom.com/category/doogee/serial-x-doogee/x5-doogee/
even without rooted phone you can flash a lot of roms from above link and read how to
Yeah i noticed this site man but says you need to register first. And one more thing spft always detects scatter files as invalid or maybe not legal even from the official site of doogee. I use the spft from doogeemobile site.
I am using SP_Flash_Tool_exe_Linux_v5.1520.00.100 with ubuntu(linux) maybe try an other flashtool edition,registering needrom is simple just making username and make a password when you are registered take the inifix hot 2.6.0 for the x5 flash it and you have got also a TWRP from wich you can root or install also the .zip roms etc.
I mentioned the inifix hot2.6.0 because that was the one i had succes even with a bricked recovery caused by flashing a cwm recovery without rooting first.
Well i just want for sure make a backup of my current rom without wiping it. I guess the infinit will delete all. Plus i also want to install recovery having rooted it 1st which is easy i think on 5.1. I have the one with the old motherboard not the -b. To sum up i want to install the official updated rom V20 via sd (which i tried and didnt work) luckily it didnt brick or via spft which doesnt load scatter file says is not valid no matter if i use latest or older version of spft in order to flash it manually. Its risky to root and install a recovery by an apk without having my rom backed up 1st. And even with the spft i cant do that. I just want to fix my battery status. Thats all. I use xp pro os.
indeed it is hard to install android 5.1 roms on the doogee x5with a twrp,al the 5.1 roms i could flash,but then i bricked the recovery,wich made no differend for the installed 5.1 roms,they just work.i can only install a working twrp by flashing Infinix Hot 2 6.0,wich is a 6.0 rom,but as far as i know you cant install a 5.1 rom with a 6.0 twrp... error 7.
Thats why we will end this discussion for now and wait for future solutions. Thx for your concern man. I just dont want to brick it since it runs smoothly with 5.1. As i said before i wanted to install the latest (official stock) V20 rom recently released. But i cant do it even from the tutorial that exists on their forum. It's a use of spft but i cant manage to do it. Scatter file always invalid.V20 Rom fixes some bugs and displays your interface like on 6.0 android version. We talk mate.
Hello !
Any news on the matter ?
I have got an X5 with Android 6 (!) on it. Have tried to root it with several one-click tools but this does not work.
Any suggestions?
Hi! What room do you recommend The most stable, And best, Under flashtool To Doogee X5? Thanks in advance for help!
hello i need help on my doogee x5 all 6.0 custom rom flash give me error 11 on twrp how to fix please ,
Any help please?
I have error 7 on all rom
Help?
Having tried to install TWRP it is rejected
Having downloaded twrp_x5max.img from needrom and used the adp method of installing the TWRP.img (https://www.xda-developers.com/how-to-install-twrp/). I get the following error message. "writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed".
So How do I get the TWRP img loaded into the Doogee X5Max (not pro) android with marshmallow?
I have tried using SP FlashTool and it says installed successfully, but I still get the default recovery program, after the dead robot with triangle and a exclamation mark inside, when booting into recovery using keys or adb command.
Is there another way of getting this image file loaded into the recovery partition?
I have followed all the set up steps in developers mode, so why cannot I use adb?
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Honor 4x hanged (in some Indian kitkat version, not rooted) and after restart it is in bootloop. Honor logo appears then blue light starts to appear then restart.
Recovery mode and dload update not working.
After unlocking bootloader tried fastboot -w, still in bootloop.
Extracted Lollipop, Marshmallow, Kitkat - B161, B126 and flashed in fastboot. Possible to flash only recovery, boot, userdata & system. For others - failed : remote command not allowed. After flashing no change, still in bootloop.
Tried to boot to recovery from fastboot boot
- for lollipop and marshmallow recoveries it says "dtb not found"
- others including twrp, cm it is in bootloop.
Out of warranty.
Need help.
oppili said:
Honor 4x hanged (in some Indian kitkat version, not rooted) and after restart it is in bootloop. Honor logo appears then blue light starts to appear then restart.
Recovery mode and dload update not working.
After unlocking bootloader tried fastboot -w, still in bootloop.
Extracted Lollipop, Marshmallow, Kitkat - B161, B126 and flashed in fastboot. Possible to flash only recovery, boot, userdata & system. For others - failed : remote command not allowed. After flashing no change, still in bootloop.
Tried to boot to recovery from fastboot boot
- for lollipop and marshmallow recoveries it says "dtb not found"
- others including twrp, cm it is in bootloop.
Out of warranty.
Need help.
Click to expand...
Click to collapse
Oh ****, that seems like a frustrating situation. What made the device mess up so much? Have you gone to service centres?
Regards,
PoseidonKing
Not tried to flash or root. It just hanged while using.
Service centre said board gone (as always). MTK devices have a factory mode through which we can check working of all board parts. I did not find any way for this.
oppili said:
Not tried to flash or root. It just hanged while using.
Service centre said board gone (as always). MTK devices have a factory mode through which we can check working of all board parts. I did not find any way for this.
Click to expand...
Click to collapse
Sorry bro, can't help you out over here in this situation.... Best of Luck regarding your device. I would suggest pm'ing a forum moderator for your issue
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
HELP.!!Back to Stock Rom ????
I am struggling like anything to go back to stock rom. I am using Honor 4x Che1-L04 snapdragon. Pls send a link where can i find the instructions to do this. Or Better U expain.
EDIT:
Roll back to EMUI 4.0 success. Used the Hauwei update extractor and used CMD. Anyhow THANKS
NEW Problem:
How to enable ADOPTED STORAGE in honor 4x che1-L04 snapdragon edition.
In Xda they mentioned only about the kirin processor version.
Help!!!!!!!!!!
balongc52b311 after failing kangvip 6.7.1
hey there. will tell you my experience with failing to flashing kangvip 6.7.1 due to wiping problem
i wiped my cache, data, system even internal storage and yet failed to flashing kangvip 6.7.1 4 custom rom due to "cust" folder unable to mount giving me this:
error 1 can't mount /cust (Invalid argument)
so after failing to mount that folder and even deleting it by mistake,i got a new error:
error 1 can't mount cust no such file or directory
i lost hope and let my my honor 4x normally boot but it took too long and i was determined its stuck on bootloop :cyclops:
i woke up today finding it on 5% battery and giving me that first time setup as if all i did was a factory format BUT all in chinese. checked the build number and it was balongc52b311.
i tried mounting "cust" folder to r/w and rebooted into bootloader but it gave me the same first error. i tried deleting the folder and then rebooting into recovery and it gave me the 2nd error. created the folder "/cast" and then rebooted into recovery and it gave me the same first problem that the folder can't mount EVENTHO it was mounted successfully right before i rebooted into recovery (did this 3 times to make sure)
did some researching and found a solution for honor 4c http://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335 or two BUT both for lolllipop and i'm marshmallow.
i'm already halfway at the method i mentioned above but i stopped after i realized it was for lollipop. i rooted my mobile and changed my build number to "Che2-L11C636B330". worth to mention that my model number remained already the same "Che2-L11".
the cust folder error is still there whenever i go to the bootloader
now i have no idea what to do, what firmware to download and if i have to downgrade first to lollipop and then upgrade to marshmallow again...
my marshmallow version was the middle east final version before this balong happened: Che2-L11C185B561 and i would like to go back to it again.. thank you in advance ( :
###*UPDATED BELOW*
fixed my problem trying the method here http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039/page2
>>>>worth to mention that i flashed my oeminfo for my UPDATE.APK REGION before flashing the extracted files from UPDATE.APP "wasn't mentioned in that method"
now i'm back to my original marshmallow version "middle east". good luck people.
abdurrahmanzaki said:
hey there. will tell you my experience with failing to flashing kangvip 6.7.1 due to wiping problem
i wiped my cache, data, system even internal storage and yet failed to flashing kangvip 6.7.1 4 custom rom due to "cust" folder unable to mount giving me this:
error 1 can't mount /cust (Invalid argument)
so after failing to mount that folder and even deleting it by mistake,i got a new error:
error 1 can't mount cust no such file or directory
i lost hope and let my my honor 4x normally boot but it took too long and i was determined its stuck on bootloop :cyclops:
i woke up today finding it on 5% battery and giving me that first time setup as if all i did was a factory format BUT all in chinese. checked the build number and it was balongc52b311.
i tried mounting "cust" folder to r/w and rebooted into bootloader but it gave me the same first error. i tried deleting the folder and then rebooting into recovery and it gave me the 2nd error. created the folder "/cast" and then rebooted into recovery and it gave me the same first problem that the folder can't mount EVENTHO it was mounted successfully right before i rebooted into recovery (did this 3 times to make sure)
did some researching and found a solution for honor 4c http://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335 or two BUT both for lolllipop and i'm marshmallow.
i'm already halfway at the method i mentioned above but i stopped after i realized it was for lollipop. i rooted my mobile and changed my build number to "Che2-L11C636B330". worth to mention that my model number remained already the same "Che2-L11".
the cust folder error is still there whenever i go to the bootloader
now i have no idea what to do, what firmware to download and if i have to downgrade first to lollipop and then upgrade to marshmallow again...
my marshmallow version was the middle east final version before this balong happened: Che2-L11C185B561 and i would like to go back to it again.. thank you in advance ( :
###*UPDATED BELOW*
fixed my problem trying the method here http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039/page2
>>>>worth to mention that i flashed my oeminfo for my UPDATE.APK REGION before flashing the extracted files from UPDATE.APP "wasn't mentioned in that method"
now i'm back to my original marshmallow version "middle east". good luck people.
Click to expand...
Click to collapse
Thanks on the update about your success on restoring your phone. Surely some poor soul will get along the same problem and your post will help him out. Sorry for the late reply btw.
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
How to Root my honor 4x Che2-L11?
Hi everyone, I'm noob, so I need a step to step guide if there's such a thing
my android version is 6.0 and EMUI 4.0
I have bootloader code for unlocking the phone, thanks in advance guys, also happy new year :good:
Phone Honor 4x (che1-L04) Stuck in fastboot mode
My phone is stuck in fastboot mode. Couldn't get the bootloader unlock key online as it requires the product id which can be obtained by dialing a number which isn't possible. I have requested directly from the customer care number and the official chat portal as well but its been more than a week and still they are asking for 24 working hours. Is there any alternative method of getting the key or atleast the Product ID?
Model name :Che1-L04
Stuck in Fastboot & Rescue mode with the bootloader locked.
I got unlock key after 12 days. Honor 4x hanged after restart it is in bootloop.
3 button sd card update not working ?
oppili said:
I got unlock key after 12 days. Honor 4x hanged after restart it is in bootloop.
3 button sd card update not working ?
Click to expand...
Click to collapse
No the update.app isnt working I guess because I have already flashed the CM13 recovery image with the bootloader locked. However, I recieved the bootloader key yesterday from the email but when I tried unlocking by the fastboot command it said it is an invalid or wrong key. Is there any other way to take my phone back to stock condition atleast without actually unlocking the Bootloader?
Princeshubh said:
No the update.app isnt working I guess because I have already flashed the CM13 recovery image with the bootloader locked. However, I recieved the bootloader key yesterday from the email but when I tried unlocking by the fastboot command it said it is an invalid or wrong key. Is there any other way to take my phone back to stock condition atleast without actually unlocking the Bootloader?
Click to expand...
Click to collapse
1. Try "fastboot continue" it will directly boot without going to recovery.
2. If fastboot flash works flash recovery of the firmware installed in phone before bootloop.
3. If still not works flash boot, system, recovery (in this order) of firmware installed before bootloop.
Confirm unlock key with customer care if it is still locked.
I wanna know is there any other method to install xposed framework since the normal installation is not working for me.
Using Honor 4x Che1-l04 running on (stock ROM) Android marshmallow 6.0.1, have TWRP custom recovery and is rooted.
SumitGupta2442 said:
I wanna know is there any other method to install xposed framework since the normal installation is not working for me.
Using Honor 4x Che1-l04 running on (stock ROM) Android marshmallow 6.0.1, have TWRP custom recovery and is rooted.
Click to expand...
Click to collapse
no other way, unfortunatly.. one way or the other, you have to flash the zip...
ps: if you are on emui, first boot after flashing xposed will take a really long time.. mine took around 25 minutes to boot.. so dont consider it a boot loop, wait untill 30 minutes and you will be profitted
Mine was in boot screen for around 3 minutes and then rebooted into recovery. Same thing was happening again and again. So at last did the restore process from TWRP.
oppili said:
1. Try "fastboot continue" it will directly boot without going to recovery.
2. If fastboot flash works flash recovery of the firmware installed in phone before bootloop.
3. If still not works flash boot, system, recovery (in this order) of firmware installed before bootloop.
Confirm unlock key with customer care if it is still locked.
Click to expand...
Click to collapse
Its not working. Please help me I am still stuck....any way of installing the stock ROM back via fastboot mode with the phone showing 'Phone Locked'
Restoring TOO MUCH with twrp?
Can restoring too much with TWRP damage my phone?
jwalker9715 said:
Can restoring too much with TWRP damage my phone?
Click to expand...
Click to collapse
not really..
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
irontaco1 said:
... so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Click to expand...
Click to collapse
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
irontaco1 said:
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Click to expand...
Click to collapse
Read this for information on how to bypass the password that your backup is asking for https://www.google.com/amp/s/www.ho...fter-restoring-from-twrp-android-backups/amp/
Strephon Alkhalikoi said:
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
Click to expand...
Click to collapse
Hey thanks for the help phone is running just fine now. I grabbed the factory image from the Google dev page and flashed it the hard way. For some reason ADB wouldn't mount /system after it was finished so I used fastboot to flash system, boot, radio, etc. Guess I won't use Flashfire for baseband anymore :laugh:
ktmom said:
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
Click to expand...
Click to collapse
Phone is working fine now. The files were encrypted because the stock kernel I was using was obviously non-permissive so it automatically encrypted my files upon reboot before it bootlooped. Really appreciate the help though.
Hi, I think i've kinda bricked my honor 5C (nem-l51), and I really need help :
A few years ago I rooted my phone to make otg work.
It worked a little while, but then a system update came up, could not update because of the twrp, so I tried to unroot it (from supersu) to do the update, and the twrp stayed after the unroot.
I stayed with the phone like this, twrp installed and update pending (still trying to install the update from time to time) and then I had to use OTG again and tried to re-root my phone.
I tried to flash the supersu files I used the first time, but, even when the flashing worked, I couldn't see the supersu app on the phone, still unrooted.
Then I tried to change the twrp (via fastboot) and I realised that I couldn't : I get the "command not allowed" failure when the recovery should get written. I tried with numerous twrp versions, and stock recovery.
So my twrp right now is the twrp-3.1.1-0-venus "OpenKirin edition" one.
The phone says it's unlocked and the frp is locked, but I can't remember if it was already the case or not when I first rooted.
I unfortunately don't have anymore the bootloader unlock code that huawai gave me originally. I have no idea how to get it again, to try to re-lock/unlock the bootloader.
Back then when I first rooted my phone, I made a back up, so I tried to restore that back up. It failed, first with "cannot wipe the cust partition". Then I tried to restore without restoring the cust partition, and I got "extracttarfork() process ended with error 255" while the system was restoring.
After that, the phone wouldn't boot into android anymore. It would be stuck at the unlocked bootloader warning message and then reboot after a few minutes.
So, lastly, I tried to install the unofficial lineageOS port from here : https://forum.xda-developers.com/honor-5c/development/rom-lineageos-14-1-honor-5c-t3713911 with my twrp.
The installation went well, but the phone is stuck while first booting in lineageOS (I let it overnight, restarted it, re-installed it, tried with the first release, nothing).
TL;DR: My phone isn't booting and I can't flash any new recovery.
Please, help me to get my phone working again
Give me the
old build number on emui
Update build you received..
Twrp working?
Fastboot?
Erecovery?
I got access to erecovery, even if the "download latest version and recovery" doesn't work. (erecovery connects to wifi, and the first thing it tries to check/download fails)
I can boot into fastboot but can't flash recovery from there because of the command not allowed problem.
I can boot into twrp, but the back up I tried to restore and the lineageos rom I tried to install both failed, so maybe the twrp has a problem?
I'm sorry I'm not sure about the build number, I'm pretty sure I was on EMUI 5.0 and android 7.x, and I think I remember comparing current build number vs the update, and it was something like B350 or B351 for the current, and B355 or B375 for the update.
I've found this in my backup file 'recovery.log' ro.omni.version=6.0.1-20160703-nemo-HOMEMADE and ro.build.id=MOB30M . So, that mean that I had android 6.x when I did the backup, way back at the beginning.
I thought the update never got installed because each time the phone would reboot to complete installation, it would reboot into twrp. But I've still updated from android 6 to android 7 somehow ?
NEM-L51C432 or NEM-L51C10 ?
NEM-L51C432 and I'm sure of that ^^
Zhyrclew said:
NEM-L51C432 and I'm sure of that ^^
Click to expand...
Click to collapse
Flash this via twrp
http://update.hicloud.com:8180/TDS/...-L51_hw_eu/update_data_full_NEM-L51_hw_eu.zip
Once done, boot to twrp and flash this
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v82938/f1/full/update.zip
Reboot.
If you are unable to flash the 2nd link then just use the dload method to flash this. If you are not aware of dload method, link is given in my signature.
Note, this 2nd firmware will replace your twrp with stock recovery. You should boot to b350 version and it will be full stock. Reason for flashing data file first is it doesn't replace the recovery to stock but just flashes your data, settings, apps. And 2nd link is main full firmware which will replace your boot, recovery, vendor everything and should boot.
Good luck
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Zhyrclew said:
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Click to expand...
Click to collapse
You may try other higher versions like 360, 370 etc and see your luck. Twrp will be replaced only if the installation os successful for the main firmware. Its just a trial and error for you now but I am 99% sure you should be able to revive the phone via dload method
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Zhyrclew said:
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Click to expand...
Click to collapse
Firmware finder website
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Zhyrclew said:
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Click to expand...
Click to collapse
Check dload guide in my signature. You can follow that now. Good luck
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Zhyrclew said:
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Click to expand...
Click to collapse
Copy them on PC and then try dload of files you downloaded from Firmware finder website.
These are files your phone downloaded for OTA update but as you were on twrp, they never installed it amd stays there
I copied the updates my phone downloaded on PC and then deleted them both on internal storage and sd card.
Then I tried dload method with b355,b375&b377 from firmware finder, and also with the update.zip I found in the updates my phone downloaded.
Nothing worked, all of them got the error "Incompatibility with current version. Please download the correct update package."
Should I try even more firmware versions, or should I try something else ?
Btw, I noticed my phone, when connected to my PC, is labeled as huawei-P9-lite, and I don't think it was always like that, but it's probably just because the twrp-3.1.1-0-venus.img is originally for the P9 lite.
I came accross this thread, where somebody recommends to flash stuff from fastboot.
I have not tried it yet, I only tried to flash recovery from fastboot, and it is failing with the "command not allowed". But maybe I could try to flash some other things ? Any advice ?
For now, despite all my attempts to install stock OTA via dload method, the phone is still trying to boot into lineageOS, and failing.
I came across the "current" firmware version with a check with DC-unlocker : "NEM-L51C432B120"
So I downloaded full OTA firmware b120 on firmware finder software, and the dload method worked !
The installation went well, and after a few minutes of the first boot, I got into phone configuration.
I have one last problem, though : the phone configuration is looping.
There is only 4 languages to choose, so I have to choose english(US), then there is a weird list of countries, none in the EU, where I feel i have to choose united states, then after some steps I have to register to huawei ID thing.
If I try to skip it, it loops to the language selection.
If I try to log in to my original account, it says "device not supported for your location" and then loops to languages. (my original account is in french/France)
If I try to create a new account with new address mail, it works but then at the end says again that "device not supported for your location" and then loops to languages.
I tried with other countries it still loops.
The other languages seems to be Chinese and Japanese, but the configuration is looping too if I choose them.
I tried with/without sim, with/without wifi connected...
Dload the next firmware now and see if it works. Then set the phone
I downloaded and installed with dload method (by removing sd card and copying directly on it the files, because I don't know how to have access to the phone internal & external memory now) the next firmware (b130 version)
The phone booted, it launched a "system optimization" that was a few minutes long, and then the EMUI configuration poped up and looped through language selection, region(country), wifi connection (successful), terms and conditions, and WLAN+(switch between wlan and mobile data automatically).
I feel like the phone is working, the notification led is even blinking when I receive sms, but I have access to nothing because of this damned configuration.
Note: the connection to huawei ID isn't prompted again in the loop once I log in, from the original or the new account. In order to be prompted again to log in to the huawei ID, I have to go to erecovery and reset to factory the phone.
The saga starts with a successful rooting of my MI 8. After the Android Q update, the rooting was wiped out. I tried to repeat the root using the previous procedure but the TWRP could not read the file system. I tried a sideload of Magisk. This gave no errors but ended badly with no OS bootable. I could use TWRP to choose to restore the factory image. After the restore and OTA updates, everything looked ok but phone calls had an echo of my voice and the other party could not hear anything. I found a version of TWRP that could read the file system and decided to try an install of Havoc OS. After a wipe of recommended partitions, TWRP could no longer read the file system. I suspect that a format (no option to avoid) wiped out the ability to read the file system. I have now no OS, TWRP can not read the file system, and MiFlash gave no errors but does not load an OS. MiFlash was tried to install a factory ROM, only takes one second, gives a success result, but no go and the phone only has a boot loop now. I have an OTG adapter on order. I suspect I may need a different TWRP specific to Android Q. Any better options?
Update: Success! After finding a post highlighting a better version of TWRP I was able to format the encrypted folders which destroyed the data but allowed a successful install of Havoc OS. Phone is working again. Now on to troubleshooting voice issues. Below is the relevant post.
https://forum.xda-developers.com/mi...3-2-3-1110-t3869729/post78221593#post78221593
Udopia said:
The saga starts with a successful rooting of my MI 8. After the Android Q update, the rooting was wiped out. I tried to repeat the root using the previous procedure but the TWRP could not read the file system. I tried a sideload of Magisk. This gave no errors but ended badly with no OS bootable. I could use TWRP to choose to restore the factory image. After the restore and OTA updates, everything looked ok but phone calls had an echo of my voice and the other party could not hear anything. I found a version of TWRP that could read the file system and decided to try an install of Havoc OS. After a wipe of recommended partitions, TWRP could no longer read the file system. I suspect that a format (no option to avoid) wiped out the ability to read the file system. I have now no OS, TWRP can not read the file system, and MiFlash gave no errors but does not load an OS. MiFlash was tried to install a factory ROM, only takes one second, gives a success result, but no go and the phone only has a boot loop now. I have an OTG adapter on order. I suspect I may need a different TWRP specific to Android Q. Any better options?
Update: Success! After finding a post highlighting a better version of TWRP I was able to format the encrypted folders which destroyed the data but allowed a successful install of Havoc OS. Phone is working again. Now on to troubleshooting voice issues. Below is the relevant post.
https://forum.xda-developers.com/mi...3-2-3-1110-t3869729/post78221593#post78221593
Click to expand...
Click to collapse
When using Android 10 , the best method for rooting is using the patchboot method, and usually it does not require formatting your data.
tsongming said:
When using Android 10 , the best method for rooting is using the patchboot method, and usually it does not require formatting your data.
Click to expand...
Click to collapse
Thanks for the intro to the new technique. I am rooted again through TWRP but I will keep this in mind for the future.