Database Develop

[Q] Galaxy S won't boot: can't mount sdcard, mmcblk0p2

Hey,
A friend gave me his Galaxy S after another friend of him got it into this following state (I'm not sure what exactly he did or tried to do):
The phone is stuck in a boot loop, sometimes it shows the first frame of the boot animation for a second before booting again. When I start it in recovery mode (Android System Recovery (3e)) I get this error messages:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
The phone does not have an SD card in it.
After reflashing with the same firmware as original, I get these errors:
Code:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions
meida files copy failed.
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
I've tried flashing different firmwares too, including rooted ones, and the results were the same except for a case where the first error was about not being about to mount mmcblk0p1 instead of sdcard, and another case where another firmware cause the phone to appear to boot, but after a minute or too it got stuck on a black screen and stopped responding.
I followed many different guides on how to fix similar problems, but none of them actually worked.
Please help, thanks a loooot in advance.

http://forum.xda-developers.com/showthread.php?t=1134975
Maybe it will help?

Thanks for the reply. Solutions 1-3 are irrelevant, as I can get into download mode, but even after flashing, any version, the problem is still there. I tried solution 4 (dbdata flash), but it doesn't solve anything. Are there any other partitions I can flash and might be able to solve this?

Ok, next thread
http://forum.xda-developers.com/showthread.php?t=1069867
Maybe here is solution?

Tried flashing the files there and no luck, still the same error. =/
I sent Faria, who said he has tools for solving this problem in that topic a PM, hopefully he'll share his tools with the community.
Meanwhile, I don't mind trying different solutions.
I also noticed something – if I keep the phone in the boot loop for a long time, it will eventually get to either a loop of the carrier boot animation (Which normally doesn't loop), or actually boot for one time. (When it booted I tried to power it off and see if it would boot again normally, and it didn't =/)

i have this kind of error few months ago, what i do was, flash pit file only with repartition, then flash pda, phone & csc.... agn flash this dbdata.rfs file, should fix the issue.

Just tried it, no luck, exactly the same error as before. =/

ops... sorry to heard that, at least it work for me but too bad not for u.....

I have the exact same error message and problem . Really hope someone can find a fix for this because I've spent hours and hours

Yep, EXACTLY same problem as OP and NO fixes for me yet. Tried everything from this thread and other threads. Let's see who's the real king of knowledge who can fix this.

any luck with this issue?

In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.

spamtrash said:
In my case it was solved by Click, but as in thread: for some people it works with repartition, while for some - without.
Or, try it Here I'd pay attention to page 2, Darky's resurrection... maybe looking for newer version at Darkyrom.
Click to expand...
Click to collapse
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.

ambrozic said:
thank you spamtrash.
i tried all this various methods. i was able to boot into android but after reboot, it never got into android anymore. stuck in boot loops. ill try Darky's resurrection now, its the last option i havent tried yet. i cant believe there are no scripts or smth to fix and rebuild file system in such cases.
Click to expand...
Click to collapse
Any Luck????????

I'd be interested with results as well. As last hope, you can try http://forum.xda-developers.com/showthread.php?t=1330491 this one, but it requires hardware mod...
Sent from tam-tam drum

any update or fix?
Someone found any fix for this?

Yep!
Hi guys!
Yep - probably I found the solution. One month ago I have bought i9000 with this problem (as broken). Finally I managed to start that SGS and even install ICS on it. The problem is (as I suppose) that internal flash memory is broken and You have to move /data partition to external SD card. So some flashes, some changes in files and repartitioning of SD card does the thing.
Currenty I am in the middle of preparing a tutorial to be pushed on YT to show how I managed to solve the problem. Stay tuned
Best regards

this is a hope.. =)=)=) please send me a tutorial. thanks

Ready
So.
Finally I had some time to add voice recording to my movie and volia - is ready.
I hope it will help at least somehow.
I am not sure if this manual will help in Your case(s), but it might be at least a hint
Best regards
Fteller.

^ So, umm, where's the link for your YT video? Thanks.

Error mounting data and cache

Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?

devbro said:
Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?
Click to expand...
Click to collapse
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean. I had a situtation where some things would not mount. data being one of them.. Not sure what else. Then I just mounted /system and everything was ok. Could it be that for some reason system is not getting mounted and you not formatting it besides an empty directory.

YayYouFixedIt said:
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean.
Click to expand...
Click to collapse
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.

devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
some corruption seems to have occurred.
perform a hard reset in the 'stock' recovery (this will format /data).
then boot in and re-setup. any userdata you had will be gone (including media/content stored locally, etc.).
in case of /system corruption (after performing the above; you still cannot boot in), you can format that partition separately and re-flash it from the CWM file for the latest posted stock update.
you can find file(s) on droidbasement, as needed.

I belive I have the same probleme, how i could i do it right?

devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
How did you try to format data in fastboot??
That's done in recovery afaik.
nero0345 said:
I belive I have the same probleme, how i could i do it right?
Click to expand...
Click to collapse
What problem do you have? /data not mounting? Format it in recovery but you will loose everything stored on your internal SD.

I finally took my tablet in for a check with asus. They said that I ahve corrupted my boot and since I replace the recovery there is no way to fix it. the only way to fix it is to replace the motherboard at this point. It will cost 190$ to replace!!!!

Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.

devbro said:
Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.
Click to expand...
Click to collapse
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...

berndblb said:
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...
Click to expand...
Click to collapse
When I talked to the tech at their center, there is apparently some special actions that only their recovery can do. These actions are those that allow changing boot table and other low level functions of the tablet which has nothing to do with the built-in memory or system files.
If I did not replace the recovery, then the repair by asus would have only cost 40$.

Another OnePlus 3T Bootloader Issue After SELinux -_-''

As most of you know that twrp takes a longer time to load on f2fs this is due to some bug but today we caught a new issue when I decided to unlock the bootloader and flash twrp to use lineageos o.o but but it got stuck at splash screen so I decided to go the #twrp for support at first they said it normal so I waited for an hour it was still stuck ? okay wtf ?
so lets investigate
Code:
<Dees_Troy> we're talking about the 3T, right?
<jcadduono> <11>[19700220_12:31:55.318574]@0 init: no such service 'qseecomd'
<jcadduono> WTTTTTTTTTTTTTF.
<jcadduono> that would certainly explain why its waiting forever
<jcadduono> oh i see
<jcadduono> androidboot.hardware=unknown
<jcadduono> your bootloader is not sending CMDLINE from aboot image
<Zenn> is this normal?
<Zenn> possible my bootloader is something new from oneplus?
<jcadduono> no, it is absolutely not
<jcadduono> flash 4.0.2 full OTA from twrp thread in oneplus stock recovery
jcadduono> maybe theres a fastboot command that enables/disables cmdline, try fastboot oem cmd_show
<jcadduono> and paste output on gist
<jcadduono> fastboot oem cmd_show
<Zenn> waiting for device
<jcadduono> you have to go into bootloader mode, ex. adb reboot bootloader
<Zenn> FAILED
while a temporary way was found to got me booting
Code:
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
if you encounter any issue please hope onto #twrp or contact @jcadduono
Code:
18<jcadduono18> i submit more question to oneplus on what flag causes this to happen and proper way to disable it
@Sultanxda @franciscofranco @koenkk @ujwal.p @apascual89

another issue to bring to light is when I previously thought there was an issue with Ext4 and recommended everyone to flash that fstype swap zip.
the issue experienced was the "reboot" buttons causing TWRP to crash and restart rather than reboot. this was actually due to the addition of the TWRP app installer!
this commit fixes it: https://gerrit.omnirom.org/#/c/21661/
as you can see, what's happening is that /data/app didn't exist on an empty data partition, and so the DIR* was NULL, but there was no NULL check before readdir was called on it. This caused a NULL ptr exception and crashed TWRP when looking for the TWRP app.
you can get past this by simply disabling the "ask to install twrp app" option in the settings page
there should not be any FS corruption, but that was a worry I had initially due to TWRP crashing from this problem and creating multiple sdcard mountpoints over each other. this issue should be fixed soon too...
credits to @mad-murdock for finding this one for me

I might need some assistance. (EVA-L19)

After unlocking the bootloader, installing TWRP recovery and rooting my phone with SuperSU (v2.82), I was preparing to install a custom ROM (more specifically the Resurrection Remix 7.1.2.) all in all, things ended up going out of hand and I accidentally deleted my internal storage, losing every single bit of my existing ROM, not to mention the RR ROM file as well. Now when I try to wipe, I can't, it usually says "Failed to mount '/data' (Device or resource busy) and "Unable to mount storage".
I tried using ADB sideload but to no success, only the same message. What I can understand is that the previous data is gone, I tried changing the format of data, system and cache to FAT & exFAT but it still did not resolve my issue.
I'm out of options here, I don't want to have to give up this phone because of my stupidity.
I also tried flashing the LineageOS 14.1 ROM to see if anything was different, here is what it said:
Installing zip file '/sideload.package.zip'
Target: HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B361:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
detected filesystem exfat for /dev/block/bootdevice/by-name/userdata
mount: failed to mount /dev/block/bootdevice/by-name/userdata at /data: Device or resource busy
unmount of /data failed; no such volume
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Script succeeded: result was [1.000000]
Although it said succeeded it clearly did not work and I am sitting without a ROM. I'm not smart when it comes to these things please help a guy out.
(Is there a way to going back to completely stock EMUI 5.0?)
Cheers.

EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros

zgfg said:
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
Click to expand...
Click to collapse
I know this is awkward to ask and all, but how exactly do I go about this, I'm pretty lost and I have minimal experience with this stuff..

I never had to use it but here is their portal (with download info, prices, instructions, etc)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)

zgfg said:
I never had to use it but here is their portal (with download info, prices, instructions, etc)
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
Click to expand...
Click to collapse
I'm terribly sorry for being THIS stupid. As I'm looking into this even more, I'm conflicted about the credit amount I need, been scrolling through the list and I can't really find my problem involving firmware I suppose.

People usually buy for 15 Euros. It may help you, Chrome will automatically translate from German
https://www.android-hilfe.de/forum/...-wiederherstellung-mit-dc-phoenix.818669.html

I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.

christopherpfister said:
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
Click to expand...
Click to collapse
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?

Hexagonal said:
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Click to expand...
Click to collapse
UPDATE: I flashed the stock recovery image and it showed me the wipe cache partition and factory data and system reset, I tried both, only the cache one succeeded, the other one failed. I saw a post that directed you to flash boot.img, recovery.img, recovery2.img and then system.img, I did that, but I couldn't boot into my phone - the good thing is however! That I can use my touchscreen in the recovery now.
Obviously the second time booting into EMUI recovery it prompts me to 'Download latest version and recovery', I try to connect to my Wi-Fi, seems okay but then it suddenly fails. More specifically it says 'Getting package info failed'. Save me please :crying:

So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.

christopherpfister said:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
Click to expand...
Click to collapse
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!

Hexagonal said:
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Click to expand...
Click to collapse
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.

Hexagonal said:
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Click to expand...
Click to collapse
Whats the error? Why doesn't it work? What happens when you try to boot?

christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
That's what I'm trying to figure out, when I try to boot in it's just stuck on a boot loop. Unfortunate..

Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?

christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
christopherpfister said:
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
Click to expand...
Click to collapse
I know, but it was flashing the Huawei logo and the unlocked bootloader warning continuously. It was set on EXT4 but as I was saying, it said script succeeded at 50%.

Hexagonal said:
'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Click to expand...
Click to collapse
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.

christopherpfister said:
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
Click to expand...
Click to collapse
I deliberately set the data partition to EXT4 before installing

Hexagonal said:
I deliberately set the data partition to EXT4 before installing
Click to expand...
Click to collapse
Can you check in TWRP if it actually says /data is ext4?
Which lineage are you trying to install? Don't you need a vendor.zip for some of them?

/data is indeed on EXT4, and I was installing the one that was on the room section.

Tate bricked - repair partition table?

My KFHD7 - Tate (PVT-08) has some trouble in the last time.
It stucks in a boot loop with the yellow Kindle logo.
I am able to reflash boot, bootloader and recovery via fastboot.
Then I normally was able to flash a system image after run recovery and can run this system once.
But after a reboot the bootloop exists again.
Now i'm able to start TWRP with the procedure described above.
The partitions cache, userdata and system always appear with 0kb. So I change the file system and change it back afterwards. Then the partition size is correct again and I can flash.
This time, however, I can no longer access the system partition.
If I try to change the file system I get the error message:
Code:
Failed to mount '/system' (Invalid argument)
Error changing file system.
A repair of the file system also fails:
Code:
Repairing system using e2fsck
/sbin/e2fsck -fp /dev/block/mmcblk0p11 process ended with ERROR: 8
Unable to repair system.
I suspect therefore (with my modest knowledge) problems with the partition table.
Maybe someone can upload me a flashable gpt.bin or something.
Or is a completely different method more suitable?
Many thanks in advance.

I have a working Tate. What exactly do you need? gpt.bin means nothing to me.
I can connect and provide a dd of something if you say precisely what you need.
In your position, I would first be asking how your partition table could have been altered. What do you suspect you may have done to change it? Unless you know you could have damaged it you may need to look elsewhere before possibly doing more damage by screwing around with the partition table.
Code:
Failed to mount '/system' (Invalid argument)
Error changing file system.
start by posting what you used as a command. No one can tell from the error what you did right/wrong
BTW how did you root the device, what version of Tate was it running before you did that?

First of all, thank you for someone's interest in the thread after such a long time.
Because of your question how to read out the gpt.bin I did some more research.
Now I actually managed to deblock the tablet!
For this I used the KFHD System.img Restore Tool. After that the problems with the system partition disappeared.
The thread is therefore solved for me and may help others in the same situation.
Thank you very much for your support!

Sylvan86 said:
First of all, thank you for someone's interest in the thread after such a long time.
Because of your question how to read out the gpt.bin I did some more research.
Now I actually managed to deblock the tablet!
For this I used the KFHD System.img Restore Tool. After that the problems with the system partition disappeared.
Thank you very much for your support!
Click to expand...
Click to collapse
I'm very pleased that my reply stimulated you to look again and got you a fixed tablet. The amount of support we get for these older tablets here seems less than minimal.
I have rooted mine but have not managed to install a recovery or fully regain control yet. I'll look at that tool you used. Do you know what Tate version you were running before , was it "up to date" ( ie sync'ed since 2014 ? ) . Mine has 7.5.1 and that seems to cut off a lot of options.
One thing I'm stuck on is booting into "recovery" mode. I have read that it is vol-up during boot but this does not seem to change anything for me, It just boots normally. If I do vol-down, I get "safe mode" but that's not much help.

Thanks for the link. I had looked at the before but was not sure if it applied to these devices, so did not want to risk it. It worked fine. One thing it forgets to tell you is to disable OTA updates. The first time I gave it wifi access it shot off without so much as a please and thank you and updated me back to 7.5.1 . So first thing to do is to kill updates:
Code:
su
cd /system/etc/security/
mv otacerts.zip otacerts.notazip