Related
Hello All!
After power ON Vibrant have a message:
Android system recovery <2e>
Samsung Recovery Utils
- for BML -
reboot system now
reinstall pakages
delete all user data
delete cache data
update media, please wait
E:Can't mount /dev/block/mmcblk0p1 (or /dev/bloc
k/mmcblk0)
(Invalid argument)
E:copy_dbdata_media:Can't mount SDCARD:
copy default media content failed.
In download mode cannot enter. Try any combinations.
Odin see phone, but cannot upload nothing after START
Date of manufacture: 10/08
Via ADB reboot download only reboot, cannot entering download mode.
Please help me. Thank you.
you are in recovery, thing is update.zip isnt clockwork.
98classic said:
you are in recovery, thing is update.zip isnt clockwork.
Click to expand...
Click to collapse
And what to do? Have a idea?
pm me your email, i'll make it super easy for you.
edit nvm, i attached it. download, extract, make sure phone is good through usb and on, run the .bat it'll push cw to your phone and then just run "reinstall packages"
let me know if it worked.
98classic said:
pm me your email, i'll make it super easy for you.
edit nvm, i attached it. download, extract, make sure phone is good through usb and on, run the .bat it'll push cw to your phone and then just run "reinstall packages"
let me know if it worked.
Click to expand...
Click to collapse
D:\push_cw>adb push update.zip /sdcard/update.zip
* daemon not running. starting it now *
* daemon started successfully *
failed to copy 'update.zip' to '/sdcard/update.zip': Permission denied
hmmm, you arent mounting storage to pc right?
edit: works fine on my phone, wonder whats up with yours.
edit2: you can download a rom, rename it update.zip and drop it in that folder and it will push it to phone. basically it'll push anything named update.zip to your main sd
98classic said:
hmmm, you arent mounting storage to pc right?
edit: works fine on my phone, wonder whats up with yours.
edit2: you can download a rom, rename it update.zip and drop it in that folder and it will push it to phone. basically it'll push anything named update.zip to your main sd
Click to expand...
Click to collapse
I think that not have ROOT access to phone. Any idea?
maybe? root it http://forum.xda-developers.com/showthread.php?t=739300
I think this is solution can make if phone full worked. Bot now i have brick.
if it turns on it aint bricked
loading from SD-CARD
Have a solutions, that download system from SD-Card (memory card in a slot)?
for example:Format external Memory Card in EXT2, upload image of OS on SDcard, after loading phone from memory card and installing.
Really need recovery my bricked.
Thank you.
Hello!
I'm trying to find out where to see a list of parameters I can use in there.
I'm using the ClockworkMod recovery (even if I think it's just universal that part), but if I write in that cache file "boot-recovery --nandroid" nothing happens when I reboot into recovery, if I set just "--nandroid" it says "E: invalid arguments"...
What I want to achieve is to execute a nandroid backup and then one or more update zip files. Is it possible?
Thanks!
no one has any idea?
Hi
I have a problem i get this error : E:failed to mount /efs (Invalid argument)
and the /efs file is empty there is nothing there what do i have to do please help
and the other message i get is ( Factory mode is on )
and sometimes it register the network after some hours it got no service and after flash i got back my network it hapend many times.
Please help.
Click to expand...
Click to collapse
The Phone is Dead now !! anyone can help please
habab said:
Hi
I have a problem i get this error : E:failed to mount /efs (Invalid argument)
and the /efs file is empty there is nothing there what do i have to do please help
and the other message i get is ( Factory mode is on )
and sometimes it register the network after some hours it got no service and after flash i got back my network it hapend many times.
Please help.
Click to expand...
Click to collapse
Read this thread.
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
i didn't understand this
2- Create a file with a name 'factorymode' on the sdcard, open it, input 'ON' and then save it. Navigate to the efs folder, create the folder with a name 'FactoryApp' (case sensitive). Finally move the file 'factorymode' you have created above to that folder. Reboot the phone to see if the problem still persists?
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
i have tried that thread still have same problem .
Any help !?!?
..
fffft said:
I'm sure that you find this frustrating. However we are not psychic. Unless you tell us what led up to this and in particular, a step by step, detailed description of what you have tried, how can we discern going on?
What led up to this situation? What exactly have you tried? Step by step, in detail. What exactly is in your /efs folder? Did you create the /efs/FactoryApp/factorymode file as was suggested earlier? Do you have a backup of your /efs partition? Is reactivation lock disabled?
If you actually created the file in the manner described and it didn't succeed and barring something novel in a description of your situation the next step is probably to mount the /efs partition from recovery mode, format it, recreate the /efs folder, remount and reboot so that the efs is rebuilt. But before you do any of that, give us a better description of your situation.
.
Click to expand...
Click to collapse
Hi , i Downloaded a efs backup app and i just pressed on restore before i press on backup , after that the /efs file is empty . i tried to make ( /efs/FactoryApp/factorymode ) with this app : root browser but that didn't work...
i have tried to Flash with many stock room from sammobile but the /efs file still empty .
after reboot i have to connect to Wifi every time i reboot the phone and some time i have Network and some time nott .
..
yes i have backup of the efs ,
the app that i am using just named Root browser with black android pirate icon
.
i maked the directory ( FactoryApp ) then ( file factorymode on the root ) then moved it on FactoryApp , after reboot i find the file emptey again !
and i used this app ( http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325 ) for backup
..
1. i am sorry, my English is so bad !!
2. day 1 , i Downloaded the app Samsung tool and then maked a backup of EFS on External SD-Card ,
3. I maked restore and i had removed the SD-card
4. after that i didn't know that the efs file was damaged , i just installed an room from sammobile ( G900FXXU1ANG9_G900FNEE1ANG5_NEE ) , after the installation was done the phone started but i got an warning massage that says , FactoryMode is on and the wifi was off and only emergency call , i rebooted the phone the wifi was till of but i got back my Network after that i tried many firmware from sammobile
5. o searched on xda and find that it can be the efs but when opened the /efs it was empty.
6. i have the efs-backup on my sd i tried to restore it but nothing happened .
7. i tested that ( Opened this app : https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree ) maked /efs/FactoryApp/ and then file factorymode , ON ) but it can't be moved to FactoryApp when i move or copy it to the folder it is nott there , After rebooting the phone even the FactoryApp directory is deleted .
in my sdcard i found only this ( samsung tool/efs.img )
i tried to make this again
directory ( FactoryApp ) then ( file factorymode on the root ) then moved it on FactoryApp
Click to expand...
Click to collapse
After reastart phone screen is just black !! but the pc is finding it !!! now the phone is dead
..
No i can't boot to anything !! it is just black screen .
No i can't boot to anything !! it is just black screen .
please help me with that.
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
fffft said:
I'm sure that you find this frustrating. However we are not psychic. Unless you tell us what led up to this and in particular, a step by step, detailed description of what you have tried, how can we discern going on?
What led up to this situation? What exactly have you tried? Step by step, in detail. What exactly is in your /efs folder? Did you create the /efs/FactoryApp/factorymode file as was suggested earlier? Do you have a backup of your /efs partition? Is reactivation lock disabled?
If you actually created the file in the manner described and it didn't succeed and barring something novel in a description of your situation the next step is probably to mount the /efs partition from recovery mode, format it, recreate the /efs folder, remount and reboot so that the efs is rebuilt. But before you do any of that, give us a better description of your situation.
.
Click to expand...
Click to collapse
fffft said:
No problem and your patience is appreciated.
Nothing anomalous is showing up in those details so I think we can safely assume that accidentally pressing the restore button rather than backup button simply corrupted your efs partition. All of those questions were aimed at confirming that with certainty, but I understand that this is a lot of work and frustrating for you too. So we'll proceed on that basis.
An efs.img file is an uncompressed efs backup. So try restoring that with your efs program. I have no idea if it is a valid (working) backup, but you aren't going to cause any further harm by trying to restore it. If that works, great and you're done. If not, then we'll go on to rebuild your efs instead.
To rebuild your efs partition we need a custom recovery. So a few last questions.
You are rooted, correct?
Did you use Towel root or CF-autoroot? (I am trying to discern if you have super su /busybox installed)
Are you able to boot to recovery mode (home + power up + power)?
Do you have a custom recovery installed e.g. TWRP or CWM?
If you can answer yes to all four questions, then go ahead and run the following efs repair script. If not, then you'll need to install a custom recovery first. If you're already rooted but don't have TWRP, then it's just a matter of flashing TWRP with Odin from download mode.
In any event, once you have a custom recovery in place you can run this recovery script.
Download the script here. Copy it to your external SD card. Then boot to recovery mode and install the flashable zip file "Brick_Loop_FIX_afterRestoringBackup.zip" that you copied to your Ext SD card.
Then reboot. If you still have any issues, reboot a second time, then let us know if your phone is working properly again.
Credit to Backachu, I believe for saving me the work of having to write a script for you or describe how to enter the commands manually.
The script comes from this thread. http://forum.xda-developers.com/showthread.php?p=47014662
As an aside, there is a minor mystery there. This comes from a Note 3 thread so when I went to modify it to work with your S5, I found that it was already set up for the S5 rather than the Note 3.. so why it is that way in a Note 3 thread is a mystery. Go figure. But I did check and you can use it the way it is.
.
---------- Post added at 07:43 AM ---------- Previous post was at 07:36 AM ----------
I'm not sure what you mean by "dead". If you can boot to recovery & download mode, don't worry about it for now. Otherwise please elaborate.
.
Click to expand...
Click to collapse
..
fffft said:
Don't panic. I'm sure that we can address the new issue, whatever it is.
I need a little information to determine how to fix it.
I understood that your screen is black after you rebooted. What do you mean by the PC can find it. What message do you see on the PC.. the normal USB message when you connect your phone or something else? If something else, what is the exact message from the PC?
Also please do the following
Disconnect the USB cable and remove your battery from your phone for ten seconds. Then replace the battery.
Now press and keep holding the home button. Then press and hold the volume down button as well, then lastly the power button. Keep holding all three until the phone starts (about ten seconds).
Let me know if you do or don't get to the download mode screen when you do that.
If you don't, try it a second time, just in case you weren't continously holding all three keys to get into download mode.
If you still don't, then we want to ensure that the Kies program is not running (if you have Kies on your computer). Then try going to download mode again in the same manner as above, then plug the phone into your computer with the USB cable and start the Odin 3.09 program and tell me what you see on the Odin screen.
.
Click to expand...
Click to collapse
When i plug it in i get a news USB device named : ZUES Flash Device .
i have tried to Hold Home + Volume - + Power nothing happen.
Odin don't find it , and kies program is not running.
..
Hello everyone,
Please Help me to fix this issue
TWRP shows E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount internal storage
I have twrp v2.5
Actually, I am trying many solutions but nothing change
Hi, pal. I have the exactly same problem these days. On my opinion, when you have made wipe and wipe dalvik cache, you just deleted the system folder and data. I did same thing, now I'm stuck! :Д When you are trying to change the firmware, is the logo pictures changing for you every time you flash any other .zip file? We' are now complete lost man. Is your USB working like mine where PCs not detecting it? I think they've launched this kind of firmware only to destroy our device, so we can buy a new one. That's the idea. Go to the service and repair center of Lenovo and ask them for help! I wrote them down before a while, now I'm waiting for the response. We have left only two or three possibilities to flash the Rom with the Terminal in the Recovery. But if your PC recognizing the drivers, you will manage to flash the Stock 4.2.2 Rom with Flash tool , otherwise you are stuck too! I have no idea how to flash it. I can give you the terminal commands for you, which are hard to find, but you and me, we need the proper .img files for the flashing procedure. Go to the 4pda forum and ask for help, if you find any solution, come back here telling it and for me. There's a possibility, but it is difficult to create a proper .zip archive, because I only know that we need those folders and files: meta folder- updater-script, logo. bin, lk.bin, boot.img and system.img.
But when I insert the commands there, I don't know how the whole process must be working, something is happening there. The problem is that one of those lines did not work for me. Those are the commands for flashing any Rom with the terminal in the recovery. But first you must see if the PC is installing your drivers properly, open device manager and look for the drivers on the internet and try to install them. May be you have a working USB port, so there's no problem, just flash the stock rom with the Flash tool. But if it is not working as it is here, no other possibilities left, my boy! The only one left or two of them : Flashing the device either through fast boot mode or adb sideload, but you must install those drivers so PC can find the device. Well, you can always do this at your own risk from the terminal.
Oh, I forgot, those problem came when we deleted fstab file for our device.
Flashing firmware through the TWRP terminal commands:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p6 (for the memory ROW+ ) or
dd if=/external_sd/system.img of=/dev/block/mmcblk0p5 (for CN+ memory)
dd if=/external_sd/boot.img of=/dev/bootimg
dd if=/external_sd/lk.bin of=/dev/uboot
dd if=/external_sd/logo.bin of=/dev/logo
First, system.img must be converted to systemEXT4.img, then flashing it and you need to have a systemEXT4 in the .zip archive. But I think my system folder is deleted. :Д
simg2img /external_sd/system.img /external_sd/systemEXT4.img
Good luck to you! According to me there is a space after the dot and it must be like this: system. img, boot. img. But not sure!
Hi again. Tooday It occurred to me where our problem may be came with the tablets. When we flashed a custom Rom, we put it for the wrong MTK processor. Ours is MT8389, not 6589. The stock roms are too for the MT8389 according to me. We flashed a wrong Rom. Now the tab must be formatted somehow either through some commands from the terminal, or USB port and path to the USB must be repaired. Then, flashing with the Flash tools is our only option left! Sorry! );
They killed our device on purpose with the Custom rom. Do not flash them any more with such Roms.
Hi,
I've been using some custom Lineage with my S8 SM-G950F which worked for for a while and now I'm trying to get back to stock, usually its quite simple download the firmware from Sammobile and flash it with Odin.
I did it and it seem to work perfectly, download the latest version G950FXXSADTI1_G950FOXMADTI1_ITV, my phone is from Italy and bough directly from samsung.
I flashed with Odin 3.14 pointing the 4 files, used the CSC not the HOME one, clean everything, no errors.
I started to install things and after installed most of the stuff I try to add my Credit Cards to Google Pay and it does not let me do it and tell me it is a rooted phone and I could not do add credit cards.
Netflix doesn't even appear on PlayStore to donwload.
Everything works fine, I tried to reflash a couple of times with no success
Only thing strange is when I enter into recovery, it gives me some errors as bellow:
#fail to open recovery cause (no such file or directory)# --> the cause would be me holding keys while starting the phone I believe
Supported API: 3
e: unknow voulme for path [/odm]
e: unknow voulme for path [/vendor]
e: unknow voulme for path [/odm]
e: unknow voulme 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 /system/omc/SUP/
....some others similar lines
E:[libfs_mgr]is_dt_compatible() firmware info not valid : '/proc/device-tre/firmware/android/compatible: no such file or directory
IF someone can help me here, I appreciate
Solved, just closed the bootloader.. Silly of me to forget it
Thanks anyway.