I want to help you ... I want to go back from updating Marcimello to Lolipop and I have tried many methods, including installation through. Huawei program extracted and installed, but the problem emerged and is fingerprint does not exist. And tried it through fastfood installation. Installation up to 5% and installation fails ... Please help me ?
Related
Hello, this is my first post. First off thanks to the entire community for this wonderful forum and the ability to ask questions like the following here .
Phones background information: In my spare time I attempt to fix phones for family and friends. I recently received a sm-n910a (att note 4) that was on stock 4.4 kitkat and did (does) not have an active at&t mobile plan. Its function is to be used as a wifi phablet for web surfing/games and the user was interested in upgrading the Android system to 6.0MM if possible as well as SIM unlocking the phone for a future Straight talk prepaid plan.
1. Without full-root I was unable to make a complete backup initially but owner wasnt worried about a complete data wipe so I didn't think it would be a problem. (Dumb mistake I know now )
2. Used Odin to flash stock Android 5.1.1
3. Used Kingroot and/or Kingoroot to temp root. Pretty sure it was Kingroot, but not positive.
4. Used Z3x box program to simunlock (was successful)
5. Made complete backup using ADB
6. Downloaded stock 6.0 updates from xda forum post and loaded on sd-card.
7. Entered recovery to update to 6.0 but found errors:
E: failed to mount /efs (invalid aurgument)
DM verity verification failed // Did not display anything about the drk like other people mentioned online.
8. Used Z3x box program to wipe efs (was successful)
9. Entered recovery to check errors and the E: failed to mount /efs was gone
10. Researched online about Dm verity verification failed as much as possible and used the solution to wipe cache, wipe user data, flash stock 5.1.1 rom again, wiped cache agian.
11. At first startup the recovery system lets me access sd-card content and I can select the update file but as soon as it is done and attempts to update, fails with dm-verity problem immediately, and dm-verity verification failed persist after any reboot or wipe until I reflash.
12. After multiple attempts to reflash kitkat problem still persist and with the locked bootloader I am at a loss as to what to do next to rectify the problem.
Any help or suggestions would be greatly appreciated. I hope I posted in the correct forum thread. Thanks agian in advance. -CM
Nobody has any advice for me
Lol, just checking back in agian. Nobody has any suggestions or similar experiences with a situation like this. Any feedback is appreciated. Thanks agian in advance. -CM
perplexive said:
Lol, just checking back in agian. Nobody has any suggestions or similar experiences with a situation like this. Any feedback is appreciated. Thanks agian in advance. -CM
Click to expand...
Click to collapse
I have thé same problèm . But i have thé bootloop After flash Rom.do you have thé solution of your situation? Help me with it if you have.t hank
that requires you to do some modification
don't try it
i know this may seem off topic
but can you help me with something?
Hello,
Initially, I was getting error 7 when attempting to update. However, after following the steps here, I'm getting an "Invalid zip file format!" error.
I haven't seen anything useful on how to fix it. These files are definitely not corrupted as I have accessed them on my PC.
Anyone have any ideas?
I was getting same error a lot, infact was not able to install any 3rd party APK also. What i did was complete reset and installed Stock 4.1.7 ROM/Recovery/Boot thereafter installed OB22 Modem+Firmware, then DM-Verity patch for OB22 and with this RR5.8.4 install was success. Please try as a short cut flashing: OB22 Modem+Firmware, then DM-Verity patch for OB22, then ROM and no Wipe to try update. Take full nandroid backup - best of luck.
Hello everyone,
I find myself with a big problem with my OP3T. Wanting to upgrade to the android 10 version of the Havoc rom, I got the E1001 error 7 message so impossible to install it.
Wanting to restore my old version (Havoc Pie), it doesn't boot once reinstall and sends me directly in Fastboot Mode.
Well then I decide to reset everything and reflash the rom under Pie and Error 7 too ... WTF!
I checked everything, my recovery is up to date, I have the latest firmware installed. I tried everything in vain, always this error 7 with any rom even the official one.
I don't know where this problem comes from but having spent about 10 hours looking for the solution, but nothing is solved
Need your help!!! thank you in advance :crying::crying::crying::crying:
Dear XDA-Developers,
After trying for many hours searching different forums and websites looking for help, I decided to make an account here and ask for help here.
I am currently on a Rooted OnePlus 5t with OxygenOs 9.0.3. I have not updated my phone in a really long time and decided to do so now.
I decided to dirty flash the full official ROM for OxygenOs 9.0.11 which was released recently with TWRP.
At first, I was on an older version of Blu_sparks recovery but replaced it with the newest TWRP from their website (Dumpling 3.3.1-0).
When I first tried to flash it, I got this error message:
failed: no space left on device
E1001: failed to update system image.
Updater process ended with ERROR 7:
Error installing zip file 'sdcard/download/Oneplus5Toxygen_43_OTA_054...
After trying multiple other recoveries, trying to flash with and without the compatibility zip and also trying to flash earlier versions of OxygenOS with different TWRP versions, I still get the same error message from TWRP as above.
Since it says that I supposedly don’t have enough free space, I looked for a way to change that and came across a thread which suggested to free some space by removing system apps that are not unnecessary, I tried doing that and flashing it again, but that also wasn’t successful.
My phone also has more than 10gb of free space.
I also tried to change the „assert“ line in the updater-script of the update, but I did not find any such line in the updater-script document in the zip file?
Does anyone know what causes this error message and what I can do to successfully update my phone?
And I was also wondering what would happen if I just let my phone regularly update it over settings?
It says that root is detected and my phone would be un-rooted once the after updating.
However, the update shown is only 1839mb so I’m very hesitant to do it.
But if I went through with this, would I just have to reroot my phone?
Will my recovery be replaced with the stock recovery, or will it remain TWRP?
Will my Bootloader get locked again?
Thank you so much for taking the time to read this, I appreciate it.
With kind regards,
Mutambo23
I would like to install a custom rom, but when trying I came across an error in the twrp saying that the zip was not compatible.
It's the first time I'm doing it, so I'd like some help to understand the whole process from the beginning, what I need to unlock before installing the rom and everything.
I'm on Android 10, ie binary 10.
Thank you for your attention in advance
DO NOT DO IT