Database Develop

Help me troubleshoot my SDCard errors!

Hello,
Like many other users on this forum, I am having trouble with my i9000M sdcard after doing some ROM flashing.
Although there is some extensive threads collecting the different situations people are experiencing, I was hoping I could get some help for a specific circumstance relating to the sdcard issue.
I'll start by..
- Detailing the firmwares I have flashed, and what happened
- What is working / not working now, and how I got to get to the current situation
- And finally, I'll detail what I'm trying to do and where I'm getting stuck.
I would really appreciate some help with this, and thank anyone who takes the time to read it. I am trying to be very thorough to give you as much information as possible.
-----------------------------------------------------------------------------
1. Started with stock firmware. I am not sure what it was.. I believe the phone is equivalent to the Bell i9000M, but I am on the SaskTel carrier.
2. Flashed firmware I9000XXJP2: This worked, and I was using Froyo 2.2 fine.
3. Tried to root Froyo 2.2 firmware: This FAILED and the trouble began. I was using the update.zip method, and the source claimed it was compatible with 2.2. I had to hard reboot the phone, but it would stall on the white text intro screen (not the animated one).
4. Went into Download mode. Tried to flash firmware I9000UGJH2 (apparently the most current bell firmware), using Odin v1.1. This FAILED, and I had to hard reboot, which resulted in the PHONE - ! - PC error. I am aware the i9000M can still be recovered from this state.
NOTE: I could do nothing at this point: all firmware flashes failed, UNTIL I CHANGED TO ODIN V 1.3!
Using Odin v.1.3:
5. Flashed a series of firmwares.. (I9000UGJG8, I9000XXJM1, I9000XWJG5), ALL resulted in the phone either being in a shutdown-boot loop to the white Glaxaxy text screen, or the battery charging screen.
I could enter Download mode to reflash, but NOT recovery mode.
6. The ONLY semi working firmware is I9000XXJP2, Samsung Froyo 2.2. This is what the phone is now.
- I CAN enter Download mode, Recovery mode, and the phone stalls on the white Galaxy boot screen, but goes no further, and does not restart.
- I CAN run abd commands
Here is the output I get from each of the options in the Recovery mode:
Code:
I9000XXJP2
Odin 1.3
512.pit
Flashes fine
Goes into recovery mode
Displays error:
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
copy default media content failed.
Try to format sdcard:
Formatting SDCARD:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
ensure_root_path_unmounted It's not mounted
update media, please wait
E:Can't mount /dev/block/mmcb1k0p1
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
Try to wipe cache partition:
-- Wiping cache...
Formatting CACHE:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/cache)
ensure_root_path_unmounted ret 0
unmount (/cache) attempt 1 (Unknown error: 0)Cache wipe complete.
Try to apply sdcard:update.zip
Same errors as 1) can't mount sdcard therefor installation fails.
Reboot system:
- Will accept adb download reboot
note: I can reach download mode using the button combination
- recovery mode: can access with button combination or 'adb reboot recovery'
- power off: battery charging indicator shows
note: it does not loop the battery indicator
- power on: stalls at Galaxy S GT-19000 white lettering screen.
note: i recieve an indication on windows desktop that a device has been connected which is capable of USB high speed point
ADB COMMANDS WORKS: device is detected
Things I have tried:
I tried booting into a Ubuntu Live cd to see if I could format the sdcard, as suggested in this thread: (sorry, forum won't allow me to hyperlink, thread id=759910)
The disk utility picked up the Samsung drives (One was labeled something like Samsung_Galaxy, and the other Samsung_Galaxy sdcard, but I'm not 100%) but could not format them. There was also no info being listed about the size.
Things I would like to try / have hunches on:
Before all this happened, I made a Nandroid backup of the orriginal firmware, and copied it from the i9000's sdcard to my computer. I made the backup using Rom Manager's Clockworkmod.
Is there a way to use Odin to flash Clockworkmod, so I can restore this backup?
-everything out there says to use Rom Manager, which I can't access because the phone is pseudo dead.
Will the backup even still be on my sdcard?
Wait, my sdcard isn't mounted.. can we try mounting it with abd? (I tried, but am not sure of the command / path of how to do this..
Can abd be used to restore my backup stored on my computer? Is this dependent on the sdcard being mounted?
I fully appreaciate those you take the time to read through this as it is rather lengthy. I just want to ensure I have tried every means to revive the device, and hopefully some more skilled users can help with the mounting and adb syntax.
All comments and ideas are welcome and appreciated! Thank-you

Sorry to be the bearer of bad news. But time and time again this error has proven to be a hardware error. Mine did the same thing and samsung/bell had to replace the mainboard in my phone. Good luck, but unfortunately, anything you do further is a waste of time short of sending it back for repair.

Stuck on glowing Samsung logo

Hello!
This post might be a bit lengthy as I try to explain in detail what happened. Sorry for that!
I already read the posts suggested upon entering the title on this one, but I could not find a solution for my problem....
Three days ago, my P1000 (non-rooted, GB via Kies) froze. I turned it off (by pressing Power for a few seconds).
I turned it on again. It booted, but reached only the Samsung logo and would stay there forever.
I turned it off again, removed the external SD and did the factory reset (via Power+VolUp).
It did the reset, but the problem of the glowing logo remains.
I started to google a lot, and got acquainted with Odin, (Stock)ROMs, tar files, PIT files, etc.
but I could only gain a vague idea of all these things as I lack a deeper background knowledge.
So I downloaded several (Stock ) ROMS and PIT Files and tried to flash them on the P1000 using Odin.
The last combination was GB-Stock-Safe-v5.tar together with gt-p1000_mr.pit, recommended as being a good way to "re-stock" the P1000, which I tried to flash with Odin (repartition checked, since having a PIT file). It almost worked but movinand.mst failed. So I removed it from the tar file and tried again.
This time the hidden.rfs failed. So I removed it as well from the tar file. Then the flashing succeeded (but without the movinand.mst and the hidden.rfs)
And the problem remains.
When going into Android recovery mode <3e>, it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
csc : deleting /system/csc
csc : done
Successfully installed package.
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
-- Updating application
E:failed to mount /preload (No such file or directory)
E:install_application_for_customer:Can't mount /preload
your storage not prepared yet. please use UI menu for format and reboot actions.
copy application failed.
-- Applying Muli-CSC...
Installing Multi-CSC
Can't access to '/system/csc/DBT/system/'
Successfully applied multi-CSC.
Maybe I have now what is called a "soft-bricked" P1000? My P1000 can only go into recovery mode and into download mode (and into "glowing logo" mode).
I would be grateful for any help so that I can bring the P1000 back to normal life...
Thanks in advance.
Larry

Huawei P10 Lite, TWRP Error 9, pls HALP

Hello everyone,
My phone is in what it seems to be erecovery loop, I tried flashing images via fastboot extracted from update.app file, didnt work at all.My phone is unlocked, I flashed twrp again and downloaded latest stockrom version for my country(asked a friend about it since he has the same phone), I put those 3 files on my usb and connected it to my phone.Opened it in twrp, when i try to flash update.zip i get Error 9.I tried pretty much anyting i could find on this forum and other sources from google, nothing rly seems to work and there isnt anything at all for error 9.Do u guys by any chanse know what is the problem here?
device: Huawei P10 Lite WAS-LX1C432B194 (latest version for my country, Serbia, Eu)
phone unlocked, twrp installed, can do fastboot commands
This is what i get when trying to flash that update.zip
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Formatting Cache using make_ext4fs...
Wiping data without wiping /data/media ...
Done.
Updating partition details...
...done
Installing zip file '/usbotg/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: Success
script succeeded:resut was []
check_write_data_to_partition,write data error
[COLOR="Red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from
zip failed
[COLOR="red"]Updater process ended with ERROR: 9
Error installing zip file '/usbotg/update.zip'[/COLOR]
Updating partition details...
...done

There is already a thread for this problem: https://forum.xda-developers.com/mate-7/help/softbricked-device-fix-t3159742/page5

LwannaCM said:
There is already a thread for this problem: https://forum.xda-developers.com/mate-7/help/softbricked-device-fix-t3159742/page5
Click to expand...
Click to collapse
I already firgued it out, but tnx for the response.
I bought sd card(didnt have one), did dload method, since normal one approach didnt work i used force update approach(dload moved to sd card, power off, hold vol+ + vol- + power button and it installed) also i needed to flash stock recovery beforehand(so it removes twrp, used fastboot to do it, phone was unlocked, power off connect to PC via usb cable and hold down vol- right away, then flash it through fastboot), it cant do force update with twrp still installed.Once it was done i normally booted to stock rom, phone was no longer unlocked, now i unlocked it flashed twrp and rooted it, everything works just fine.Hope it helps some1 with the same problem.
source: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 , there is guide thing for both normal and force update

Thank for the help. It gives me a clue but I am still struggling as the force update approach get stuck at 5%. Thanks anyway.

NOTE 8 sm n950f firmware error problems

i have a note 8 sm n950 i done the android update a few months ago and and it got my phone stuck in a boot loop, i installed new firmware which i was able to use the phone again but lost data signal, i fixed that but now my calls and text are coming through with a german number (im in the UK) i have tried to install stock firmware using odin and keep getting sw rev check fail device 11 binary 6 (and other variations of that error) i have also tried clearing the cache and wiping the phone from the boot menu but no luck, could anyone help, i would be very grateful

Have you check that you have downloaded and installed the correct version of the OS on your device?

pazler said:
i have a note 8 sm n950 i done the android update a few months ago and and it got my phone stuck in a boot loop, i installed new firmware which i was able to use the phone again but lost data signal, i fixed that but now my calls and text are coming through with a german number (im in the UK) i have tried to install stock firmware using odin and keep getting sw rev check fail device 11 binary 6 (and other variations of that error) i have also tried clearing the cache and wiping the phone from the boot menu but no luck, could anyone help, i would be very grateful
Click to expand...
Click to collapse
The binary error you are getting is because you are trying to flash older filmware than what is already on the phone., this is not possible because of security updates. Downloading the latest filmware for you device should resolve this error, and then hopefully fix the other errors you face.

stonedpsycho said:
The binary error you are getting is because you are trying to flash older filmware than what is already on the phone., this is not possible because of security updates. Downloading the latest filmware for you device should resolve this error, and then hopefully fix the other errors you face.
Click to expand...
Click to collapse
im pretty sure i have tried the latest one for my phone, as i have tried many others but i was never 100% certain it was, could you point me in the direction of one?

pazler said:
im pretty sure i have tried the latest one for my phone, as i have tried many others but i was never 100% certain it was, could you point me in the direction of one?
Click to expand...
Click to collapse
In post number 2 in the thread below, you can install "samfirm" on your Pc, this will give you the latest update to download, at a fast speed. For region (on samfirm) put your service provider, ie BTU or XEU for the UK.
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072

stonedpsycho said:
In post number 2 in the thread below, you can install "samfirm" on your Pc, this will give you the latest update to download, at a fast speed. For region (on samfirm) put your service provider, ie BTU or XEU for the UK.
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
Click to expand...
Click to collapse
seems to of worked fine, no problems yet, thank you!

pazler said:
seems to of worked fine, no problems yet, thank you!
Click to expand...
Click to collapse
Glad to hear :highfive:

stonedpsycho said:
Glad to hear :highfive:
Click to expand...
Click to collapse
sooooo.... it was working fine for a couple days then the phone froze with a glitched horizontal line on the screen, i rebooted the phone and thought nothing more of it. A day later did the same thing (different place in the screen this time) i have wiped the cache a few time times but it hasnt improved. It is also freezing on the samsung loading screen and or getting stuck in a boot loop, the phone does work normaly for short amounts of time (few hours or so) but keeps happening, i managed to copy this log from the recovery menu if any help
p.s this is simlar to the original problem i was having before i changed the firmware
fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
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 directory)
can't open directory '/sytem/omc/SUP/ect/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory

pazler said:
sooooo.... it was working fine for a couple days then the phone froze with a glitched horizontal line on the screen, i rebooted the phone and thought nothing more of it. A day later did the same thing (different place in the screen this time) i have wiped the cache a few time times but it hasnt improved. It is also freezing on the samsung loading screen and or getting stuck in a boot loop, the phone does work normaly for short amounts of time (few hours or so) but keeps happening, i managed to copy this log from the recovery menu if any help
p.s this is simlar to the original problem i was having before i changed the firmware
fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
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 directory)
can't open directory '/sytem/omc/SUP/ect/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
Click to expand...
Click to collapse
This is beyond my knowledge. I would take a guess that you have some sort of hardware issue as flashing stock filmware usually resolves any software bug. Hopefully someone who has faced the same or someone more knowledgeable will be able to help you further.

HI Experts i am getting the same issue in my note 8 sm-n950f according to my knowledge i lost its efs and baseband partition by mistake and my phone now stuck on Galaxy Logo now the OEM System is locked by default i am not able to flash TWRP please Suggest me how can i recover pretty phone back in Normal Condition :crying:

mehroz1234 said:
HI Experts i am getting the same issue in my note 8 sm-n950f according to my knowledge i lost its efs and baseband partition by mistake and my phone now stuck on Galaxy Logo now the OEM System is locked by default i am not able to flash TWRP please Suggest me how can i recover pretty phone back in Normal Condition :crying:
Click to expand...
Click to collapse
As we have said many of times before, if you lost your EFS folder and you never made a backup of it then you're screwed and you'll need to send it to Samsung for repair because you can't use anyone else's EFS because the EFS holds your IMEI and the phones serial numbers and such. It's information that's never supposed to be removed or deleted.. However someone else said if you delete certain stuff in the EFS folder and then reflash it that it would work and I tried this method and it failed to work so I don't know any other way except sending it to Samsung repair facility.. It also requires root access which you obviously can't do since it's OEM is not unlocked so I really doubt there's anything you can do short of sending it to Samsung..
https://forum.xda-developers.com/ga...i-detect-sim-card-t4134733/page2#post83127549
This is the link but like I said this didn't work for me..

Failed to mount /system || failed to verify whole file signature || signature verification failed

Hello,
first of all thank you for this forum...
I have an old Samsung J3 2016. The device was very slow so I decided to try to install a custom rom, but I did something I hadn't to do! I even can't explain what's happening.
Some infos:
the device should be in debug mode
OEM unlocked
I have downloaded the original pit file using Heimdall
I flashed something ( I even can't recall what I have done) and now the device doesn't boot properly
I can put it in download mode (volume down + power button + ....)
I can put it in the other condition (?) (volume up + ...)
I have a PC running Linux Mint 20
I can connect the device to my PC through Heimdall but if I try to flash ROM I get errors*
I can connect the device to my PC through "JODIN3 Casual" but if I try to flash something JOdin tells me that my PIT file is corrupted and if I try to ask JOdin to make a custom pit file it tells me to restart the device. The device restarts and JOdin doesn't see it.
Error when I try to flash something or update from external storage: see file attached.
WHAT CAN I DO??
Pardon my bad english and the lack of infos due to my poor knowledge