Remove failed dir /system/carrier/att/priv-app/attiqi_att

First of all, thanks for this great community. I joined to share my Problem and hopefully add knowledge.

I have a S8+ with:

8.0.0/R16NW/G955FXXU3CRGB

#fail to open recovery_cause
File-Based OTA
Supported API: 3
Manuel Mode 1.0.0
remove failed dir /system/carrier/att/priv-app/AttIqi_att
RP SWREV B:3 K:2 S:2

I cant get any method to work to remove FRP or downgrade my S8+

My latest firmware should be:
Model SM-G955F
Model name Galaxy S8+
Country

Version Android 8.0.0
Changelist 13569719
Build date Fri, 25 May 7162 14:26:54 +0000
Security Patch Level 2018-05-01
Product code DBT
PDA G955FXXU2CRED
CSC G955FOXM2CREB

But somehow I messed up and got:

Model SM-G955FD
Model name Galaxy S8+
Country

Version Android 8.0.0
Changelist 13971786
Build date Mon, 16 Jul 2018 05:46:41 +0000
Security Patch Level 2018-07-01
Product code DBT
PDA G955FXXU3CRGB
CSC G955FOXM3CRG9

There must be someway to correct this issue? Ive tried all G955F Combo Roms

Which dont work because of the firmware issue?

Neither Odin nor Samsung pro Tools run clean, I end up with RP SWREV binary 3 2 1 device 3 2 1 errors.

I reckon I am missing something. Really annoyed by my mistake with the firmware.

I would be most thankful for shared experience and todo I didnt try yet.

I have got samsung galaxy a8 2018 device. I rooted my phone with this video: https://www.youtube.com/watch?v=uYYyxWH3xew Several days later I downloaded stock rom in sammobile. I flashed stock rom to my phone with odin (I didn't remove the magisk first, I mean I didn't run magisk_uninstaller.zip or didn't remove it via magisk app)but I choosed home_csc file and when flashing was completed, it rebooted itself and stuck on samsung page. I closed phone and went to recovery mode. After that, I wiped data with Wipe data/factory reset. Finally the phone was opened. Now, when I'm in odin mode, I see

current binary: samsung offical 
FRP lock: On
Oem lock: On

In recovery mode:

#Reboot Recovery Cause is [BL:Recovery Mode Set by key]#

Support SINGLE-SKU
File-Based OTA
Supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]

#MANUAL MODE v1.0.0#

remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or dictionary) Successfully generated dm-verity hash tree. E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible': No such file or dictionary

I can get OTA updates and the phone status in settings is Official. But I'm not sure if the magisk was completely removed. Maybe some files were left inside the phone. Or maybe it is running in the background. Please help me.

Thank you in advance

Note 8 flash firmware still getting same error.... - T-Mobile Samsung Galaxy Note 8 Questions & Answers

Hi I have the Note 8 and ever since the Oreo update my phone been acting funny my screen got darker the when I get a call I can slide the button on ls because it freezes the phone so I have to pull down notification bar and pick up from there also the sound got lower I did wipe cache partitions and nothing but I noticed at the bottom that it says:
fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
remove failed dir *‘/system/carrier/ATT/priv-app/AttIqi_ATT’ (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device or address
E: [libfs_mgr]Couldn’t get verity device number!
E: [libfs_mgr]Error removing device mapping: No such device or address
Successfully verified dmverity hash tree
So I used Odin to flash the firmware but when I checked I'm still getting the same error message please can someone tell me how to fix that I will really appreciate it very much

Is it a T-Mobile note 8 or AT&T note 8?
Sent from my God Mode 8

Same issue, fail to open recovery_cause...
Mine is from Xfinity / Galaxy S8 plus SM G955U
The problem in my phone is "not network connection" everything else works great maybe some problem with EFS I don't know I need help

Model Sm-n950u
Carrier Tmobile
Baseband N950USQS4CRE1

It looks like the firmware you are trying to flash is for AT&T. Make sure you get the t-mobile version ....S4CRE1...which should be the latest version bootloader 4
And try again
Sent from my God Mode 8

Related

Any update on the 'Network Error" during installation?

Searched around everywhere and the issue seems to be relatively widespread. During the Gear VR installation process, the install button becomes greyed out, stating "Network error occurred. Try again later."
Im using a Galaxy S7 Edge (G935F) stock ROM rooted +xposed.
I've tried editing the CSC file at /system/csc/sales_code.dat but this hasn't done anything!
I'd prefer not to wipe my phone and go through the hassle but if it that works (I've heard it doesn't) then I'll give it a shot.
Any help would be greatly appreciated, thanks!

I got the same problem after xposed installed on my G935T, when it was rooted and installed all work fine, but when i returned to stock rom (because the lag and big hot introduced by rooting it) GearVR never work again always with the wizard error "network problem" but i noticed that when i enter to the recovery and leave it, i get a red message "data mount problem invalid argument" i check xposed installer install.sh script and i notice that they mount /data storage in some lines maybe they change the way /data need to be mount so.. gearvr detect that data is wrong mounted and it avoid to be installed.. so.. im stuck on that weird problem.. and cant install gear vr now.

I figured it out! It's a problem with your phone's CSC version (Consumer Service Code)!
Flash your original CSC version (that should be compatible with Gear VR) using this tool - http://forum.xda-developers.com/s7-e...on-30-t3392957
If your variant is not available contact the Dev and he will add it upon request! Let me know how you go

Thanks you benno4678 for that solution!, it seems like is more than one solution for this problem hehe, well i fixed it.. i just take out the sim card and start the phone without it.. then i connect to an U.S vpn and everything works fine this time.. is like Oculus hate Cuba nahh.. seriously i think this is because I'm using t-mobile phone with TMB CSC in a different carrier like you said... but without sim card the phone din't show the carrier info so oculus installs works. Btw my operator don't have any CSC defined so.. my solution is the only one that work for me

Take the SIM card out and reboot. Install the software with the SIM card OUT. It worked for me.

No carrier data after Odin stock restore [NEED HELP]

Hi everyone,
Noob here. I was trying to sideload the 6.0 OS and was having issues. The after many attempts, the install worked...but then failed the installation. After this, on the bootloader screen, I was getting the error "dm-verity verification failed" which some posts recommended re-flashing a stock image onto it to fix this. So I looked for a stock image of 5.1.1 and found a guide on how to do this restore. All of this part went fine.
Except now, everything is working but no carrier data. I have phone calls, wifi, etc. I will try to give as much information as possible, please let me know if you're missing some information I can provide.
Model: SM-G920A
Baseband: G920AUCU3BOJ9
Kernel: 3.10.61-5527015 dpi#SWHD2407 #1 Sat Sep 19 11:08:32 KST 2015
Build #: LMY47X.G920AUCU3BOI2
SIM card status
Signal strength: -78dBm 62 asu
Network type: LTE
Service stats: In service
Roaming: Not roaming
Network state: Disconnected
The phone is offering a 103.30MB update right now. When I try to install it, it reboots the phone, shows the installation progress bar and fails (around 25% I think).
Can you please help me get back to a working state?

Yowza. You're on BOI2 (old) build with newest official base band (BOJ9).
I think your best bet is to use ODIN to flash BOJ7, then follow the instructions in the update to MM thread - side load to BOJ9 then PD5 then PD6.
Everything you need is linked in the OP of this thread.
http://forum.xda-developers.com/show....php?t=3371884
Sent from my SAMSUNG-SM-G920A using Tapatalk

Thanks for pointing me to that post. I started the flash in Odin with OJ7, putting all files in their proper field. The flash failed shortly after starting. Now the device says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software."
I installed and started the Smart Swtich software. The device is not listed in the Emergency Software Recovery list. I reinstalled the drivers a couple times, I can see the device in Device Manager and everything looks fine. How do I get out of this situation...
Every time I reboot the phone, it shows that same screen about the Emergency recovery.
Thanks

I could be wrong, but I don't think smart switch works for recovery on ATT models. Maybe take it to a best buy with Samsung store and see if they can get you up to full BOJ9?
Mucking around with Samsung software isn't my strongest suit - the s6 has been pretty locked down so I haven't played around much, and my last Sammy before it was an S2. Maybe someone more familiar can jump in.
Sent from my SAMSUNG-SM-G920A using Tapatalk

I got it to work. I used Odin to flash each file, one at a time (since one of them was causing an issue). 3 of them worked. I then sideloaded OJ9, then PD5. I have PD6 left, but I'm sure it'll go well.
Thanks for your help mate

HELP - "dm-verity verification failed..." recovery message and no cell service

Background Info:
Was rooted on OE2 via pingpongroot and supersu and froze some bloatware with Titanium Backup, nothing else done to the phone. Flashfire was on there but never used. Phone has worked fine this way for about 7 months.
This past Friday I suddenly lost all network connectivity and was very sporadic in connecting to the LTE network. Also lost ability to send text messages.
These are the steps I did:
1. Went to the ATT store, verified IMEI was ok, and got a new SIM card - nothing
2. Tried *#*#4636#*#* dialer code to see the network settings - nothing
3. *#0011# diagnostics dialer code - nothing
4. Tried different APN settings as well as APN reset - nothing
5. Factory reset - nothing (could not factory reset from UI, had to do it from recovery - "dm-verity verification failed..." message seen in recovery)
6. Removed pingpongroot app and uninstalled root via supersu, verified with rootchecker - nothing
7. Did another factory reset without root - nothing (could not factory reset from UI, had to do it from recovery - "dm-verity verification failed..." message seen in recovery)
8. Somehow the texting message center digit code was changed, so I did some googling and changed it back to +13123149810 from 313133127 - FIXED TEXT MESSAGING
9. Spent an hour with tech support verifying there were no network restrictions or limitations with my device - nothing
10. Attempted an OTA update on the phone - update failed (dm-verity verification failed.... message in recovery)
I didnt find too much on the dm-verity verification failed... message in recovery. It seems it has something to do with system files being modified, or something with the EFS. I cannot figure out what is going on with no network service, so an option is to either replace the phone under warranty from a service center, or to try and flash stock firmware via ODIN. Phone doesnt have knox tripped and says official under status, so I dont think I would have a problem replacing with them.
Questions:
1. Will "dm-verity verification failed..." cause issues with Odin and going back to stock recovery? Last thing I want is a brick when I could return it.
2. Can anyone think of anything else I could try in terms of trying to get my cell signal back? It connects to LTE in high populated places, but in places where it used to have fine reception (work, home) it gets nothings. This combined with the fact that my message center code was changed makes me think something deep in the network settings was also changed, but I have no idea where to look.
Thanks.

Do you still have frozen bloatware? You might want to try un freezing everything, and seeing if that helps. Perhaps you locked something up that's in need of an update / conflicting now.
AoN

Everything should be unfrozen after I did the factory reset, as I saw all of the ATT bloatware pop up again.

I am receiving reception again!
1. Odin back to stock. In this case it was OE2
2. Factory reset - this removed the "dm-verity verification failed..." message in recovery
3. Took the OTA update to OI2 ROM version
4. Factory Reset
5. Took the OTA update to OJ7 ROM version
6. Now have reception again in areas where it suddenly dropped off.
I do notice that my IMEISV number changed between OTA updates, and there are some extra network options in the secret dialer code menu. Not sure if that had anything to do with it, or the fact that I did not take any OTA updates since receiving the phone 7 months ago.
Anyway, hope this helps some people who may have suddenly lost reception in places they used to have it.

Sorry bro, as you installed the old program?

I believe it's because you are on Of4 firmware, but restored the oe2 files? To get back you need the flash the files in Odin from the muniz of4 update thread.
Nevermind, I see you updated already.

[Q] Can't mount /dev/block/st110 [Solved]

Hoping a kind soul can help a total fool who should have left well alone!
I have a UK Samsung Galaxy S I9000 phone that was unlocked by the previous owner but still had all the "3" branding which I wanted to remove. I was already on ver 2.2 (updated via Kies) although I don't know the exact revision.
After lots of reading (obviously not enough) I followed a guide to reflash via Odin v1.7 to I9000XWJS3 using separate files for PIT (803), PDA, PHONE and CSC. The guide said to tick Re-partition on which might have been the cause of my problem.
Needless to say after the flash, I got the error message "Can't mount /dev/block/st110" and subsequent reboots just give me a black screen. I still had access to the download mode so I tried another posts solution to fix the black screen starting with a flash to I9000XXJPC with a 512 pit and re-partition again. This time the odin process started but no progress bar materialised. After a very long while I disconnected. Thankfully I can still enter the download mode but this time am hoping someone with more knowledge is willing to help me though the process of recovering my phone if its still possible.
Just looking for any stock UK firmware and then I will let Kies update from now on.
Many Thanks
[Solved]
For those that want a quick summary of what restored my phone. Flashing I9000XXJPC with a 512 pit clicking re-partition.

You still can use xxjpc, with repartition ticked. Many a times, odin will fail for no reasons. Try again, but make sure you close Kies completely.
Sent from my GT-I9000 using XDA App

Thanks g00ndu. You gave me the courage to re-run xxjpc again by confirming I was on the right track and this time it worked. Small donation on its way for helping me recover my phone.
I have one further question though. Can someone confirm if the I9000XXJPC firmware is for the UK? I hope to only use Kies from now on but it now says "the version of the device cannot be updated". I am using the latest version 2.0.0.11014_49.
Thanks again
Edit - Kies lists the current firmware version as PDA:JPC / PHONE:JPC / CSC:JPC (KOR). Something tells me I have the wrong country firmware. If anyone can provide a link to the correct one and the Odin settings I should use it would be greatly appreciated.

Still trying to get a solution to this and have noticed that my product code in Kies registry entry is GT-I9000HKDKOR. I am wondering if this is because I used a wrong CSC file?
Any directions would be very welcome.
Thanks

Go to www.samfirmware.com and grab the Europe/UK firmware. Get a 2.2.1. one. All the CSC, Phone, Modem files should be in the package.

Thanks snapper.fishes. I am now downloading I9000XXJPU (512.Pit) - hopefully this one is correct as some of the downloads for 2.2.1 show (803.Pit). As there are no instructions with this I assume I don't click re-partition. Is this correct?
Thanks for the help

This is almost soul destroying....
I ran the update "I9000XXJPU (512.Pit)" as mentioned above and it flashed successfully. I am now on 2.2.1
Re-plugged in the usb cable and no windows popup to view the sd contents and nothing in "My Computer". Kies recognises something has been plugged in but remains on "connecting" - the phone itself shows the usb graphic and "connected".
I then went into Settings -> About Phone and there is no USB Settings option.
And just to rub it in I typed in *2767*4387264636# as per the wiki guide on here to view the Product code and it's still on Korea GT-I9000HKDKOR.
Edit - Have now tried *#1234# and the phone says:
PDA: I9000XXJPU
PHONE: I9000XXJPU
CSC: I9000OXAJPU
Not even sure if this bit helps

In case this is a help to other novices like me with the wrong product code. I found the following info and you don't need to be rooted to run it:
E.g. Changing CSC to XEU: Note - this will only work if the multiCSC was used when firmware was flashed
Type *#272*IMEI# and select XEU to install. (to check IMEI: *#06#)
Phone will reset to the default setting (perform a backup beforehand if req)
XEU = UK's product code
As for the USB issue (no USB Settings menu option in About Phone), is this just a change in the 2.2.1 menus? I noticed a USB Settings menu in "Wireless and network" and they have changed how this works. Kies still refuses to connect to the phone, but maybe this is just Kies.
Thanks

Jpu firmware is broken with kies. I think from memory that jpy and onwards allows that connection.
Jpu wasn't considered a official firmware but it worked incredibly well.bar the kies problem.
Sent from my GT-I9000 using XDA App

I'm getting the same error the op did.
What happened? I flashed CM7 and it worked fine. I then decided to do a restore with the backup I had made earlier with CWM, this is when **** went wrong. Couldn't boot up after this or get to recovery. Went into download mode and tried to reflash factory firmware. JL2 Andriod 2.2 for Bell Canada I9000. Says successful but just boots to 3e recovery with " /dev/block/st110, (Invalid argument), E:copy_dbdata_media:Can't mount DBDATA: "
Below that it says: " your storage not prepared yet. please use UI menu for format and reboot actions. copy default media content failed.
My biggest fear is the dreaded Int.SD card failure, the op gave me hope but same thing after every reflash.
Any suggestion?

I also have a Bell I9000M that did that. After attempting several combinations what ended up working for me was flashing JPU with 512.pit and repartition enabled, modem, PDA and CSC all selected in odin 1.3. That got me a working device. Then flashed JH2 to get recovery 2e back. Then flashed to the ROM I was originally on (Darky's 9.3). After that I flashed a CWM zip for the JL2 modem to get data back.
Sent from my GT-I9000 using XDA App

[Q] to place a call first turn off aeroplane mode

My phone has stopped working on the 3 network when I try to make a call I get the message "to place a call first turn off aeroplane mode"
I have reset the phone and still I have the same issue .
I have removed the sim and replaced it and I still have the same issue.
I have also removed the sim rebooted the phone and shutdown and reinserted the sim and I still have the same issue
The sim works in another phone.
The phone was on CM 11 and has recently upgraded to CM12 the phone has not been rooted or had any other ROM installed apart from the original one.
I can see the IMEI number
I have logged a call with One plus but really want to get the phone working again

Try clearing the cache from recovery. Failing that, re-flash the OS.

Try flashing some radios

Sorry for late reply I ahve been away and no phone means no internet
Thanks tried this and still the same
Thanks which radio do you suggest?

You can find the radios here http://forum.xda-developers.com/onep...ation-t2843675

I tried installing a radio form the link you provided
and I get this error
e: footer is wrong
e: signature verification failed
Installation aborted.

Did you switch to CM12 through OTA or if you did it manually then did you apply the firmware update?
And which modem did you use?

I manually did the firmware update and the radio was I tried XNPH44S radio

There's a separate update other than the ROM that should be flashed when going from KK to LP. Maybe flashing that would help

Can you tell me what this is as I am unaware of it

anyone?