Hello everybody,
I have my X5 flash a Custom Rom from this forum .
Now I will return tostock rom .
I seem however the Custom Rom flash partition /cust to have deleted.
Have now many attempts ( flash via fastboot , various other Rome etc. ) but TWRP always says : unable to mount / cust ( invalid argument )
would I'm grateful if someone could help me .
Please excuse my bad english.
Best wishes
Marc
Hi
download stock ROM for your region and flash it with stock recovery
it should fix your problem
I've already tried. Unfortunately, breaking the update process with an error message.
Have anyone an Idea?
bly2 said:
Have anyone an Idea?
Click to expand...
Click to collapse
first off what model is your phone ?
do you still have TWRP installed ?
how are you trying to apply the update ? from phone off or from update.app
Hello,
my phone is a KIW - L21 .
I have tried the following :
- Phone unrootet , original Recovery , on the UpdateApp tried a local update to make - > Failed
- Phone unrootet , original recoverey - > phone off vol + vol- power simultaneously - > update failed
- Phone rooted , TWRP installed , a update.zip created using huwaeiappextractor - > flash process aborts with instructions that the / cust partition can not be established .
- Tried /cust.img to flash via fastboot - > same as above
greeting
bly2 said:
Hello,
my phone is a KIW - L21 .
I have tried the following :
- Phone unrootet , original Recovery , on the UpdateApp tried a local update to make - > Failed
- Phone unrootet , original recoverey - > phone off vol + vol- power simultaneously - > update failed
- Phone rooted , TWRP installed , a update.zip created using huwaeiappextractor - > flash process aborts with instructions that the / cust partition can not be established .
- Tried /cust.img to flash via fastboot - > same as above
greeting
Click to expand...
Click to collapse
Flash this with TWRP >> http://loadbalancing.modaco.com/download.php?file=customromtemplate-5x-plk21-b130-r3.zip
Thank you for the link. The installation is, however, again with the error "fail to mount / cust invalid commando"
bly2 said:
Thank you for the link. The installation is, however, again with the error "fail to mount / cust invalid commando"
Click to expand...
Click to collapse
what version of TWRP are you using ? Use this one
did you reboot recovery and try again ?
did you try to go to TWRP / Mount and choose /cust and try again ?
if all these fail your going to need to take it to a service center theirs nothing else to do
I had an issue with /cust partition and managed to fix it last night.
This was a complicated process but I'll try and explain as best as I can.
You need to obtain the original stock CUST.img file. You can download the full system images from https://mega.nz/#!Kg9UiKiD!cCh9UK0Oi-P1UNk-e1RBk_jlUEHGm0MGYa_HSlQ-3c4
You also need simg2img from https://github.com/KinglyWayne/simg2img_win
copy CUST.img into the simg2img directory, edit convert.bat to change the command to: simg2img.exe CUST.img cust.ext4.img
Or open a command prompt and navigate to the folder, running simg2img.exe CUST.img cust.ext4.img
Once run you'll have an ext4 image. The original image is a sparse image - useless for direct writing.
Boot your device into TWRP. Mount internal storage then copy the new cust.ext4.img file to your device.
You need ADB on your computer for the next step. Open adb shell:
now do the following:
dd if=/sdcard/cust.ext4.img of=/dev/block/mmcblk0p23
assuming you copied the cust image to your internal storage
Once the dd process has completed, test this worked by mounting the cust partition inside TWRP. If it mounts then the dd worked correctly and your cust is restored.
a question:
cust.img is 205.403 KB (kiw-21L-B130)
the conversion in cust.ext4.img arrive at 524.288 KB
mmcblk0p23 (cust partition) in the device is just 507.904 KB
is normal?
It worked! Thank you thanks for your guidance and effortless !
linux33it said:
a question:
cust.img is 205.403 KB (kiw-21L-B130)
the conversion in cust.ext4.img arrive at 524.288 KB
mmcblk0p23 (cust partition) in the device is just 507.904 KB
is normal?
Click to expand...
Click to collapse
Yeah, no problem. Sizes will look different on the device but the image fits.
Thank you!
Question
Hi, i have a LeEco Le Max 2 (Le X820). I have the same problem.
Where i can find original stock CUST.img file for this model?
I wanted more, but i can not find.
Thanks.
I want to know how you ended up here asking about a different phone?! Unbelievable.
Answer
evoGage said:
I want to know how you ended up here asking about a different phone?! Unbelievable.
Click to expand...
Click to collapse
I don't know what to say, but i have the same problem and can't install nothing with TWRP.
http://www.hihonor.com/nl/support/details/?DOC_ID=84203 KIW L21 West EU try this i had same issue and it solved it. Click on downloaden (Sorry its Dutch) unzip it put the update.app file in the root of your SDcard in a folder named 'dload'. This should solve the System Failed Error that u normally get with this methode WEST EU ONLY
Answer
Thank you Demian3112, but my phone is Leeco Le Max2 (x820 model) and have android 6.0.1.
Thanks
Thanks dude, helped me out a lot.
Related
Hi,
Today i received a notification on my L22 to update to Marshmallow (310).
But when it reboots into recovery (stock), it says system update failed.
Note:
I have rooted my phone and installed custom rom before. But i used to get back to stock (both rom and recovery) with a TWRP restore. This has worked with all the previous updates of Lollipop (e.g. 130 to 150), but its not working with Marshmallow.
Can someone please help!!.
Can someone please help. I hope this is a beta version. Actually I had opted for the beta previously.
there are no restoration files zips for MM yet, alternatively, you can flash TWRP back via adb and restore your back up. else, follow the steps in thread below....good luck!
http://forum.xda-developers.com/honor-5x/help/bricked-honor-5x-t3328308
Thank you @nandakalyan @Arobase40 for the information.
I can check with them. But when i tried to login to their community, for some reason, my login credentials weren't recognized.
As an update, I tried the following
I downloaded the lollipop 150 firmware and flashed the BOOT, RECOVERY, SYSTEM and CUST image files. But I received REMOTE: COMMAND NOT ALLOWED error while flashing CUST. I even tried installing the USB/ADB drivers again. Still no luck.
Then i tried the update. Still the same error.
Again i followed step 1, then relocked the bootloader (successfully). But still got the same error. (Because i read somewhere that it could be due to modified firmware)
Looks like some issue with the package. So i might have to get back to them.
I will post the update once i get the update from them. Thank you very much guys.
Arobase40 said:
The CUST image file can't be flashed !
But I saw someone was able to rebuild the /Cust folder and its content but I'm too lazy to do the search...
It's in the Honor 5x thread.
Click to expand...
Click to collapse
That is correct, cust.img can't be flashed through ADB, I have had this issue too.
@mani0608
The only best way is to flash stock recovery, create a dload folder in the root of the sd-card, place the update.app (original firmware file) in it, boot into download mode (power + vol up + vol down) and let the whole factory image be flashed.
nandakalyan said:
That is correct, cust.img can't be flashed through ADB, I have had this issue too.
@mani0608
The only best way is to flash stock recovery, create a dload folder in the root of the sd-card, place the update.app (original firmware file) in it, boot into download mode (power + vol up + vol down) and let the whole factory image be flashed.
Click to expand...
Click to collapse
I followed this and then tried the OTA and voila it worked!!
mani0608 said:
I followed this and then tried the OTA and voila it worked!!
Click to expand...
Click to collapse
Super....congrats! Glad it worked
EDIT: My solution was to have an exFAT formatted SD card with update.app, I had previously only tried on an ext4 formatted card.
Hi everyone!
I've been looking for days for a way to get my Honor 9 working again to no avail.
It started with me trying to install a custom ROM on my EMUI 5.1 Honor9, but when the touch buttons didn't work I decided to go back to stock. This is where the problems started.
FRP and bootloader was unlocked before doing this.
After many different firmware tries I managed to get into stock rom (B130), and apparently it locked FRP again, but since the touch buttons still didn't work I decided to rebrand with B120. Bad idea.
Now my phone has FRP locked, so I can't flash images from fastboot anymore (command not allowed), and no working OS.
I do however have TWRP installed as recovery2/e-recovery, so I can still adb push images and install them via TWRP.
I've looked through every thread on this forum and tried every possible solution I could find (extracting images from update.app, copying update.app to /dload on external sd, different firmware versions etc)
If there is there anyone here that is more experienced than me that can give me any pointers in the right direction, I'd be incredibly grateful!
As far i know there only 3 service repair firmwares publicly available which works the dload way. There nougat and are meant to use from nougat.
Alright, so they won't work for me no matter how hard I try?
What alternatives are left to me?
What's your region and version firmware actually ?
You stated you rebranded ?
What region region service repair firmware did you used ?
Region is EU, I'm not really sure what my original firmware is, but i suspect around B130? I know, I'm an idiot for not checking before I wiped it..
I tried at least, to install the B120 in order to get the capacitive buttons to work, but I'm pretty sure I didn't succeed.
I've been using EU firmware to try and get the phone up and runnin. A few different versions.
have you tried to flash again B130 whit 3 fingers mode?
mmmhhh but maybe you have need stock recevery....
With 3-finger mode you mean stock recovery? (Not twrp or stock eRecovery)
How would I flash this using stock recovery, via update.app method?
When flashing stock recovery to recovery partition it boots straight to twrp (flashed to recovery2) regardless of what buttons I hold. :/
If i flash twrp to recovery and stock eRecovery to recovery2 partition and restart holding vol+ and pwr, I get a screen similar to fastboot screen with "error 2 - could not load"
I'm afraid that if i flash stock both recovery and eRecovery, I have no way of flashing images or restore twrp due to FRP being locked...
Thank you everyone for taking the time to respond, really appreciate it!
not undestrand...
now you have TWRP installed or Stock recovery? phone turn on in system or have a loop? what it is the problem? only FRP blocked?
how you can falsh twrp and stock e-recovery if you have frp blocked?
what is happen when you turn on phone holding Volume + and Power Button WHITOUT ANY USB CABLE CONNECTED?
this is three fingers way:
1) download "stock service B130" from:
https://forum.xda-developers.com/hon...stock-t3696892
2) copy UPDATE.APP and update_STF-L09_hw_eu.app to external SDCARD into /dload folder
turn on the phone holding Volume + and volume - and power ( three fingers way)
if all is good, phone restart in stock recovery and update firmware....
you will have again bootloader and frp blocked after new firmware will be flashed
if you have a twrp installed you can try this method.... but i dont know if it work whit frp locked:
1) download "stock service B130" from:
https://forum.xda-developers.com/hon...stock-t3696892
2) download those 2 file from
https://mega.nz/#F!Y59nFYbJ!fb1f4UpEdgABZ4NhOfu1JQ
3) put all files in HWOTA7 directory on external SD
4)In TWRP find the folder HWOTA7 on the phone SD and from it flash the file "hwota7_update.zip"
he phone will reboot itself into the stock recovery and it will install the firmware.
++++++ Important ! ! ! ++++++
After have installed the firmware, you need to boot into the recovery and make a full Wipe
if all ok, b130 firmware will be flashed.
let me know if you try
First of all, thanks a lot for trying to help me!
I will try this method. I downloaded the HWOTA script, however in the bash script contained in this file, it says:
#!/sbin/sh
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p34
echo --update_package=/sdcard/HWOTA7/update.zip > /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_all_hw.zip >> /cache/recovery/command
reboot recovery
Which means that I should have 3 zip files present on the phone in /sdcard/ called update, update_data_public and update_all_hw.
These zip files do not exist in the B130 firmware you linked. What files should I use for this?
I tried running it anyway and got into recovery, however it says "Software install failed! The update package does not exist. Please download the package again."
Alright, that may have thoroughly f**d me. Now TWRP is replaced with stock eRecovery.
I suppose I can put files on the SD card by using my laptop, but then I'd need the correct files. Anyone?
Now you should be able to flash with b130 service Repair files:
http://androidhost.ru/v5
Instructions inside, you will need an sdcard formated to extfat.
I've tried SO many times trying to get this update method to work, but always stuck at 5%, until now!
Seems like exFAT is the key! When formatting the SD card on my laptop with linux, it became formatted as ext4, which was fine to read and write to in twrp, but however stock recovery seems to demand an exFAT partition.
Today I went out and bought an USB SD card reader and formatted with exFAT on my windows machine and lo and behold the update was installed!
I don't know if I'm an idiot for missing this fact or if it is not iterated enough. This solved my issue though!
Thanks a lot, Oslo83 and Angelobiz
miffeltoffel said:
First of all, thanks a lot for trying to help me!
I will try this method. I downloaded the HWOTA script, however in the bash script contained in this file, it says:
#!/sbin/sh
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p34
echo --update_package=/sdcard/HWOTA7/update.zip > /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_all_hw.zip >> /cache/recovery/command
reboot recovery
Which means that I should have 3 zip files present on the phone in /sdcard/ called update, update_data_public and update_all_hw.
These zip files do not exist in the B130 firmware you linked. What files should I use for this?
Click to expand...
Click to collapse
yes... you have right...i missed somethings:
update.zip same same
update_STF-L09_hw_eu.app have to rename in update_all_hw.zip
update_data_public.zip dont need for restore....
happy that you have solved.
which files have you used?
I used the stock B130 files in the thread that you posted, worked like a charm. As stated, the issue seems to have been that Linux cannot format in exFAT, and stock recovery can only read exFAT.
As curtana has dynamic partition, we can't flash any zips to modify partitions. That's why we can't change/edit fstab to make data encryptable. But i found out, that, the partitions' content can be edited right after flashing any rom. They become RO only after first boot.
Instructions:
1. Download any Eu rom for you variant
2. Download decrypt zip from here
3. Flash Eu and flash en_de-crypt_v2.zip right after that without reboot
4. Unmount vendor partition
5. Format data and reboot.
Thanks. I'm going to try this later.
So after that you can edit root files? cuz i want to edit mixer_paths.xml because of the very low sound
After this , phone always reboot in fastboot , xiaomi eu 11.0.9.0 ! who can i fix this now?
Anasbel said:
After this , phone always reboot in fastboot , xiaomi eu 11.0.9.0 ! who can i fix this now?
Click to expand...
Click to collapse
I got the same issue and the only one thing I can fix it was to reinstall ROM or flash stock ROM via MiFlash.
I think rebooting in fastboot shows that the ROM on your device is broken.
For example when I'd tried to install Xiaomi.eu after installing LineageOS (ofc did full_wipe), I got the rebooting issue. But flashing Stock ROM before installing that ROM, It went well.
It sometimes depends on the installed ROM or other zips which you install it with
For me it worked also with Global 11.01, but not by the first Try and I could not see it in Miui, but after flashing a Custom Rom (Havoc) over it, the Device was decrypted.
Can't flash it with Joyeuse.
Can someone please port it?
Thanks!
this method does not work, writes rw, but when you delete the system application after restarting, you get bootlop.
I can't believe he provided a boot-loop tutorial
will it work for poco m2 pro (GRAM)?
@Sudeep Duhoon Bro can you help this thread out plz?
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
There is a newer Version v3 of the decryption Zip. Could you please update the Link?
If I am not mistaken, the zip is designed to encrypt, it will not work to decrypt.
Via recovery:
- If the file exists: -
/vendor/etc/fstab.qcom.bak
1 - Go to the file:
/vendor/etc/fstab.qcom
2 - With a text editor change in fstab.qcom:
"encryptable = ice" to "fileencryption = ice"
- If the file does not exist: -
/vendor/etc/fstab.qcom.bak
1 - Go to the file:
/vendor/etc/fstab.qcom
2 - We copy it in the form:
/vendor/etc/fstab.qcom.bak
3 - With a text editor change in fstab.qcom:
"encryptable = ice" to "fileencryption = ice"
The error is displayed in the selected line of the encryption.sh file, the command has the strings reversed.
Changing that line in the file should work the .zip
Hi
Emui 9.1.0.257
I have TWRP 3.4.0-1 installed i trying format data waiting over 10min
Any ideas.
Hello again - I had the same issue and after restarting without any success notice in TWRP, I was left with an not booting system.
I could fix it by flashing all the different needed *img files via fastboot. This was needed as my rescue tasks may made it even worse.
Do you have any idea why this happend? The used TWRP was TWRP-3.4.0.0-emui9_eR.img
horqai said:
Hello again - I had the same issue and after restarting without any success notice in TWRP, I was left with an not booting system.
I could fix it by flashing all the different needed *img files via fastboot. This was needed as my rescue tasks may made it even worse.
Do you have any idea why this happend? The used TWRP was TWRP-3.4.0.0-emui9_eR.img
Click to expand...
Click to collapse
Hi!
I have the same problem and tried to fix it via flashing *img files, but I don't know which. I downloaded an update.zip and extracted some *img files from the UPDATE.APP. I read somewhere that I need to flash kernel, system, ramdisk and recovery_ramdisk to get back to the stock rom. But I didn't find a ramdisk.img file to flash. So which is necessary to restore at least erecovery to get back stock rom and where to get the right files?
lenzelot said:
But I didn't find a ramdisk.img file to flash.
Click to expand...
Click to collapse
On EMUI 9.1 ramdisk is included in the recovery_ramdisk.
Try this way out...
- Make sure to have the stock recovery flash
- Download correct Service ROM for your region and EMUI version ( Settings > About phone > build number.
The bracketed (Cxxx) is your device’s regional variant. This number is very important in determining the correct firmware to download!)
- download Service ROM here: Androidhost.ru website, (type Ane- or Anne-).
- Unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it!
- Turn off your phone and flash FW using three button combo. The process will erase all your data! (and lock again the bootloader! ).
Edit: you can also try following:
- Install TWRP (on Pie)
- In TWRP flash eRecovery_ramdisk (use button Install image ). Then reboot into eRecovery and download latest versiom via WiFi.
-Alf- said:
On EMUI 9.1 ramdisk is included in the recovery_ramdisk.
Try this way out...
- Make sure to have the stock recovery flash
- Download correct Service ROM for your region and EMUI version ( Settings > About phone > build number.
The bracketed (Cxxx) is your device’s regional variant. This number is very important in determining the correct firmware to download!)
- download Service ROM here: Androidhost.ru website, (type Ane- or Anne-).
- Unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it!
- Turn off your phone and flash FW using three button combo. The process will erase all your data! (and lock again the bootloader! ).
Click to expand...
Click to collapse
Thanks for the quick response. I think I tried something like that but unfortunately the transfer to the phone stopped due to storage shortage. Is there any partition I could format using fastboot or adb if this is possible? So far I can only access the bootloader and the start screen of twrp (without really booting it). In the latter state it is possible to run adb commands.
Just read the edit. Will try so.
lenzelot said:
Is there any partition I could format using fastboot
Click to expand...
Click to collapse
Try fastboot command
fastboot erase userdata
and restart.
lenzelot said:
the transfer to the phone stopped due to storage shortage
Click to expand...
Click to collapse
You can use also OTG.
Sorry for the late response and thanks for your great help!! erasing the userdate was the key
Hi folks, I've had a Huawei P20 Lite lying around here for a while. It is a demo device.
I was able to successfully unlock the bootloader with using the Testpoint method.
Now I need help to change the country code from "demo" to "eu" and I also need the right firmware. Is there a free way to change the country code?
I hope you can help me with that ? Thanks in advance.
cvpcvp said:
Hi folks, I've had a Huawei P20 Lite lying around here for a while. It is a demo device.
I was able to successfully unlock the bootloader with using the Testpoint method.
Now I need help to change the country code from "demo" to "eu" and I also need the right firmware. Is there a free way to change the country code?
I hope you can help me with that ? Thanks in advance.
Click to expand...
Click to collapse
Hi, look here
If you are running EMUI 9.1, flash C432 oeminfo and use variant with HuRupdater https://forum.xda-developers.com/t/...0-0-046-070f-emui-8-0-0.4324543/post-85538623
https://forum.xda-developers.com/t/...0-0-046-070f-emui-8-0-0.4324543/post-85538725
Thanks in advance. Somehow I can no longer get into the / system or the smartphone can no longer boot. When running HuRupdater I also get an error message that / System cannot be mounted. It only boots TWRP
I was able to import the oeminfo beforehand. There weren't any problems.
cvpcvp said:
Thanks in advance. Somehow I can no longer get into the / system or the smartphone can no longer boot. When running HuRupdater I also get an error message that / System cannot be mounted. It only boots TWRP
I was able to import the oeminfo beforehand. There weren't any problems.
Click to expand...
Click to collapse
Can you write down exactly what you did?
What is your version of EMUI?
In fastboot mode run commands:
fastboot oem get-build-number
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
I guess I've stupidly used the wrong command line a number of times to get twrp to run.
fastboot flash system, boot or recovery twrp....
At least it worked with the country ID change ... if only a small consolation for the first
fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.112(C432)
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 8.0.0.112(C432)
cvpcvp said:
ANE-LX1 8.0.0.112(C432)
Click to expand...
Click to collapse
your firmware is incomplete, it must be 8.0.0.143, if I'm not mistaken. Try again Huru method & factory reset in Stock recovery (not in TWRP!).
Or, download Service ROM Link , unpack , there's dload folder in "Software" . Copy dload folder (without unpacking it) to the OTG flash, turn off the phone and press and hold both volume buttons + Power ( this method will lock the BL again).
Thanks for the files. But i get an
Softwaere install failed
Incompatibility with current version.
Please download the correct update package.
EDIT: cant find the firmware version: ANE-L01C185B112 / ANE-LX1 8.0.0.112(C432)
EDIT2: same fail with 8.0.0.178(C432)
cvpcvp said:
Softwaere install failed
Incompatibility with current version
Click to expand...
Click to collapse
Probably due to incomplete firmware .112 , ( it was stupidity on my part to suggest Service ROM in this case, sorry. Maybe I was too sleepy...).
1. Try again Hurupdater method, it should work (don't forget to press Volume down)
2. Reboot into eRecovery, if possible, and select Download latest version and recovery
cvpcvp said:
cant find the firmware version: ANE-L01C185B112
Click to expand...
Click to collapse
Flash only C432 regional variant!
-Alf- said:
Probably due to incomplete firmware .112 , ( it was stupidity on my part to suggest Service ROM in this case, sorry. Maybe I was too sleepy...).
1. Try again Hurupdater method, it should work (don't forget to press Volume down)
2. Reboot into eRecovery, if possible, and select Download latest version and recovery
Click to expand...
Click to collapse
Can you explain me, how i can Boot into twrp without Flash twrp in recovery ramdisk?
cvpcvp said:
without Flash twrp in recovery ramdisk?
Click to expand...
Click to collapse
And what stopping you from doing it?
-Alf- said:
And what stopping you from doing it?
Click to expand...
Click to collapse
Okay, idon't think that's relevant anymore anyway
I found the problem. It was the TWRP version. I took the latest one (twrp-3.5.2_9-0-anne.img) and it couldn't mount the /system partition. Now I took a version from this forum (twrp-3.2.1-0.img), which seems to be specially adapted for the Huawei devices. Unfortunately, it doesn't support OTG, but that wasn't a problem because I moved the files it to the internal memory.
Only with this twrp version could HuRUpdater.zip be executed correctly and all other files just like that. Here, too, I was first asked to press the vol-down button.
After the smartphone finally boots properly, I flash the firmware via dload to lock the bootloader again and do over the Recovery Wipe data / factory reset + cach partition.
Now I'm on version 8.0.0.046(0CXB). Unfortunately the device cannot find a new firmware version and nothing can be updated via HiSuit.
Can you tell me which step I have to take now to get the latest Android version for the device?
Thank you very much so far for your help
cvpcvp said:
Now I'm on version 8.0.0.046(0CXB)
Click to expand...
Click to collapse
Unfortunately, you have incomplete FW there again, I think you're doing something wrong. And until the correct FW is there, you won't be able to receive OTA update or update via dload.
If you have followed instructions to the letter , it must work.
Use this TWRP . ( I don't know why you used TWRP 3.5.2.9, in the guide there is a link to 3.2.1-pretoriano80.). 3.5.2.9 isn't fully compatible with our device.
Try this way out:
- Flash TWRP
- Wipe - format data
- Reboot back to TWRP
- Wipe - Advanced wipe - wipe Dalvik/ART, cache, data, system
- Go back and flash HuRu
Note: the installation of the first file (write radio image...) must take longer, 2-3 minutes, this is proof that the installation is proceeding properly.
Btw, have you tried update via eRecovery & Wi-Fi?
Did it exactly like that. And then the 9.1.0.370 (C432) from the same thread loaded (dload / ANE-L01_hw_eu).
Now i have the firmware: ANE-LGRP2-OVS 9.1.0.370 in the device information.
Unfortunately, there is no further update, but I also don't know whether the current one is already the most recent?
What I also notice is that Dual-Sim settings are available in the menus. The IMEI2 is only provided with 000000000000000. I know that my device "only" supports single SIM.
Can I fix that too? Then everything should be fine as far as possible
cvpcvp said:
ANE-LGRP2-OVS
Click to expand...
Click to collapse
Wrong again .
cvpcvp said:
What I also notice is that Dual-Sim settings are available in the menus. The IMEI2 is only provided with 000000000000000. I know that my device "only" supports single SIM.
Click to expand...
Click to collapse
Oh, it's all clear now
Because this oeminfo is for dual SIM. Oeminfo for single SIM can be found for example here:
https://forum.xda-developers.com/t/c432-single-sim-oeminfo.3873312/
Also update_all_hw.zip file is for ANE-L21, you need ANE-L01, unfortunately, I don't have files for single SIM.
cvpcvp said:
Can I fix that too?
Click to expand...
Click to collapse
Maybe...You have to downgrade to Oreo via HuRupdater using downloaded files, then install TWRP over eRecovery and install stock Recovery.
Download https://androidhost.ru/2zMw and create dload folder .
In TWRP install new oeminfo.img , then go back to the main TWRP's menu, select Reboot > Power off. Use three buttons kombo to flash service ROM.
To be honest, I've never tried a variation like this, so I'm not responsible for this procedure, but it should work. The question is, is it worth it ...
-Alf- said:
Wrong again .
Click to expand...
Click to collapse
Which step is missing now exactly? I followed the steps from you. I also used the files from the other thread that you linked. The single-sim / dual-sim problem is not important either. The main thing is that it works that way too
cvpcvp said:
The single-sim / dual-sim problem is not important either.
Click to expand...
Click to collapse
Are you sure? In my opinion, this is your main problem...
Hello, it's been a while. I sat down again and went through everything. The dual SIM files fold onto a single SIM smartphone. I was finally able to install the update via eRecovery after flashing via TWRP. Then two updates were pulled or installed via Android OS. Now I'm on 9.1.0.132 (C432E5R1P7).