Related
[Solved] Idol 3 5.5 6045O MM update failing with "has unexpected contents" hyp error
I previously used Panasonic Eluga Switch ,installed AlekOS 2.5, reloaded a backup of my boot and system image partitions made before i installed AlekOS 2.5, became unable to access fastboot controls after that, updated using mobile upgrade q 5.0.0 back to 5.0.2, got the OTA update and received the error listed below.
The error I get is:
"EMMC:/dev/block/bootdevice/by-name/hyp:73728:e57103f3c7eae1b83159aac575f3855d2f4c534b:73728:66fe261ae2b46ed4a9ad2df6f6e6ab2d96701e49" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
E:unknown volume for path [/tctpersist/fota_retry_counter]
E:unknown volume for path [/tctpersist/fota_retry_counter]
Installation aborted.
E:unknown volume for path [/cache/recovery/block.map]
E:erasing upade package failed errno =2
E:unknown volume for path [/cache/recovery/block.map]
I have tried factory resetting, mobile upgrade q 5.0.0 , wiping the cache after factory resetting and after mobile upgrade q , but I still get the error.
When I wipe my entire system, the update.zip looks for something that is within system, does not find it, and fails.
Solution Edit: Seems the problem may have been with the version of the Mobile Upgrade Q I was using. The one for the idol 3 listed on Acatel's site (version 5.0.0 ) was not the latest Mobile Upgrade Q version! Even though the latest Mobile Q version was within a different phone's area (version 5.0.9) it has the options for all the other phones just like version 5.0.0. So I Used the newest version and and side loaded my update using the stock recovery adb. I think you should be able to just update normally without having to side-load ,however, after using the updated mobile upgrade q.
AceIn said:
I previously installed AlexOS 2.5, reloaded a backup of my boot and system image partitions made before i installed AlexOS 2.5, became unable to access fastboot controls after that, updated using mobile upgrade q back to 5.0.2, got the OTA update and received the error listed below.
The error I get is:
"EMMC?/dev/block/bootdevice/by-name/hyp:73728:e57103f3c7eae1b83159aac575f3855d2f4c534b:73728:66fe261ae2b46ed4a9ad2df6f6e6ab2d96701e49" has unexpected contents.
E?Error in @/cache/recovery/block.map
(Status 7)
E?unknown volume for path [/tctpersist/fota_retry_counter]
E?unknown volume for path [/tctpersist/fota_retry_counter]
Installation aborted.
E?unknown volume for path [/cache/recovery/block.map]
E?erasing upade package failed errno =2
E?unknown volume for path [/cache/recovery/block.map]
I have tried factory resetting, mobile upgrade q, wiping the cache after factory resetting and after mobile upgrade q , but I still get the error.
When I wipe my entire system, the update.zip looks for something that is within system, does not find it, and fails.
I may need a STOCK idol 3 6045O bootstack with a stock hyp?
Click to expand...
Click to collapse
You can try Eluga Switch Firmware and then, restore your 5.0.2 backup
If it doesn't work, you have to request all boot block from 5.0.2 6045O (tz,rpm,sbl1,aboot,hyp).
murigny64 said:
You can try Eluga Switch Firmware and then, restore your 5.0.2 backup
If it doesn't work, you have to request all boot block from 5.0.2 6045O (tz,rpm,sbl1,aboot,hyp).
Click to expand...
Click to collapse
I mean I've already tried restoring my backup, maybe my backup of my boot and my system image were already had a corrupted hyp? It is odd that even using alcatell's mobile q isn't getting me back to a stock untouched hyp. Yeah I think I need to request all boot block from 5.0.2 6045O. How do I do that?
AceIn said:
I mean I've already tried restoring my backup, maybe my backup of my boot and my system image were already had a corrupted hyp? It is odd that even using alcatell's mobile q isn't getting me back to a stock untouched hyp. Yeah I think I need to request all boot block from 5.0.2 6045O. How do I do that?
Click to expand...
Click to collapse
Do you mind booting TWRP from fastboot and pulling the update.zip from the device? You could also pull it to your computer and edit the updater-script to remove patching that file and see if it gets somewhere.
Unjustified Dev said:
Do you mind booting TWRP from fastboot and pulling the update.zip from the device? You could also pull it to your computer and edit the updater-script to remove patching that file and see if it gets somewhere.
Click to expand...
Click to collapse
Here is a link to the OTA update.zip my phone downloads.
Link
Unjustified Dev said:
Do you mind booting TWRP from fastboot and pulling the update.zip from the device? You could also pull it to your computer and edit the updater-script to remove patching that file and see if it gets somewhere.
Click to expand...
Click to collapse
Yes, if using TWRP, just edit updater-script and remove patch check and patch apply for hyp.
AceIn said:
Here is a link to the OTA update.zip my phone downloads.
Link
Click to expand...
Click to collapse
Unzip for updater-script
So I am going to try to use Mobile Update Q version 5.0.9 to get android MM on my device through that program. I will update if it succeeds. Also seems as though my system partition was larger than it should have been somehow .
Edit : Nope still only gets me to a stock 5.0.2 :/
Edit2 : Trying to sideload the update.zip from the stock version of my phone, given by mobile update q 5.0.9, through the stock recovery adb. It is looking promising.. It got past verifying the current system and is now on patching system files!
Sweet ! It worked! Thanks for the push in a different direction Unjustified Dev!
Some things I did differently were not upgrading while in developer enabled mode, Using mobile upgrade q 5.0.9, and trying to sideload the MM update as soon as my phone booted into 5.0.2.
AceIn said:
Sweet ! It worked! Thanks for the push in a different direction Unjustified Dev!
Click to expand...
Click to collapse
Can you tell me all the steps you went through to install the update? I've been having the same issue as you and I also have the 6045O. Thank you.
SenyorMauricio said:
Can you tell me all the steps you went through to install the update? I've been having the same issue as you and I also have the 6045O. Thank you.
Click to expand...
Click to collapse
[1] There is this program called mobile upgrade q that you can get from the Alcatell website. Get mobile upgrade q version 5.0.9.
[2] Run that program and follow its instructions, You WILL loose all your apps and internal storage data (data not on your sd card) in the process.
[3] I guess once your phone boots up it will be on stock 5.0.2, I think you can just update from here normally ... but what I did was sideload using adb (look it up it is a downloadable program and also something that come within the stock recovery of the phone which you get to by shutting down your phone holding down both power and volume up buttons and releasing the power button while still holding the volume button up when the screen turns on.)
AceIn said:
[1] There is this program called mobile upgrade q that you can get from the Alcatell website. Get mobile upgrade q version 5.0.9.
[2] Run that program and follow its instructions, You WILL loose all your apps and internal storage data (data not on your sd card) in the process.
[3] I guess once your phone boots up it will be on stock 5.0.2, I think you can just update from here normally ... but what I did was sideload using adb (look it up it is a downloadable program and also something that come within the stock recovery of the phone which you get to by shutting down your phone holding down both power and volume up buttons and releasing the power button while still holding the volume button up when the screen turns on.)
Click to expand...
Click to collapse
I got all that, how do I capture the OTA file before it deletes itself so I can sideload it?
Download it from the idol 3 Reddit, someone uploaded their's.
Or after you download the update you need to unlock the bootloader with fastboot commands, boot into twrp, and copy the update.zip elsewhere.
this is where the update will be /data/data/com.tcl.fota/.fotadownload/update.zip ... but you can only really access those folders through TWRP
AceIn said:
Download it from the idol 3 Reddit, someone uploaded their's.
Or after you download the update you need to unlock the bootloader with fastboot commands, boot into twrp, and copy the update.zip elsewhere.
this is where the update will be /data/data/com.tcl.fota/.fotadownload/update.zip ... but you can only really access those folders through TWRP
Click to expand...
Click to collapse
Thanks, it worked!
Hey folks, im hoping someone can help me out as im at my wits end here.
When i first got my phone i was able to install TWRP and root the phone and install a custom rom.
Then i downloaded the latest version of Twisted mate 8 and used TWRP to install it and for whatever reason when the phone went to reboot it put me into EMUI recovery and forced me to install the latest version with recovery.
Now that my phone is cllean slate, im trying to install TWRP and with no success. My bootloader is still unlocked but no matter what process i use, wether its ADB or SRK tool kit, after i do the cmd entry and it says its been installed, when i try to reboot into TWRP (holding volume up with power) I get EMUI.
its as if the latest version of EMUI is preventing me from installing TWRP again.
Does anyone know what could be the issue.
also can anyone recommend a site that has a clear simple step by step guide to rooting this phone?
I need to install Twisted Mate 8 or Kang VIP ASAP.
Thanks
Yeah. Install twrp manager from play store and try to reboot from there. But both volume buttons at start and release them almost immidietly
Skickat från min HUAWEI NXT-L29 via Tapatalk
I was finally able to install TWRP but when I enter TWRP and it first asks me for a code for the encrypted data, which I never encrypted, and when I bypass that and try to install an img all the storage options say 0 mb
spinward said:
I was finally able to install TWRP but when I enter TWRP and it first asks me for a code for the encrypted data, which I never encrypted, and when I bypass that and try to install an img all the storage options say 0 mb
Click to expand...
Click to collapse
Hi spinward,
You have to format data with twrp. Don't forget to save it first and restore it after formating.
grofock said:
Hi spinward,
You have to format data with twrp. Don't forget to save it first and restore it after formating.
Click to expand...
Click to collapse
I've done the format in TWRP and nothing changes, except the stock ROM is reset.
When i enter TWRP again the partitions/hd all say 0mb still
Flash TWRP via TWRP and see
Hi,
I think I ran into the same problem while updating my AL-10 from B172 to B361 and all the detours one has to make during that update trajectory.
After flashing TWRP, you have to reboot but make sure your phone isn't connected with USB-cable to your computer. That did the trick for me
Regards,
Build Number: FRD-L04C567B320 (USA)
Files for DOWNLOAD:
Download link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v68366/f1/full/update.zip
Region Patch:
http://update.hicloud.com:8180/TDS/...66/f1/full/hw/usa/update_data_full_hw_usa.zip
How to install:
1. Requirements: Your device needs to have TWRP custom recovery installed and has to be rooted.
2. Before proceeding make sure that your device model is FRD-L04 from Settings > About phone.
3. Download the update.zip package from above links and copy it to your Sdcard /dload folder.
4. Turn your phone off and reboot into recovery mode by hold Vol up + Power for a few seconds.
5. Back up all the partitions into the external microSD card (recommended).
6. Now go to Install and select the update.zip package you copied to your Sdcard.
7. Upon installation wipe the cache and reboot your phone.
8. In case you encounter issues with Bluetooth, NFC, etc you can try flashing the region package provided above through TWRP.
Warning: As mentioned earlier, this is a beta update that contains many bugs and has several compatibility issues with hardware and 3rd party apps.
USE IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY BROKEN RELATED TO IT
perzan07 said:
Build Number: FRD-L04C567B320 (USA)
Files for DOWNLOAD:
Download link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v68366/f1/full/update.zip
Region Patch:
http://update.hicloud.com:8180/TDS/...66/f1/full/hw/usa/update_data_full_hw_usa.zip
How to install:
1. Requirements: Your device needs to have TWRP custom recovery installed and has to be rooted.
2. Before proceeding make sure that your device model is FRD-L04 from Settings > About phone.
3. Download the update.zip package from above links and copy it to your Sdcard /dload folder.
4. Turn your phone off and reboot into recovery mode by hold Vol up + Power for a few seconds.
5. Back up all the partitions into the external microSD card (recommended).
6. Now go to Install and select the update.zip package you copied to your Sdcard.
7. Upon installation wipe the cache and reboot your phone.
8. In case you encounter issues with Bluetooth, NFC, etc you can try flashing the region package provided above through TWRP.
Warning: As mentioned earlier, this is a beta update that contains many bugs and has several compatibility issues with hardware and 3rd party apps.
USE IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY BROKEN RELATED TO IT
Click to expand...
Click to collapse
Thanks ..
I might as well post this here -> -> How to: Root and repair data on the FRD-L04 - B320
https://forum.xda-developers.com/showpost.php?p=70266853&postcount=262
Will android pay stop working even if I use the official beta 7.0?
Thanks man, but is there any successful way to flash B324 so far?
Is Wi-Fi calling enabled in this beta?
Managed to do the same using Charles app (see https://forum.xda-developers.com/ho...-to-nougat-t3510275/post69885525#post69885525) without any unlocking and flashing.
I have the FRD-L04B567 phone. I installed the TWRP for the Honor 8. I have installed a different ROM (CM13.1 ROM) successfully. I followed your instructions to the "T" in post #1 . The install of update.zip stopped at /cust with an error. I tried wiping and rebooting but am stuck in the "honor" bootup screen. Unable to force back into TWRP or fastboot or ADB at this time. Still picking up the pieces....
UPDATE: I forced phone into Huawei eRecovery screen and selected factory reset/wipe That got Nougat running but there is no keyboard and Google will only allow voice for any input. Since my wifi is encrypted, I cant give Nougat a password to get on the internet. I am creating a temporary unencrypted network to see if I can get further.
UPDATE: TWRP was wiped so I will reinstall. Then I will try update the regional update (second update mentioned)
UPDATE: Reflashed TWRP 3.0.2.0 for Honor 8, I can get into the bootloader but not recovery, eRecovery works but...(worthless). I cant flash the second update.zip because I cant get TWRP started. Obviously 3.0.2.0 is not compatible with Nougat, I may try 3.0.3.0? why not...
UPDATE - Flashing TWRP 3.0.3.0 was dumb. Now ADB sees the device (good) but I can not get to bootloader or recovery. TWRP flashes (displays) once a second and will not start (bad) . Hopefully someone can learn from my quest.
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
thekubiaks said:
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
Click to expand...
Click to collapse
This guy
https://forum.xda-developers.com/member.php?u=4210629
Could help you recover, but he will be back only after 15th Jan.
Have you tried Huawei's hisuite? It has a recovery option..
yalokiy said:
This guy
https://forum.xda-developers.com/member.php?u=4210629
Could help you recover, but he will be back only after 15th Jan.
Have you tried Huawei's hisuite? It has a recovery option..
Click to expand...
Click to collapse
Thanks for the reply, I finally got TWRP 3.0.2.0 for Honor 8 flashed (but now it won't work), I believe Nougat and TWRP aren't compatible. Huawei Hisuite said that phone was fine and recovery not necessary??? I disagree. I think I will have to wait for TWRP that is Nougat compatible with FRD-L04
thekubiaks said:
I have the FRD-L04B567 phone. I installed the TWRP for the Honor 8. I have installed a different ROM (CM13.1 ROM) successfully. I followed your instructions to the "T" in post #1 . The install of update.zip stopped at /cust with an error. I tried wiping and rebooting but am stuck in the "honor" bootup screen. Unable to force back into TWRP or fastboot or ADB at this time. Still picking up the pieces....
UPDATE: I forced phone into Huawei eRecovery screen and selected factory reset/wipe That got Nougat running but there is no keyboard and Google will only allow voice for any input. Since my wifi is encrypted, I cant give Nougat a password to get on the internet. I am creating a temporary unencrypted network to see if I can get further.
UPDATE: TWRP was wiped so I will reinstall. Then I will try update the regional update (second update mentioned)
UPDATE: Reflashed TWRP 3.0.2.0 for Honor 8, I can get into the bootloader but not recovery, eRecovery works but...(worthless). I cant flash the second update.zip because I cant get TWRP started. Obviously 3.0.2.0 is not compatible with Nougat, I may try 3.0.3.0? why not...
UPDATE - Flashing TWRP 3.0.3.0 was dumb. Now ADB sees the device (good) but I can not get to bootloader or recovery. TWRP flashes (displays) once a second and will not start (bad) . Hopefully someone can learn from my quest.
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
Click to expand...
Click to collapse
If you want to get back to any working state, i recovered from 7.0 unbootable to vanilla 6.0 like so (for frd-l09, but probably still applies):
https://forum.xda-developers.com/honor-8/how-to/honor-8-bricked-t3521813/post70326674#post70326674
// edit, also for completeness, i then flashed twrp 3.0.2 (official) and installed the cm 7.1.1 from the other thread here. All working fine.
fuflo,
thank you for your reply, it helped me get my Honor 8 back up and running.... I am now running CM 14.1 and Nougat 7.1.1 on my FRD-L04
Cheers
---------- Post added at 05:32 AM ---------- Previous post was at 05:31 AM ----------
fuflo,
thank you for your reply, it helped me get my Honor 8 back up and running.... I am now running CM 14.1 and Nougat 7.1.1 on my FRD-L04
Cheers
B320? I used these update files and mine says B317. Am I missing something?
jim262 said:
B320? I used these update files and mine says B317. Am I missing something?
Click to expand...
Click to collapse
Look again in the thread closely, you'll find another script to go to B320
Same problem as above, I could flash the update.zip, but not the USA package, maybe I didn't have the right TWRP version?
Hello, I would like some help since I got this device just yesterday.
I got it with the EMUI 4 Android 6.0 stock installed on it. Since there was no update for it I unlocked the bootloader installed twrp rooted and manually flashed EMUI 5 7.0. Everything worked fine.
I created a backup through TWRP and restored it succefully multiple times.
Then I installed the Meticulus TWRP (since I was told it is a prerequisite for the AOSP). I Flashed the AOSP but it stuck during the boot animation (30 minutes afterwards I powered it off).
I reflashed my old TWRP and tried restoring my backup. IT fails with the explanation "Cannot wipe /vendor" while at the top it says "Cannot mount /vendor (invalid argument)" "Cannot mount /product (invalud argument)".
Anyone has a clue how to fix this? Fastboot adb all works so there should be a way to boot into an OS properly?
Since AOSP was not booting i guess you forgot formatting /data partition to ext4... And did u Used Stock vendor and not openkirin ones ?
Gesendet von meinem Honor 6X mit Tapatalk
As said I have replaced the custom TWRP with the default one so I think this should not apply anymore?
The "cannot mount vendor/product" messages came from the default TWRP after I reflashed it again.
At the top it says "cannot mount /vendor" either so I guess that is the actual problem?
It would be nice to get teh AOSP up but I really want to be able to boot into something first honestly.
And did u Used Stock vendor and not openkirin ones
Click to expand...
Click to collapse
Can you please explain? When I flashed your ROM i was on your TWRP. Does this even matter anymore?
At best I would be able to restore my backup.
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
algg said:
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
Click to expand...
Click to collapse
Yes you can but not creating it through twrp, but flashing it by fastboot mode: this is because
image (.img) files needs to be flashed by fastboot mode to avoid any kind of problem.
So, you should look for the last version of stock firmware on which you was before going custom, like BLN-L21CXXXB368 for example; tell me your build number and I'll find the package for you. Then, extract from the UPDATE.APP (a very big file that contains every partition in your phone like recovery, vendor, data, ecc. - you'll find this file inside the zip archive that contains the downloaded update) the vendor.img using Huawei Update Extractor, and then flash it through fastboot mode using the command "fastboot flash vendor vendor.img".
Otherwise, you could rely on dload method to reflash a full update package, and this should really fix everything since that it'll be like a new and clean installation of the OS. Then, unlocking the bootloader again and reflash TWRP to finally restore your previous backup made when it was working would be the final step.
Feel free to ask for further help
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
algg said:
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
Click to expand...
Click to collapse
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload because package verification always failed at 5%, i tried every combination but without success.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
RedSkull23 said:
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload, i never be able to using it successfully because package verification always failed at 5%.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
Click to expand...
Click to collapse
For fastboot yes flashing recovery or boot do work but vendor does not. Maybe the ISO is corrupted somehow I will try it again on a different machine now with the tool.
The link you posted the dload method from is the one where I initially found it as well so yea.
Also it shouldn't matter what I install since the only thing I need is the actual vendor (and product?) partition to work. I have a functional backup just TWRP cannot create/mount the partitions. So even a way to just create them without any data would actually fix my problem (at least I hope so?)
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
algg said:
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
Click to expand...
Click to collapse
@RedSkull23, thanks for the tag mate.
@algg, No need to flash the vendor image as you already had the stock vendor img.
Now what else you can try is to flash the stock recovery, boot to stock recovery, select factory reset and reboot. It should most probably fix the issue.
If not, reflash the TWRP, a regular TWRO available and not specific to elite or meticulous, but generic one given by OldDroid.
I hope you have downloaded the content for dload, if not, download these for B140.
Flash this via TWRP- http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_BLN-L21_hw_meafnaf.zip
no further changes and Then use dload method for this file- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v105054/f1/full/update.zip
Try above and provide feedback. This is what I could think of best possible way to have everything with all system app working.
If not, let me know and I will try to help further.
Hi, I thought I need the vendor image since TWRP (all versions) tell me "Could not mount/wipe vendor" and "Could not mount/wipe product" "invalid argument" for both.
I tried the factory reset before but it does not work. It stops at 23% then shows a red exclamation mark and just goes to the original screen with the 3 buttons (restart, shutdown and wipe).
I am currently trying to get it to recognize my sd card. But somehow it does not work through TWRP it just does not recognize the 8GB SD Card. Also I am currently on the TWRP I was before all of this happened (3.1 openkirin). Without the SD Card recognized I can't put the dload files for it on it and in turn I can't use the dload.
I mean technically it should very well be possible to fix the device since it isn't a real brick and even TWRP and Fastboot load. It's just that all those little things are somehow ruining it.
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
algg said:
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
Click to expand...
Click to collapse
Sure, let me explain.
The first file is the data file which will install few systems apps like file manager, updater, themes, clock, fm radio etc. This will work via dload as well but the installation time is around 3-7 seconds so, over the course of time and flashing few times, i realised that these PV files cannbe flashed via TWRP and it works perfectly fine specific to PV files( twrp won't supoort other stock zips). We foash this first so that it updates your buld number and also does not replace the recovery with stock (as if you flash the main update zip first, it will replace with stock recovery so flashing the 2nd file will be quick but with unstable system apps, sometime).
Now we flash the main zip file with update.app via dload and it Install the main firmware for boot, vendor, recovery, system, usrdata etc.
Hope this explanation helps, if not let me know and I will rephrase myself.
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Is there any way I can "debug" what is going on while the boot animation is playing?
What is confusing me is that the boot animation plays just normal but it simply does not continue to the actual OS.
algg said:
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Click to expand...
Click to collapse
Not bricked..its just Data is not mounted or encryption. Should never encrypted it. NVM.
Do one thing, boot to twrp recovery. Try flashing and get error, then go to main TWRP page and click on reboot, select recovery out of 4 options( power off, system, bootloader and recovery). It will boot to recovery, now try flashing it again and see. Most if the time it helps.
Else, go to main page, select wipe, click on format rather than wipe here, it will prompt for typing Yes to confirm. Biit to recovery from main twrp page ( as mentioned above). And try this same thing of formatting data couple of times and then flash the zip and then dload.
I know these are tedious steps but inhave revived my device many a times with all these tricks after some efforts.
Good luck
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
algg said:
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
algg said:
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
I'm happy for you man, indeed it would be so bad, especially because you got this device 3 or 4 days ago if i didn't read bad, anyway what matters is that now it works. Are you able to restore the previous backup through TWRP now? (But before trying... Make a backup of your actual OS )
shashank1320 said:
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
Click to expand...
Click to collapse
Are you joking man? I just tagged you for more help, but practically you helped him in everything, not me; I'm sure that you would noticed the thread and helped as always even without my tag, i just speeded up things for being helpful to algg.
algg, I'd like to apologize myself; i didn't vanished after tagging shashank, today i just was at work and obviously i was busy for help, but as i saw with pleasure he already helped you to restore your OS and that was the objective. Nice one, guys!
Hi guys,
I cannot do anything.
As you can see in the image, I can only have access to erecovery. I tried to download and recover but at the point of getting package from server, i receive the error info failed.
I can get access to fastboot push vol down and power.
cant get access to recovery push vol up power.
3 buttons works
while in recovery mode my win 10 do not recognize the usb drivers.
jacllondon said:
Hi guys,
I cannot do anything.
As you can see in the image, I can only have access to erecovery. I tried to download and recover but at the point of getting package from server, i receive the error info failed.
I can get access to fastboot push vol down and power.
cant get access to recovery push vol up power.
3 buttons works
while in recovery mode my win 10 do not recognize the usb drivers.
Click to expand...
Click to collapse
Ive Found A Solution Follow This Link
And find the service repair post and follow the instructions
https://forum.xda-developers.com/honor-8/development/firmware-huawei-honor-8-frd-l09-stock-t3696921
You Would Have To Use dload To Fix It
Find The Post In The Picture
thanks but i have a frd lo4
jacllondon said:
thanks but i have a frd lo4
Click to expand...
Click to collapse
So I managed to get back to TWRP recovery.
When I try to flash a rom I receive this errors:
/cust invalid argument
/system invalid argument
/vendor invalid argument
/product invalid argument
jacllondon said:
So I managed to get back to TWRP recovery.
When I try to flash a rom I receive this errors:
/cust invalid argument
/system invalid argument
/vendor invalid argument
/product invalid argument
Click to expand...
Click to collapse
I See, What You Need To Do Is Use, Is Use HurUpdater And Download The Latest Full OTA MF, MAKE SURE IT IS APPROVED. Rename The TWRP File That You Used To "recovery.img" In Order To Keep TWRP.
HurUpdater:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Make Sure Ur Doing This On Ur MicroSD Card
Follow The Instruction, Rename Each File As Same As The Image
Put HurUpdater As The Same Folder At The Firmwares
So I followed those steps.
At the end of flashing got the same errors.
Phone now is showing only the honor logo.
jacllondon said:
So I followed those steps.
At the end of flashing got the same errors.
Phone now is showing only the honor logo.
Click to expand...
Click to collapse
Delete Everything Like Format Data, Clearing Internal Storage, Vendor, All Files In Internal Storage Gone...
Make Sure TWRP Says That There Is No OS Installed
Then After That Flash The TWRP File That Your Using As A Recovery Using TWRP Just Incase It Disappears. Clear Everything Thing That Twrp Has An Error Of.
Then reboot to recovery
That Might Fix The Errors
Dont Worry Ive Done This Before And My Device Was Fine For Flashing Roms And Other Stuff.
And Maybe Redo It What I told You
I Know That This Is Probably Gonna Work Because I Cleared Everything Before And Install A Rom And I Was Fine Or Install EMUI
Flash Hurupdater Again I think If The File Are There
You Could Install A Custom Rom If You Want Though, But You Will Have Worser Battery Life Though
Fixed it thank you!!!!!!!!!!!!!!!!!!!!!!!!!
jacllondon said:
Fixed it thank you!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Yasss!!! Woohoo!