Database Info

[Q] Uscc Samsung Mesmerize stuck in recovery

I had just put CWM and Voodoo Lagfix on my phone, and it was working properly. (Except for the Market saying "Server error" and giving me a retry button every time I tried to open it) But then I did a factory reset because I was trying to get my Market to work, It would show the Samsung screen, then go straight to Android System Recovery. It wont let me navigate with the Volume buttons, or select anything with the Power button. But it will hide the text when I press the home button. Useless. Under the four options I can select, it reads:
E:failed to open /res/recovery.fstab (no such file or directory)
E:unkown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:Unkown volume for path [/data/fota]
#Manual Mode#
E:Unkown volume for path [/cache/recovery/recovery_kernal_log]
E:Can't mount /cache/recovery/recovery_kernal_log
E:copy_kernal_file : : Can't open /cache/recovery/recovery_kernal_log
E:unkown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unkown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Unkown volume for path [/cache recovery/command]
So far I've tried reflashing cwm recovery through odin, still wont work. I've been also trying to put stock android on my phone, but I can't figure out how to. I really like what I had before it crashed, so I want to try to use the same Kernal and Rom, hopefully without messing my phone up after it's fixed. So can anyone help me out? I may need with some detailed instructions or something, because I barely know what I'm doing, but I have some knowledge of it. Lol.

It took a lot of searching, but I ended up figuring out how to fix my phone, Megaupload being down made it harder than I wanted it to be, Lol.

Same thing happened to me. Care to help?

I'm going to assume you want to start all over...
You have to flash the patched version of Froyo in Odin with the repartition box checked.
Once you do that you will have a totally clean, stock phone.
If you ever think you bricked this unbrickable phone, just follow this easy step.
Here's EE19 (patched Froyo ROM):
http://db.tt/fyjLWiu0

Omggg.
Well. I already fixed it, but next time I mess up, I will definitely do that! Thanks for the help.

chad
same thing happend to me wont mount anthing the link wont let me dl anything off drop box says unautherized
---------- Post added at 02:43 PM ---------- Previous post was at 02:38 PM ----------
any help would be greatfull

Check out the Phone completely bricked(I dun goofed) thread as I posted a link to my dropbox w/ the ee19 stock file.
Sent from my PC36100 using Tapatalk 2

Emergency calls only (but valid IMEI)

Hi everyone, I'm in a particular situation. I bought an used J710MN but I forgot to check that the IMEI number that's under the battery matches with the one that appears in the software. It turns out that they didn't
BUT: Before I bought it, I made a test call and the phone was working OK. I had no problems.
After that I installed TWRP with Odin in order to root it. That's when the phone stopped working.
What I did:
I believed that the phone wasn't working because the physical IMEI is reported (I checked) so:
1. I flashed superSU and rooted the phone
2. I installed Xposed and IMEI changer and I set the IMEI of an old phone of mine, but nothing happens. In fact, although the physical IMEI is reported, the "soft IMEI" that the phone had initially was NOT reported and as I said, I tested the phone when at the moment I bought it.
Something must have changed when I installed TWRP.
Additional info:
1. I have NOT an EFS backup.
2. I currently have a VALID IMEI address (the one that I installed with IMEI changer)
3. In Settings -> About Device -> Status, I see the following:
IP Address: [shows an IP address]
Wi-Fi MAC address: [shows a valid MAC address]
Bluetooth address: Unavailable
Serial number: [shows an 11 characters length string]
4. In Settings -> About Device -> Status -> IMEI Information, I see the following:
IMEI: [shows a valid IMEI address]
IMEISV: 01
4. I can use wifi without problems
5. When I try to make an EFS backup from TWRP, I get the following:
Code:
[COLOR="Red"]Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.[/COLOR]
Updating partition details...
[COLOR="Red"]Failed to mount '/data' (Invalid argument)
Failed to mount '/cpefs' (Invalid argument)[/COLOR]
...done
[COLOR="Red"]Unable to mount storage
Failed to mount '/data' (Invalid argument)[/COLOR]
Full SELinux support is present.
[COLOR="Red"]Unable to mount /data/media/TWRP/.twrps[/COLOR]
MTP Enabled
Updating partition details...
[COLOR="Red"]Failed to mount '/data' (Invalid argument)
Failed to mount '/cpefs' (Invalid argument)[/COLOR]
...done
[COLOR="Red"]Unable to mount storage
Failed to mount '/data' (Invalid argument)[/COLOR]
Also I have a question: Could the carrier still know the physical IMEI number if the phone has a different IMEI number in software?
Thank you

I've got the same... after installing " twrp-3.1.1-0-j7xelte " on Galaxy J7 J710F/DS
well, I fixed it as far that only one ERROR is left: " Failed to mount '/cpefs' (Invalid argument) ".
for that installed " CF-Auto-Root-j7xelte-j7xeltexx-smj710f " with ODIN and then reinstall " twrp-3.1.1-0-j7xelte ".
But can't find any Info to this ERROR MESSAGE.
Acutually it is still not possible to install any ZIP with TWRP... no ROM, no SUPERSU, no MAGISK, no other RECOVERY
---------- Post added at 11:29 AM ---------- Previous post was at 11:13 AM ----------
HCFatLiveDE said:
I've got the same... after installing " twrp-3.1.1-0-j7xelte " on Galaxy J7 J710F/DS
...........
Acutually it is still not possible to install any ZIP with TWRP... no ROM, no SUPERSU, no MAGISK, no other RECOVERY
Click to expand...
Click to collapse
some more Info that might be important:
after install twrp-3.1.1-0-j7xelte (but before I wiped everything) the Stock-Rom made a ERROR MESSAGE when getting to the LockScreen (but interrupted by SIM PIN Input )
It said "device can not be started, integrity check failed" ... and that a factory reset is needed... I did it often, but always same ERROR.
Now trying to install custom ROM but twrp-3.1.1-0-j7xelte tell " Failed to mount '/cpefs' (Invalid argument) "

the little thinks
well, I have a J701F/DS .... thats why it did't work ....

Updated my Samsung J7 pro( SM-J730F) to Android 8.1 Oreo and the phone only shows emergency calls, Imei is okay, it just can't read the local network, tried searching network manually, just shows error, downgrading back to nougat still the same problem, tried patching with z3x pro tool , still the same issue, anyone to help please am desperate now.

flash G930UUEU4BQD2 on 930T - failed setting up dirty target

930T: on stock G930TUVU4BQH7.
use Odin3+v3.12+(PrinceComsy).
Flashing G930UUEU4BQD2 was "pass", then failed while installing the applications.
any help is appreciated. err mesg below and attached
--Installing package...
E: Failed setting up dirty target
[com-app-link] fail to mount /system as rwE: failed
successfully verify for dmverity hash tree
E: failed to stat (null)
E: failed to mount /system (Invalid argument)

Same problem here...still no solution.
Mine boots and is usable for a minute or two, but by the time I get an error that Samsung Cloud has stopped, the phone reboots.

yutaka001 said:
930T: on stock G930TUVU4BQH7.
use Odin3+v3.12+(PrinceComsy).
Flashing G930UUEU4BQD2 was "pass", then failed while installing the applications.
any help is appreciated. err mesg below and attached
--Installing package...
E: Failed setting up dirty target
[com-app-link] fail to mount /system as rwE: failed
successfully verify for dmverity hash tree
E: failed to stat (null)
E: failed to mount /system (Invalid argument)
Click to expand...
Click to collapse
did you ever figure anything out I got the same thing on my SM-G930P

MR G00DT1M3Z said:
did you ever figure anything out I got the same thing on my SM-G930P
Click to expand...
Click to collapse
You just gotta flash regular CSC and not home CSC. It will wipe your device but it fixes the problem.

unnecessarycomma said:
You just gotta flash regular CSC and not home CSC. It will wipe your device but it fixes the problem.
Click to expand...
Click to collapse
Thank you I figured that out by reading a little more. Hey do you know anything about how to sim unlock my sm-g930p ?

unnecessarycomma said:
You just gotta flash regular CSC and not home CSC. It will wipe your device but it fixes the problem.
Click to expand...
Click to collapse
I tried that before I read your post and it worked. Thank you!

adb sideload does not finish

I was following this tutorial wiki.lineageos.org/devices/walleye/install and I am stuck with sideloading Lineage
I run `adb sideload lineage-17.1-20201013-nightly-walleye-signed.zip` while phone shows "Starting ADB sideload feature" then comes "Installing zip file '/sideload/package.zip'" and then I can see the progress bar below moving, but nothing more, no percentage or more textes or whatever. And it does that now for multiple hours.
Before when I tried it, it stopped completely and the progress bar was frozen.
So I guess something is not working here?! I use Lineage from here, 20201013 download.lineageos.org/walleye

I even cannot push the zip to /sdcard
$ adb push lineage-17.1-20201013-nightly-walleye-signed.zip /sdcard
adb: error: failed to copy 'lineage-17.1-20201013-nightly-walleye-signed.zip' to '/sdcard/lineage-17.1-20201013-nightly-walleye-signed.zip': no response: Success
Click to expand...
Click to collapse

Maybe you can use twrp

armuttaqin said:
Maybe you can use twrp
Click to expand...
Click to collapse
In a way Iam using TWRP, like in the tutorial. So I start the adb sideloading within twrp, how else could i use it? So how can I put the zip onto the phone to use twrp install?

and when I did the format data wipe, I got the errors
failed to mount '/system' (invalid argument)
failed to mount '/vendor' (invalid argument)
Click to expand...
Click to collapse

ok I managed to install from OTG usb I again got the error about /vendor, and also "warning no OS installed" before I rebooted, but then I booted into LOS and it seems to work now....

Hi, just wondering if you have any specifics regarding the steps you followed for OTG USB install? I'm new here and I seem to be having a very similar issue with a newer version of the walleye build

Seriously could use help flashing custom ROM to Oneplus 8t (Tmo-variant) I am at my wit's end

Ok, first off let me say thank you in advance. I had the Oneplus 7t and (Tmo) and played hell with it trying to root until I found that MSMTool and then had a hayday with it. Now I have the 8t, I have been waiting for a working TWRP because I really like TWRP and I really like Magisk. As of yesterday my stock Rom was fully rooted with TWRP, Magisk, and busybox. It had been that way for several days with no glitches or errors, so obviously bootloader unlocked, phone is carrier unlocked and got my oneplus unlock token last tuesday (5 days ago). On my 7t after trying several ROM's I settled on Havoc-OS so with my 8t I was just going to go straight to Havoc-OS even thought I might try messing around with a kernel update at some point in the near future. BUT...... somehow I have angered the Android God's and am being punished. I have been through much frustration in the past with things Android, have always been able to figure it out thanks to XDA, but today I must humble myself, finally make an account and ask for help. To the best of my recollection here is what I have done with the results.
But before that my current state is, I can boot to TWRP recovery, fastboot, bootloader, EDL and all that but I wiped partitions prior to starting the flashing process so right now I can not boot to system.
I started at techsphinx.com/smartphones/install-havoc-os/ It is a very straighforward guide. but gave error 7, which I believe is wring device error so I checked and it's the kebab havoc like it should be (I think, I'll get to that in a moment) so I look it up and everything says to get in to the file and find the update binary and update script and edit the update script, blah blah EXCEPT that in my copy of havoc-os in the called out directory I have different files. Mine are otacert and metadata. two completely different scenarios. otacert is a binary file while metadata when opened with notepad gives this text:
ota-property-files=payload_metadata.bin:1784:116801,payload.bin:1784:1262105569,payload_properties.txt:1262107411:156,care_map.pb:737:1000,metadata:69:621
ota-required-cache=0
ota-streaming-property-files=payload.bin:1784:1262105569,payload_properties.txt:1262107411:156,care_map.pb:737:1000,metadata:69:621
ota-type=AB
post-build=OnePlus/havoc_kebab/OnePlus8T:11/RQ3A.210805.001.A1/eng.kshiti.20210826.065117:userdebug/release-keys
post-build-incremental=eng.kshiti.20210826.065117
post-sdk-level=30
post-security-patch-level=2021-08-05
post-timestamp=1629960471
pre-device=OnePlus8T,OnePlus9R
I can't remember when was supposed to be remarked in the updater-script file but there is nothing like that in this file. That is all that is present in this directory, META-INF/com/google/android
Everything I try to push to the device errors out before it completes with a broken pipe error, adb sideload is similar in that it won't finish the transfer to the phone. Now anything I try to do in TWRP gives me error can't mount partition_name. I had a nandroid backup but I can't use it because partitions can't be mounted.
I wondered if it was the tmobile variant thing so I tried the msm tool for switching tmobile to universal edition first but I can't get msm tool to work in my device manager the now soft-bricked device shows up as the QS BULK device which is not the right one so I install the automatic driver installer for the qualcomm usb drivers, no effect so I follow how to install manually and windows will not let me and tells me it's likely that the driver file is corrupt or has been tampered with.
My frustration level right now is just before the part where I take a hammer to the phone and make as many small pieces as I can.
The state of my phone right now is that I can't even get it into edl mode because I can't get it to turn off. reboot to power off, holding volume up and power both leave it to when I push both volumes in the screen comes on and I am in bootloader mode. I am at a complete and utter loss.
I need my phone for work tomorrow

@Frustrated_AF,
Regarding the QualComm device driver: I've attached my notes on how I installed the MSM Tool (including the QC driver) in case it's of any help to you. (@Unbrick Instructions.zip). Just note that my phone is a KB2000.
If you can get into bootloader mode, than you can flash TWRP. Get it from https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
And once you're in TWRP you can install the Havoc rom zip file using the instructions in post #2 in the TWRP thread. Get Havoc from https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/.
Note that the Havoc thread installation instructions were written before TWRP for the 8T was available. And, yes, I've installed Havoc using TWRP so I know it works.

BillGoss said:
@Frustrated_AF,
Regarding the QualComm device driver: I've attached my notes on how I installed the MSM Tool (including the QC driver) in case it's of any help to you. (@Unbrick Instructions.zip). Just note that my phone is a KB2000.
If you can get into bootloader mode, than you can flash TWRP. Get it from https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
And once you're in TWRP you can install the Havoc rom zip file using the instructions in post #2 in the TWRP thread. Get Havoc from https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/.
Note that the Havoc thread installation instructions were written before TWRP for the 8T was available. And, yes, I've installed Havoc using TWRP so I know it works.
Click to expand...
Click to collapse
Thank you, I have one issue (at least) that I can't find anything on in your instructions... I have been unable to install the usb drivers, on 2 different laptops one old one new one running windows and one running Linux with Windows in VMWare. same thing both times. I have tried the oneplus exe file, the qualcomm auto-installer andstlil show up as QUSB_BULK_ CID...... When I try to manually install by clicking on let me choose one Windows won't allow it. Windows says the file is possibly corrupted or tampered with. So I am unable to use any of the MSMTool versions I have tried.
Any ideas on that?
Cancel that. Please forgive me if I seem panicky if I can't get my phone working by tomorrow morning there will be hell to pay at work. So in your instructions where you write:
"If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ), extract the files, then install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you extracted the CAB file and selecting that directory."
I downloaded the file (brought back memories from doing my 7t) and extracted it to a folder on my desktop oddly enough without even updating the driver my edl mode device was detected correctly.
Working on the rest I'll get back to you shortly and once again I can't even begin to express my thanks!

@BillGoss Ok hopefully this will be the last question and it might be a dumb one but I'm not wanting to screw this up any more, In post #2 paragraph 2, bullet point 1 at https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
He states "sideload/flash ROM + installer" if I sideload the ROM it's going to install it, I don't see that the installer would go onto the device??? That URL is from the RECOVERY part of it from the ROM part of it at the URL https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/ under "installation" it describes a process of altering the RO M files payload.bin and then putting the pieces back together then using ROMinstaller.exe while phone is in fastboot mode.
Could you shine any light on this for me?

Frustrated_AF said:
@BillGoss Ok hopefully this will be the last question and it might be a dumb one but I'm not wanting to screw this up any more, In post #2 paragraph 2, bullet point 1 at https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
He states "sideload/flash ROM + installer" if I sideload the ROM it's going to install it, I don't see that the installer would go onto the device??? That URL is from the RECOVERY part of it from the ROM part of it at the URL https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/ under "installation" it describes a process of altering the RO M files payload.bin and then putting the pieces back together then using ROMinstaller.exe while phone is in fastboot mode.
Could you shine any light on this for me?
Click to expand...
Click to collapse
Like I said, the Havoc thread instructions relate to the pre-TWRP method. And I've never used that method.
The TWRP instructions say to sideload the rom and installer (TWRP installer zip) because installing the Havoc rom also installs a recovery, thereby replacing TWRP. That's why you need to reinstall TWRP after installing Havoc.

@BillGoss Thank you for your patience with this. I just assumed that learning what I learned when I did my 7t would transfer right on over to this and it would be simple... Haha. So now this... sideloading ROM at 47% from my powershell window it stops and says "adb: failed to read command: No error" On my device:
Flashing A/B zip to inactive slot A
step 1/2
step 2/2
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Updating partition details...
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
...done
Devices on super may not mount until rebooting
recovery.
To flash additional zips, please reboot recovery to
switch to the updated slot.
Leaving me clueless as to what has gone wrong or what to do about it. Any ideas on this one?
Edit; It worked! I did nothing else except rebooted it and it came up fine brand new havoc-os so far nothing at all wrong. I have no idea why all the failed to mount errors and I don't think I really care all that much it works!!! I'm going to flash twrp and magisk and be done for the night with it. @BillGoss I can't thank you enough. You have saved my bacon [email protected]!

Frustrated_AF said:
@BillGoss Thank you for your patience with this. I just assumed that learning what I learned when I did my 7t would transfer right on over to this and it would be simple... Haha. So now this... sideloading ROM at 47% from my powershell window it stops and says "adb: failed to read command: No error" On my device:
Flashing A/B zip to inactive slot A
step 1/2
step 2/2
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Updating partition details...
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
...done
Devices on super may not mount until rebooting
recovery.
To flash additional zips, please reboot recovery to
switch to the updated slot.
Leaving me clueless as to what has gone wrong or what to do about it. Any ideas on this one?
Edit; It worked! I did nothing else except rebooted it and it came up fine brand new havoc-os so far nothing at all wrong. I have no idea why all the failed to mount errors and I don't think I really care all that much it works!!! I'm going to flash twrp and magisk and be done for the night with it. @BillGoss I can't thank you enough. You have saved my bacon [email protected]!
Click to expand...
Click to collapse
Glad you're ok now. Those error messages are common when installing roms because those partitions (what used to be the system partition and is now a set of virtual partitions inside the physical super (sda15) partition) don't get properly setup until you reboot.
The 8T is a virtual A/B device which makes life more complicated than the old simple partition and straight A/B partition devices.