Hello wonder if anybody can help
I'm looking for a flashable system image for the ASUS ME70CX.
I'm working on a ex-Demo version of the tablet with custom firmware installed for demo usage.
I downloaded the latest firmware from ASUS UL-K01A-ww-12.2.3.28-user.zip
I've erased cache ,userdata and system
From the downloaded firmware I've flashed boot.img ,fastboot.img ,and splashscreen.img
I tried to create a system image using a rooted normal version following online details copying partition mmcblk0p9 and then used sparseconverter to fix a sparse error.
But I get an error says folder not found on the device in recovery (fastboot).
So the first question would be have I copied the correct partition ?
Failing that is there a working system image I can download ?
cheers
Did you find a solution? I tried to update my sons ME170CX/K01A tablet with the download from the Asus website and now it wont boot up. I can get it into droidboot, but dont know what to do from there. I just need to get it working again. I've tried to update with fast boot but it says
error: update package has no android-info.text or android-product text.
I've also placed the update on an SD card and gone to recovery from droid boot but it does nothing.
Any help would be greatly appreciated. I'm just not familiar with using fast boot. I been trying for a couple days now, and I'm not finding what to do from here. Just that i should be able to flash from droid boot.
Edit: I found this
http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
I found the update for the CX/K01A that had the same software image version as listed in the OP and followed every step as described, with the exception of the download and renamed it to K01A_sdupdate. This all started a couple days ago when I replaced the main board because the micro usb port got ripped off the board. I was much cheaper than sending off for repair and easier for me to buy a used unit with a busted screen from eBay. When I got it all together and working it would not update from 4.3, after all I have done and following the instructions here in the OP it is now on 4.4.2. This is right where it was with the original board. Since he only uses it for games and downloaded movies I'm not messing with it anymore now that its working properly. He'll just have to start over with his games.
dave011182 said:
Did you find a solution? I tried to update my sons ME170CX/K01A tablet with the download from the Asus website and now it wont boot up. I can get it into droidboot, but dont know what to do from there. I just need to get it working again. I've tried to update with fast boot but it says
error: update package has no android-info.text or android-product text.
I've also placed the update on an SD card and gone to recovery from droid boot but it does nothing.
Any help would be greatly appreciated. I'm just not familiar with using fast boot. I been trying for a couple days now, and I'm not finding what to do from here. Just that i should be able to flash from droid boot.
Click to expand...
Click to collapse
Assuming it works the same way as the ME70CX.
First is to get the correct firmware version as not all the ones listed are compatible with all versions for a one hit update.
EG the original version I downloaded wouldn't update / install from the SD card but v10.32.1.33.3 will but it'll then update OTA to v11 .
Download the update , extract the zip files until you get to the last one eg UL-K01A-ww-10.32.1.33.3-user.zip
Rename it K01A_sdupdate.zip
This will now update from the SD card.
If you have erased the unit extract the img files from this file and flash them , then update from the SD card and reboot and it'll work again.
But you need the correct version. I went for the one that was installed in another unit or it updated to on it's first update.
So if you can boot the original chassis up and look at the software version then download the closest on to that.
If you do this to an ex-display model it'll still be in Demo mode afterwards but search for ASUS Retail site and it'll tell you everything you ever need to know about their software for retail operation. Same applies to Samsung . Samsung retail website again has everything you'll ever need to know.
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?
Hello,
english powered by google
I desperately my Xperia SP on Android is trying to switch 4.4. Unfortunately, most Totourials are useless, alone because very often missing files or they are just out of date.
After so many problems I managed to flash my Xperia. Unfortunately nothing had the desired effect due to the files.
Currently I have the following problem which I do not get resolved:
I have loaded with the Flash tool the Cyanogenmod bootfile via fastboot, earlier I had installed CWM course with USB debugging and deactivated Bootlock. ect.
Unfortunately, he did not start the CWM but the CyanogenMod and I did not have the possibility to install the ZIP file on the SD card. Instead, I've obviously just all deleted.
Currently I have no system, but only the CyanogenMod. A flash on Standart is suddenly no longer possible FAILED (remote: Download size too large). Even when I extracted the System.sin I had problems to start them in fastboot mode.
I had previously done with older files, unfortunately the installation was on the ZIP file in recovery mode error. Why I have updated the files and all programs.
Restoring the standard firmware previously ran flawlessly ...
So I really do not go on and am really desperate.
I very much hope that my one helps the more clueless than me.
Best regards,
Ben
So i assume you now have installed official sony firmware? If yes , and you have unlocked bootloader then all you have to do is install twrp recovery(TWRP recovery for Xperia SP), then download Custom rom(i.e Cyanogenmod-Cyanogenmod builds for Xperia SP), if you like also google apps(OpenGapps) and install trough recovery. It might seem difficult, i know i did not explain it very good but its late... If you have any question or you want me to write a tutorial how to install cyanogenmod step by step just tell me.
Edit: even if you cant access the system it will be easy to install cyanogenmod
Problem Solved:
Flashtool was the Problem. I used the newest Version. After a Downgrade to 9.8.16 it worked.
Thank You very much
As with my thread related to https://forum.xda-developers.com/nokia-8/help/nokia-8-sudden-restart-occurred-randomly-t3852357
I would like to flash the latest System stock OS (since there is no custom ROM yet) and decided to wipe all. I do have TWRP and all I need is system.img, boot.img or full zip to be flashed in TWRP. Does anyone have the file? Any latest up to September or October is okay if it is out there. If anyone does have it, may I request Google drive File sharing since that's the fastest file host that I can download. If there is no one have it, I will just take the obsolete one. However, I won't know if it will solve the problem.
Thank you.
Nokia 8 have more version . 1052,1004,1012...
-In version 1052 . so congratulations u have a f**king phone. The phone can't use ost tool or boot to edl mode
-There nothing rom or zip flash via twrp . only firmware flash via ost tool and ntool.
- If ur phone brick, for easily try ntool.
If u want a hard way, alrealdy have. There is a link of firmware nokia file nbo https://drive.google.com/drive/mobile/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw?usp=sharing
.
.
Then use https://www.google.com.vn/amp/s/for...eneral/nb0-unpacker-packer-tool-t3699464/amp/ for extract file nbo then u can flash system.img in this... But remember dont flash boot will break ur wifi.. However i find a way to make this worrking again ... But i dont sure my tutorial work or not although my phone save wifi again...
ValKyre said:
Nokia 8 have more version . 1052,1004,1012...
-In version 1052 . so congratulations u have a f**king phone. The phone can't use ost tool or boot to edl mode
My bad, I haven't told the phone version. It is TA-1004
-There nothing rom or zip flash via twrp . only firmware flash via ost tool and ntool.
Uh, there is a TWRP already which we can flash the system.img and boot.img or we can use fastboot to flash them.
- If ur phone brick, for easily try ntool.
Ntool is the least thing I want to do cause of many errors.
If u want a hard way, alrealdy have. There is a link of firmware nokia file nbo https://drive.google.com/drive/mobile/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw?usp=sharing
.
.
Then use https://www.google.com.vn/amp/s/for...eneral/nb0-unpacker-packer-tool-t3699464/amp/ for extract file nbo then u can flash system.img in this... But remember dont flash boot will break ur wifi.. However i find a way to make this worrking again ... But i dont sure my tutorial work or not although my phone save wifi again...
Click to expand...
Click to collapse
I already have that file. I need the latest October Patch 2018 System.img and boot.img. Anyone has it?
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.