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?
Related
Hi there, I'm desperately hoping someone can help me with this issue as I have trawled through Google for solutions to no avail
I've followed the tutorials from all the lovely people on these forums to get quite far into installing a custom rom for my HTC One X (XenonHD). Unfortunately I've been greeted with the "Decryption unsuccessful" error which I have discovered to be a very persistent error - where many people have many different solutions for it (none have worked for me ) I'm greeted with a password box, and no matter what I type into the box over 4 characters long it says:
Code:
Decryption unsuccessful.
The password you entered is correct**, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
<Reset Phone>
** - It says this regardless of what I type into the password box.
There was no important data on the phone (it's an old phone) so I'm more interested in just getting this custom rom up and running, it doesn't matter to me if I have to wipe data.
Here are the approximate steps I took to reach this position:
Set up bootloader/fastboot
Installed twrp
Wiped the device (cleared every cache etc.)
Copied XenonHD zip and gapps zip on to sd card
Flashed boot.img to the device
Rebooted - XenonHD spinning logo appears, then after about 30 seconds it asks me to enter the password, and I get the Decryption Unsuccessful error.
If you need any more information from me please just ask!
I am so appreciative of how helpful this forum has been to me so far, so I have really high hopes you guys can help me
Just a quick update: I actually managed to install a different rom using the exact same method that I did for Xenon - no signs of the decryption error whatsoever. I'm a noob at this stuff so I'm not really sure of the relevance of this but it sounds like it could be helpful in pointing towards a solution?
Ollie1700 said:
Just a quick update: I actually managed to install a different rom using the exact same method that I did for Xenon - no signs of the decryption error whatsoever. I'm a noob at this stuff so I'm not really sure of the relevance of this but it sounds like it could be helpful in pointing towards a solution?
Click to expand...
Click to collapse
Wich rom you install? The answare will help
I said in my original post which rom I was installing (XenonHD) - but I've actually managed to fix it!
To anyone else who stumbles upon this thread, if you are getting the decryption unsuccessful error you have to format your phone. In my case, it was a case of updating to the latest TWRP which includes a Format option on the wipe screen. This got rid of the encryption on my phone and I was able to use the rom!
Ollie1700 said:
I said in my original post which rom I was installing (XenonHD) - but I've actually managed to fix it!
To anyone else who stumbles upon this thread, if you are getting the decryption unsuccessful error you have to format your phone. In my case, it was a case of updating to the latest TWRP which includes a Format option on the wipe screen. This got rid of the encryption on my phone and I was able to use the rom!
Click to expand...
Click to collapse
Yes offcorce you migrate from old layout to the new leyout the roms for this two layouts are different
Hi there,
Apologies if this is something that has been asked a million times but I am a bit stuck with an update on my handset and I am not an expert on this kind of stuff. I wondered if anyone could advise further - I am trying to update my handset to the lollipop update and it fails around 25% of the way along. I have tried a factory reset already and when I do 'vol up and power' on the failure the error log reads -
L50QCT.01.102.010
Cleaning cache preload folder...
Verifying current system...
"/system/priv-app/Orange_Amazon_Kindle.apk" has unexpected contents.
Installation aborted.
Write host_mode:0 done.
The software update is 7.19.61.10 AKA the Lollipop update. The handset is not flashed with a custom ROM but the stock EE UK/HTC one.
I have already tried clearing the cache partition. Can you help please?
Thanks
You're in wrong forum mate.
Your device is M7 ... find the 7.19.61.10 RUU in M7 thread.
All you need is here : http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Any further question, ask there in M7 thread.. good luck
Hi guys,
I'm having trouble with my A2 Lite. Right after unboxing the phone I installed Magisk as described in the guide (https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626), which worked like a charm. Today, I wanted to install a OTA security update. After the update was downloaded I got an error and I remembered that I had to "uninstall" Magisk, as described in "step a" of the guide. So I did exactly as described in the guide. After Magisk was "uninstalled" I closed the app and tried again to install the OTA security ("step b") update. Unfortunately I got the same error message again ("Can't install update"). So I thought f*** it - I skipped "step b" and proceeded to "step c" and installed Magisk into an empty slot. After that I hit "reboot" and now my phone's in a bootloop :-/
bootloader is unlocked, oem unlock and debug usb are activated. I'm able to enter fastboot, but no recovery, whatsoever.
Is there any way to fix this?
just letting you guys know that "fastboot set_active b" did the trick. I don't know what the hell went wrong though. I did everything according to the guide, except for trying to update the ota update (and failing) before uninstalling Magisk.
Now, the phone is booting correctly, but I still can't install the ota update. it says "Couldn't update" and "Installation problem". What the heck...
lunatikk said:
just letting you guys know that "fastboot set_active b" did the trick. I don't know what the hell went wrong though. I did everything according to the guide, except for trying to update the ota update (and failing) before uninstalling Magisk.
Now, the phone is booting correctly, but I still can't install the ota update. it says "Couldn't update" and "Installation problem". What the heck...
Click to expand...
Click to collapse
This is probably due to the root as it modified the system partition. Check the thread regarding on how to update without losing root.
fake__knv said:
This is probably due to the root as it modified the system partition. Check the thread regarding on how to update without losing root.
Click to expand...
Click to collapse
Could you explain further? Will flashing the stock boot.img fix the issue and will I lose all data on the phone after flashing the boot.img?
thanks
lunatikk said:
Could you explain further? Will flashing the stock boot.img fix the issue and will I lose all data on the phone after flashing the boot.img?
thanks
Click to expand...
Click to collapse
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
BubuXP said:
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
Click to expand...
Click to collapse
Hi BubuXP
I followed your troubleshooting guide and flashed the boot.img as instructed. Flashing the boot.img didn't do the trick so I continued with flashing the system.img. I checked for the correct build no. of course and for both boot.img and system.img the active slot "b" was chosen. After flashing the system.img I got stuck at a bootloop. I tried to set the active slot to "a", but that didn't help either: Now it wasn't in a bootloop anymore, but it was stuck at the boot animation (horizontal beam) loading forever. After 10 minutes I tried to restart - still the same problem.
What's going on here??
edit:
I flashed daisy_global_images_V9.6.4.0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2 using MiFlash and the "Save user data" option. It was flashed successfully. However, when I start the phone it askes for a password and won't boot up into android if not entered. What the hell...? I deactivated my screenlock pin before I started all this. Is there a default password or what's the problem here?
regards
lunatikk said:
Hi BubuXP
I followed your troubleshooting guide and flashed the boot.img as instructed. Flashing the boot.img didn't do the trick so I continued with flashing the system.img. I checked for the correct build no. of course and for both boot.img and system.img the active slot "b" was chosen. After flashing the system.img I got stuck at a bootloop. I tried to set the active slot to "a", but that didn't help either: Now it wasn't in a bootloop anymore, but it was stuck at the boot animation (horizontal beam) loading forever. After 10 minutes I tried to restart - still the same problem.
What's going on here??
edit:
I flashed daisy_global_images_V9.6.4.0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2 using MiFlash and the "Save user data" option. It was flashed successfully. However, when I start the phone it askes for a password and won't boot up into android if not entered. What the hell...? I deactivated my screenlock pin before I started all this. Is there a default password or what's the problem here?
regards
Click to expand...
Click to collapse
Sorry, but I don't know anything about that. It's an encryption problem, and that's why I hate data encryption on the phone: my data is not so important to be protected when some hackers physically stole my phone, it's only a nuisance when things like this happens.
I can only suggest to change the active slot, maybe with this you can resolve.
I will also update my troubleshooting section of the rooting guide to make the data backup as the first option to be safe.
If you can sacrifice the data, you can simply format the data partition via fastboot or reflash using the flash_all.bat script.
BubuXP said:
Sorry, but I don't know anything about that. It's an encryption problem, and that's why I hate data encryption on the phone: my data is not so important to be protected when some hackers physically stole my phone, it's only a nuisance when things like this happens.
I can only suggest to change the active slot, maybe with this you can resolve.
I will also update my troubleshooting section of the rooting guide to make the data backup as the first option to be safe.
If you can sacrifice the data, you can simply format the data partition via fastboot or reflash using the flash_all.bat script.
Click to expand...
Click to collapse
I also thought that it had something to do with encryption. In the security menu, where I turned off the display lock, it said that the phone is encrypted. However neither pin nor fingerprint could unlock the phone.
I had to go for ultima ratio and flash my device with the newest fastboot image and miflash (save user data option didn't work either, btw.).
I lost all data on the device, but now everything works fine and the OTA update also ran through without any issues.
Now, I'm not sure if I will fiddle with magisk again. I really don't have no clue about what went wrong at all...
Thanks
lunatikk said:
I also thought that it had something to do with encryption. In the security menu, where I turned off the display lock, it said that the phone is encrypted. However neither pin nor fingerprint could unlock the phone.
I had to go for ultima ratio and flash my device with the newest fastboot image and miflash (save user data option didn't work either, btw.).
I lost all data on the device, but now everything works fine and the OTA update also ran through without any issues.
Now, I'm not sure if I will fiddle with magisk again. I really don't have no clue about what went wrong at all...
Thanks
Click to expand...
Click to collapse
Thanks for sharing.
Maybe something to try for next time to restore data, I don't know.
I haven't tested yet but I did make a backup using the method explained here
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
I have yet to try (or need) the restore function but running that backup created a 6gb file. My understanding is this is the majority of your apps, data, messages, etc
Without twrp I was hesitant to root but with the bit of knowledge and files shared here so far I have moved forward and glad I did. I haven't had to flash the stock image yet but hopefully this backup helps ease the pain. It is nice to be able to modify at will
BubuXP said:
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
Click to expand...
Click to collapse
Had the same problem. I tried to install the OTA of March, followed the guide to install OTA with Magisk, but after unistalling Magisk, i tried to install the OTA but it gave me this message "installazione riprenderà automaticamente quanto il dispositivo non sarà attivo";
I looked for some help online, but didn't find anything, so skipped to the point c, and i got this bootloop now.
I tried the "set_active b" command, but I'm still in bootloop. I tried to flash the stock rom but apparentrly it's impossible to do it without recovery (which I'm unable to open), so... Help?
EDIT: By using miFlash and using the flash_all command I flashed the most updated ROM I found on MIUI.en, which is the january's one. It worked, even if the build version (10.0.3) is different from the one I had previously (10.0.4). The system says that there's an available update, but i'm too afraid to try it. Suggestion are accepted!
Hello.
I was fiddling around with my phone today and wanted to clear the cache from the Recovery.
After rebooting tho it showed me a message (note that I never toggled OEM unlock or even accessed recovery/download mode or anything before today):
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
File Based OTA
Supported API: 3
MANUAL MODE v1.0.0#
Sucessfully verified dmverity hash tree
E:Failed to clear BCB message:failed to find /misc partition
Click to expand...
Click to collapse
And after a minute or so the Recovery showed up. I went to delete the cache, all went well until I was met with the same message at the end:
E:Failed to clear BCB message:failed to find /misc partition
Click to expand...
Click to collapse
Should I worry about anything ? The phone booted normally but I'm a bit skeptical about that error (maybe the cause of my as of late noticeable battery drain ?) and any help is appreciated!
EDIT: Another thing to notice is that when booting into recovery, it seems the phone is trying to install an update which isn't there, and only then takes me to the recovery menu.
Hir0xM said:
Hello.
I was fiddling around with my phone today and wanted to clear the cache from the Recovery.
After rebooting tho it showed me a message (note that I never toggled OEM unlock or even accessed recovery/download mode or anything before today):
And after a minute or so the Recovery showed up. I went to delete the cache, all went well until I was met with the same message at the end:
Should I worry about anything ? The phone booted normally but I'm a bit skeptical about that error (maybe the cause of my as of late noticeable battery drain ?) and any help is appreciated!
EDIT: Another thing to notice is that when booting into recovery, it seems the phone is trying to install an update which isn't there, and only then takes me to the recovery menu.
Click to expand...
Click to collapse
Everything you said I think is normal. So don't worry about it. It still clears cache or whatever you do.
SnowFuhrer said:
Everything you said I think is normal. So don't worry about it. It still clears cache or whatever you do.
Click to expand...
Click to collapse
I see, thank you
It's a weird bug so that's why I was worried. I did read some reports that some users couldn't wipe data due to this in the Recovery and it got me a bit worried.
Let's hope it's just a stupid bug and nothing more. Thanks again!
Hir0xM said:
I see, thank you
It's a weird bug so that's why I was worried. I did read some reports that some users couldn't wipe data due to this in the Recovery and it got me a bit worried.
Let's hope it's just a stupid bug and nothing more. Thanks again!
Click to expand...
Click to collapse
No problem. Report if it doesn't work.
SnowFuhrer said:
No problem. Report if it doesn't work.
Click to expand...
Click to collapse
Hi there
I have this issue. I cant factory reset the phone as it says MDM does not allow this.
so I used odion to reload the Stock Firmware on these but now I have FRP on this.
as it's a work device & dont know the user that last used this phone.
even after the flash I still have bcb message
Is there any other way of sorting this out.
UmangA said:
Hi there
I have this issue. I cant factory reset the phone as it says MDM does not allow this.
so I used odion to reload the Stock Firmware on these but now I have FRP on this.
as it's a work device & dont know the user that last used this phone.
even after the flash I still have bcb message
Is there any other way of sorting this out.
Click to expand...
Click to collapse
When you get into work phones, things get really ugly. Can you wipe data by flashing just csc in Odin?
Similar problem with S7, it just keeps rebooting
I have an S7, I have the same problem, the phone started freezing and rebooting every minute. So decided to Wipe out the cache and do factory reset, saw this message "E:Failed to clear BCB message:failed to find /misc partition"
The phone never goes past the Galaxy S7 Android logo screen most of the time, if it did manage to go pass, it freezes after 2 to 3 mins and reboots.
So I tried and successfully rooted, installed TWRP, took a backup and tried to wipe cache, it failed.
formatted the and tried to restore from backup and it failed, as it never went pass the S7 logo screen.
so I tried Lineage OS 17 and it worked like a charm
then tried back to Android 9 ROM from Samsung, it too started to hang and freeze - If it was an Hardware issue, I would expect Lineage OS to freeze too.
I think and it looks like Samsung is forcing its customers to buy new phones .....
Please help
thanks
Z
How to fix Galaxy J7 prime texting or calling issues: not receiving text or call aler
How to fix Galaxy J7 prime texting or calling issues: not receiving text or call alerts?
My phone is Samsung galaxy j7 prime
when I factory reset it show me this error E:Failed to clear BCB message: failed to open /dev/block/platform/13540000.dwmmc0/by-name/MISC: No such file or directory
Galaxy tab A 8
Even without appearing to have any hardware problems, my galaxy tab shows exactly the same messages described above and the same situations. I suspect it is even programmed obsolescence. Would anyone have any reliable tutorial on how to reset it completely and install a rom that was stable and compatible? Thank you :fingers-crossed::fingers-crossed:
Exactly the same problem
Hi guys,
I exactly do have the same problem. I upgraded from LineageOS 16 (which was working smooth.y ) to LineageOS 17.1 and faces a problem wit IMEI, So I tried to revert back to Stock ROM, flashed via ODIN latest version.
I could flash the stock ROM (doing NAND Eras and Re-Partition due to Vendor partition). But after reboot, the ROM won't boot and stuck with SAMSUNG screen blinking.. I managed to access the Stock Bootloader and could do a full factory reset, but I still get the error message like above.
If anyone has an idea how to solve...
My sister had many randomly chrashing apps and ask me how to fix it.
In recovery the same message was printed. BCB and /misc ...
Well I tried to clean install stock rom (A5 2017) with odin, but the user data was never deleted ... Don't know how to use odin ...
I have then flashed lineageos and now there are random reboots and apps are only crashing sometimes once opened.
I attached a crash log. The app crashin is called antennapod (https://play.google.com/store/apps/details?id=de.danoeh.antennapod&hl=de&gl=US)
Anyone knows what causing these? And if they are still related to BCB and/or /misc?
houston_ said:
I attached a crash log. The app crashin is called antennapod (https://play.google.com/store/apps/details?id=de.danoeh.antennapod&hl=de&gl=US)
Click to expand...
Click to collapse
Somehow tha attachment was delincined.
Log_2020-12-01_21-40-15.txt
drive.google.com
Hello, guys. I just ran into an error I had never seen before while flashing a new firmware on my T320. After searching around, I found more people have reported it as well on many devices and I've tried most solutions, to no avail.
When installing a zip for a lineage 16 rom, I got an error 7 message, which implies a mismatch between the rom and the device being flashed. I'm sure they should be a match, so I proceeded with the most common solution (when you know it's a match), which is to remove the device-checking code from within the zip. That didn't work, I got a "invalid zip file format" error.
I haven't tried many different roms after this in order to exclude the possibility this being actually a incompatibility issue but I'm worried because, when first flashing, I wiped the device quite carelessly. I'm afraid I might have "over-wiped" something important. I have TWRP installed, version 3.1.1.0, and did the wiping using it's built in tools.
Is there something I should never wipe, risking breaking it beyond repair? Is there a special procedure to perform or option to choose when zipping the rom back after removing the device-checking code?
Thanks for any advice,
Horácio.
horaciosalles said:
Hello, guys. I just ran into an error I had never seen before while flashing a new firmware on my T320. After searching around, I found more people have reported it as well on many devices and I've tried most solutions, to no avail.
When installing a zip for a lineage 16 rom, I got an error 7 message, which implies a mismatch between the rom and the device being flashed. I'm sure they should be a match, so I proceeded with the most common solution (when you know it's a match), which is to remove the device-checking code from within the zip. That didn't work, I got a "invalid zip file format" error.
I haven't tried many different roms after this in order to exclude the possibility this being actually a incompatibility issue but I'm worried because, when first flashing, I wiped the device quite carelessly. I'm afraid I might have "over-wiped" something important. I have TWRP installed, version 3.1.1.0, and did the wiping using it's built in tools.
Is there something I should never wipe, risking breaking it beyond repair? Is there a special procedure to perform or option to choose when zipping the rom back after removing the device-checking code?
Thanks for any advice,
Horácio.
Click to expand...
Click to collapse
A Slimroms file just made it through, so it's not destroyed, it's a matter of compatibility, somehow.
update the TWRP to 3.3.1.0
I have the same problem with T320 and was using TWRP 3.3.1.0, lineage-16.0-20191211-UNOFFICIAL-mondrianwifi.zip . I was able to install RR-N-v5.8.10-20190128-mondrianwifi-Unofficial.zip.
Any idea why?
Thanks
thro14 said:
I have the same problem with T320 and was using TWRP 3.3.1.0, lineage-16.0-20191211-UNOFFICIAL-mondrianwifi.zip . I was able to install RR-N-v5.8.10-20190128-mondrianwifi-Unofficial.zip.
Any idea why?
Thanks[/Q]
I got it working now. I downloaded 16.0 again. In TWRP- Factory reset, Advance wipe-chose Dalvick, Data, System & Cache.
This time I did not "Format Data". Not sure which did it (download or not format data).. Hope it helps.
Click to expand...
Click to collapse
having this same problem says "this package is for mandrainwifi , this device is . "
Trevorlay said:
having this same problem says "this package is for mandrainwifi , this device is . "
Click to expand...
Click to collapse
Make sure you have the latest twrp. If it still doesn't work, you could try messing with wiping/not wiping.