Hi, I was wondering if anyone can help me.
My tablet is unable to mount my /efs directory, or whatever. And while I don't know if they are directly connected,
things like my lock screen, holding my power button to get options like Flight Mode, Data Network, Restart, Etc., is gone. And I have tried screen lock to work, it doesn't. Holding my power button shuts my tablet down (in the same amount of
time that holding it would normally bring up the options screen, as well). I also loose completely my 3g, no matter wish successfully installed rom I run. I am not new to flashing rom at all and navigate trough all kind of step regarding specifics to rom by heart. All I can remember was to try the latest Android 4.1.1 - CyanogenMod 10 Preview and failed to load it, I was stuck in the boot animation for half an hour. So I decide to go back to the new stuck 4.0.4 from my provider. That is where I found the problem. Since, I have try 4.0.4 stuck, 4.04 rooted. The problem occur the same way in every rom and everything else was juste fine. I try the 3.1 stuck and 3.2 stuck and the message E: failed to mount /efs appear when rebooting from odin install.Never been able to load any version of the latest 4.1.1 from pershot. I have found a thread about the same issues from another device http://forum.xda-developers.com/showthread.php?t=1766748. I pass the entire day reading the web for solution, but no cigars so far.
I have the a Telus samsung galaxy tab 10.1 3g.
Thanks in advance if you have any idea how to resolve the /efs mounting problem.
I will added these picture to show that I have lost all important information that is apparently store in some file inside this /efs folder. Apparently this folder as been corrupt when flashing the CyanogenMod 10 Preview especially made for my tablet. So my new question would be to ask.
Do anyone know how to restore this folder even if I have no backup of it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
on off on off
try to copy the content of the efs folder with any root browser. it will have files and folders like in the screenshot atached.
Solved.
i had exactly the same problem. Was working on it for the last two days (ofcourse i am a simpleton and rookie )
But yes at last the phone is fixed and working fine with all the parameters.
So dont worry dear. Try to follow these steps : -
1. flash a rom using odin or heimdall - either stock or Cyanogenmod. You can check the repartition if using with the pit file.
2. Root your phone if not already rooted
3. Install busybox
4. Install kTool.apk (Its a small and wonderful apk. Freely available)
5. Install any file manager that supports root browsing
6. Make a backup of your efs with the help of kTool.apk (Its simple)
7. Decompress your earlier backup and copy all the files in the root efs folder with the root explorer
8. Now rename the one that you decompressed the files from as efs.img and copy it into the internal sdcard root
9. Now retore the egs.img using the kTool.apk
This will solve the problem i guess.
Good luck
8.
No file in /efs folder, and no backup
Thanks a lot for the answer guys, but unfortunately there is nothing inside my /efs folder. It's completely empty and therefore I can't copy it, move it backup it,or anything. I also have no backup of this folder. As I understand some file in this folder contain the super important information of my own system like IEME, Serial, etc... So my concern is more like is there is a way to restore this folder even if it doesn't exist. I think the answer is no and the only solution for me is to send it back to Samsung with the stuck roms from my provider and hope for them to not deny the repair so I won't have to pay. I wonder if there is other thing to do but I am pretty sure not. If someone know something let me know. I have already contact Samsung and tell them that my 3g is broken and some strange behavior occur during OTA update. They are going to send me something for me to send the tablet for reparation. Til then I really want to know if there is something I don't understand and if there is still hope. Anyway thanks in advance for anyone who know better then me.
This is EXACTLY what's going on with my tablet, and yes, there's nothing to copy. What do we do?
I originally edited my old post with this, but I wanted to be sure the OP saw it.
I finally fixed mine. See my thread at http://forum.xda-developers.com/showthread.php?t=1876260
I hope it helps
Related
Just wondering if anybody has had this issue before. I searched around a bit but haven't found a clear answer yet. After flashing a kernel through Kernel Manager Pro, the phone rebooted, checked sdcard as usual, then popped up that there was an error and sdcard was mounted as "read only". I had made a backup right before flashing the kernel like I usually do so I restored that backup but got the same error. I booted into recovery and wiped data and cache and so on and rebooted into android. No luck with that either, so I tried a backup of a different rom I had. Still the same issue (also wiped between restoring backups for good measure). Plugging it into the computer would work because it would not recognize the sdcard as a removable drive (had the "use as disk drive" option chose on my phone to clarify). Finally I had to boot into recovery, mount usb storage, right click on the drive that my phone was, and click "check and fix for errors". After a very long wait it finished and I unmounted usb storage and rebooted into android again. That finally fixed it (whew), and now I have a folder on my sdcard that is titled "FOUND.0000", and there are text files in it with names such as "FOUND.0000CHK, FOUND.0001CHK" and so on. Do I need these files anymore or is just showing me what was wrong and fixed on my sdcard? Will it cause any issues if I delete the folder? Sorry if all this is confusing or stupid. I just have never had an issue like this before and I have rooted and used quite a few android phones and tablets. Im not a noob but I definitely do not know that much about this kind of stuff so any help would be greatly appreciated! TIA
Travis
TMYINC said:
Just wondering if anybody has had this issue before. I searched around a bit but haven't found a clear answer yet. After flashing a kernel through Kernel Manager Pro, the phone rebooted, checked sdcard as usual, then popped up that there was an error and sdcard was mounted as "read only". I had made a backup right before flashing the kernel like I usually do so I restored that backup but got the same error. I booted into recovery and wiped data and cache and so on and rebooted into android. No luck with that either, so I tried a backup of a different rom I had. Still the same issue (also wiped between restoring backups for good measure). Plugging it into the computer would work because it would not recognize the sdcard as a removable drive (had the "use as disk drive" option chose on my phone to clarify). Finally I had to boot into recovery, mount usb storage, right click on the drive that my phone was, and click "check and fix for errors". After a very long wait it finished and I unmounted usb storage and rebooted into android again. That finally fixed it (whew), and now I have a folder on my sdcard that is titled "FOUND.0000", and there are text files in it with names such as "FOUND.0000CHK, FOUND.0001CHK" and so on. Do I need these files anymore or is just showing me what was wrong and fixed on my sdcard? Will it cause any issues if I delete the folder? Sorry if all this is confusing or stupid. I just have never had an issue like this before and I have rooted and used quite a few android phones and tablets. Im not a noob but I definitely do not know that much about this kind of stuff so any help would be greatly appreciated! TIA
Travis
Click to expand...
Click to collapse
This is very interesting. I've never had a problem with the SD card. Is this the same SD card that shipped with the phone?
When you, "right click on the drive that my phone was, and click "check and fix for errors" is that a windows command? Does the picture below represent the action you took?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you end up deleting those files? If so, what happened?
I am having some weird errors with my SDcard myself. I went from a flashed kernel on CM7 off to another ROM. Rebooted and SDcard errors out the wazoo. I am getting MD5 mismatches on a lot of my backups at that. If I can get a ROM that fully boots, I will likely wipe the sdcard and start over to see if it isn't from a corrupt file or something.
The same exact thing happened to me. I mounted my SD card from recovery and windows auto fixed it.
If that didn't work I was going to wipe backup. wipe, and reformat.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Link: http://goo.im/roms/mattlgroff/Blur_Version.651.167.3370.XT910.AmericaMovil.en.01.zip
MD5: FAF583BA8E5BE1D1EAC10C0BF775BAF0
Mattlgroff's Notes:
Upgraded CDT.bin, so no going back to GB after this.
Android 4.0.4 ICS - "AMXLA/XT910_MOTO_AMXLA/umts_spyder:4.0.4/6.7.2-180_SLC-34/1340677325:user/release-keys"
HOW TO ROOT: http://goo.im/apps/mattlgroff/DroidRazrRoot404.zip ---- Run the batch file in this. Be connected via USB (MTP Mode recommended), and have USB Debugging Enabled (Settings>Developer Options)
If you have Superuser left over and root is failing use this: http://rombot.droidhive.com/ROMs/spyder/ROOT/DroidRazrRoot404(IfYouAlreadyHaveSuperUser).zip
Build Date 26/6/2012
How to install from another ICS leak (same carrier, model, etc.):
Put the leak on your external SD card.
Fastboot a patched boot.img using the boot.img.p from this leak's /patch/ folder and the boot.img from the latest official version's fastboot files. (See my thread on patching boot images here: http://forum.xda-developers.com/showthread.php?p=27211509 )
NOTE: If someone posts a reply with a boot.img they patched, you can use that one as well. Only one person has to make one and post it.
Fastboot the system.img and preinstall.img from the latest official version
Boot to recovery and install the newer ICS leak.
Must be on 651.167.3370.XT910.AmericaMovil.en.01 stock rooted to install.
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Be on STOCK 651.167.3370.XT910.AmericaMovil.en.01. No frozen apps. No custom recoveries, etc.
Install instructions are using ES File Manager and Rom Manager (free) from the Play Store download these and be rooted on 651.167.3370.XT910.AmericaMovil.en.01.
open rom manager free, hit OK, now press the home button.
open es file explorer, press YES, press menu, open settings, scroll down to Path settings and under Root settings: Enable
Up to Root (path settings)
Root Explorer (root settings)
Mount File System (root settings)
"DOWNLOAD THE ICS UPDATE ZIP AND PLACE INTO YOUR PHONES /CACHE DIRECTORY (not /system/cache, but in the root of the phone)"
open ES FILE EXPLORER, locate your /cache directory and then select the Blur_Version.651.167.3370.XT910.AmericaMovil.en.01.zip
(now choose Open With ROM MANAGER)
phone will restart, and begin installation of the ICS leak (takes 10-15minutes)
phone restarts, boot animation begins, Android is upgrading :: Profit success!! Celebrate!!!
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Oh! This I want!
woohooo... aqui voy!!!
After Rooting and installing this rom, it showed the CLARO logo, then started doing the "android is upgrading" counting the apps... but after that it froze on starting applications... don't know how to unfreeze it or restart it... There is no way to do a battery pull, so can anyone help????
I managed to reset it, and it booted, but...
No Sound and it drained the battery pretty fast...
Gonna do a Factory reset to reinstall all the apps to see if that resolves this...
You should definitely just do a factory reset, along with wiping your caches from Recovery. I wonder how many people complaining of ICS issues just never did a factory reset in fact...with such a huge OS change, there's no way I would trust it just "upgrading" what was installed. I just got my unlocked RAZR and went straight from fresh Gingerbread with nothing installed to this Claro ICS, and immediately upon booting I got force closes from Google's own apps. A factory reset along with wiping the caches fixed it up. Loving it so far, only really noticeable problem I've had is the widget selection screen having each widget's name whited out, but other than that, it's been stable and solid. Battery life has been pretty great as well, easily hit 15 hours of nearly non-stop screen usage to set everything back up before it said to plug in the charger. In regular usage I can see myself going 2-3 days.
The problem as I have stated in other threads is that the battery is not charging and it wont let me do a FR... Something went very fubar and stiil don't know how to fix it... and I'nm still reading... a lot...
Waiting for someone kind enough to give a try from the retail BR ICS version to move to this one and post instructions on how to.
Edit: After a lot of reading and getting scared a couple of times, patched my own boot.img
Download here
After updating I waited for the new system to boot and rebooted to recovery to master reset, works like a charm.
Thanks juanfers! Needed that file to upgrade from the Brazil leak!
Update...
I managed to make it charge, but still I notice the battery goes very fast... I saw that there is a script for taht or something. Can anyone point me to the correct download?
Honestly, i don't know why you guys didn't use the LATAM Retail version, is the best rom for our phones, and is not full of all the claro crap
Does anyone know when ics ota is coming to Puerto Rico for our razr
hi, i write for a web page called QiiBO.com, we want to feature this rom/update to help our readers upgrade their phone, if anyone here is so kind to write a guide, we will feature you, your twitter or your name, thanking you for your help. Thanks, and you can contact me thru [email protected]
Hi!
Story goes like this. I have here clone Samsung S4 that I wanted to update the software trough CWM. Unfortunately phone died at some point and now is dead. But, I made backup of the flash with MTKDroidTools and with SP flash tool... and here comes the problems... I can not flash backup back to phone because yaffs2 files are not good page/spare ratio. Thanks to members rua1 and Alex1948 now it is more clear how to change spare ratio on yaffs2 files. Unfortunately I'm not very good with Linux, last night I boot Mint 16 from USB stick and was trying to repair my files but without success.
So, my question is: is someone willing to repair my files in Linux (who understand Linux terminal better)?
Here are some details from phone
View attachment 2574910
View attachment 2574911
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I only have problem with flashing yaffs2 files and secro.img all other are OK. If I try to flash those files I get this error
In attachment is mtd, dumchar_info, MTKDroidTools log and Sp flash tool log so you can see my file structure.Log from MTKDroidTools is from version 2.5.2 because I was using this version when I was making backup from my original phone (you will see other phones data just scroll down to MT6575)
I'm uploading original yaffs files to google drive so later I will update this post with some links.
Thank you all in advance.
Best regards
P.S. INFO FROM MTKDroidTools IS TAKEN FROM SAME PHONE LIKE MINE (FRIENDS PHONE) YES, SAME ONE HARDWARE AND SOFTWARE IS 100% SAME.
Files on Google drive link
https://drive.google.com/file/d/0Bx8Xjd1q6dr3YnFISVJBZFZPSUU/edit?usp=sharing
Little update (memory type)
View attachment 2575196
from guide:
Аttention! Yaffs2 type blocks from this backup can't be Downloaded to phone, they aren't correct! Use backup on 9th step if phone have yaffs2 type blocks!
Click to expand...
Click to collapse
files from archive is wrong
from your log:
10/02/14 11:43:23 Free space: system- 113.7M; data- 54.3M; sdcard- 16.7M; D:\ 170861M
10/02/14 11:43:46 - ERROR - tar: write error: No space left on device
Click to expand...
Click to collapse
it was necessary to release the free memory on SD card before
Hi!
First, thank you for your reply.
Yes , I did figure it out that my files are not OK. I was trying to make them manually in "yafey" for windows (software to create and edit yaffs2 images) but this software have to much bugs so one time it create system.img with full lib folder second time only half of lib files are there and also there is no option for spare ratio change.
So, MTKDroidTools did make my system backup in a folder on my PC but I can not make yaffs2 file from it because there is no software for windows that works fine (I don't use Linux). On Linux it is easy to do (at least for someone who understand Terminal commands).
So, I can send you my backuped system folder if you are willing to make yassf2 file from it (in Linux). Data and Cashe files I have create in yafey and thay are ok.
In yafey if I make new yaffs2 file and insert lib,etc,app,framework... it will not create all files in folders... and after that when I try to flash that created system.yaffs2.img I have error from BROM s_ft_readlen_not_page_aligment (4017) again problem with spare ratio.
I still have here my friends phone so if you have any idea what to do and how to do please tell. I made backup from my friends phone but same thing data,cache,system,secro files are not created correctly. I don't know why is this is it because of the MTKDroiTools or is it because of the phone?
Aaaaaaaaaarghh!!!!!
You wouldn't beleive what I just discover I just try to put my friends phone in recovery so I give a try to make backup.
NORMALY my friends phone don't want to go in recovery (just light on screen), so I have call my friend to ask him does he do something with phones recovery and he said YES i flash some recovery from net trough CWM and after that he can not go in the recovery.
CAN YOU BELEIVE HOW UNLUCKY I AM????????
If someone have any idea???
I am hoping someone here is able to help me as my problem is doing my nut in.
Our puppy tried to taste my phone the other week so I had to replace the entire front screen ( glass and LCD ). The replacement phone had an issue where it wouldn't detect any sim cards at all ( I had no IMEI number, baseband or anything ). So i took my working motherboard ( I knew it was working as I could still ring it while it was in the old phone ) and replaced the mainboard in the replacement phone.
When I first put it together and turned it on everything came up as normal but somehow my IMEI had been corrupted. I dont know how but somehow I have managed to partially get it back.
When I installed my last ROM ( OMEGA V58 ) I created an EFS.tar back up which I kept on my SD card. This is it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I still have that sat there but no matter what I am unable to restore it. I have tried to copy it over from the SD card file by file, I have even tried to use EPS expert but I cant figure out how.
Could some one please please give me some clues or a point to a simple guide that I could use before I turn the oven onto gas mark 6 and stick my head in
Blackwatch said:
I am hoping someone here is able to help me as my problem is doing my nut in.
Our puppy tried to taste my phone the other week so I had to replace the entire front screen ( glass and LCD ). The replacement phone had an issue where it wouldn't detect any sim cards at all ( I had no IMEI number, baseband or anything ). So i took my working motherboard ( I knew it was working as I could still ring it while it was in the old phone ) and replaced the mainboard in the replacement phone.
When I first put it together and turned it on everything came up as normal but somehow my IMEI had been corrupted. I dont know how but somehow I have managed to partially get it back.
When I installed my last ROM ( OMEGA V58 ) I created an EFS.tar back up which I kept on my SD card. This is it
I still have that sat there but no matter what I am unable to restore it. I have tried to copy it over from the SD card file by file, I have even tried to use EPS expert but I cant figure out how.
Could some one please please give me some clues or a point to a simple guide that I could use before I turn the oven onto gas mark 6 and stick my head in
Click to expand...
Click to collapse
Efs backups in .tar format can be restored with Odin,SGSIII EFS backup / Restore,Philz recovery and other tools are you sure that the file above is in .tar format because screenshot say's different.Also if you copy manually you have to set all the permissions of the files to the same as what is is currently in your phones efs folder.
I have a RAR file on my phones SD car that is called EFS.tar
I have tried to install it using Philz but it says it cant find it even though I have but it in the clockworkmods/backup directory. In case I have ballsed things up in the EFS directory where would I get a list of the permissions so I can send everything over manually and use ES explorer root to manually set the permissions.
Blackwatch said:
I have a RAR file on my phones SD car that is called EFS.tar
I have tried to install it using Philz but it says it cant find it even though I have but it in the clockworkmods/backup directory. In case I have ballsed things up in the EFS directory where would I get a list of the permissions so I can send everything over manually and use ES explorer root to manually set the permissions.
Click to expand...
Click to collapse
Put the tar file in root of internal sdcard or memory card and select it from recovery (like when you install a ROM).
Yes that's the file I would try like @RazorMC said or just flash it with odin or try this >> http://forum.xda-developers.com/galaxy-s3/general/tool-backup-restore-efs-imei-sgsiii-t1901098 <<
I would probably backup your current efs ( even though it is corrupt) just in case anything goes wrong
It would have been better if OP had continued the discussion in the original thread.
It has a better chance of solutions since members can see the full history of the issue.
Mod Edit
Thread Closed - Please see [Q] Urgent EFS help please
ronnie498
Forum Moderator
My fellows and friends,
One of these days, I received an update from LineageOS and when installing it from OTA ( using TWRP ), the first lines ( about 10 to 15 ) from the istallation sequence activities were all red, showing that something went wrong. Immediately I removed the batery to stop the process and installed the first version of the custom rom, using the TWRP. It worked fine and I received some notifications about the new revisions of the rom. I skipped the one that caused problems and accepetd the download the one on the Nov, 17, 2018 of the rom, and had installed. It appeared to me that everything was ok but, one day I turned the phone off during thje night. The next morning, I tryed to boot the phone without success. It started an infinite loop situation..... So, I tryed to repeat the same procedure to install the very first version of the rom using TWRP at the recovery mode. When I was using the TWRP to perform the advanced wipe, the dalvik cache, data and system could not be wiped. The answer about the problem was shown as : failed to mount /efes ( inavlid argument ).
I got the information that, in cases like that, the stock rom should be installed. I downloaded it from www.stockrom.net and had it istalled with the use of Odin. Unfortunately, the boot loop was there again.
What was worse now was that no TWRP was installed and Odin could not recognize the phone, although I had installed the newest set of drivers from Samsung, applicable to any devices from them.
Please I need your help to see if there is a possible solution to solve this case. Phone Model: GT-i9300 SSN -I9300GSMH - in Brazil
The message I got from the phone: E: failed to mount /efes ( inavlid argument )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thank you in advance any help from you guys,
Gilberto Leite
Flashing a stock ROM will always replace TWRP with the stock recovery.
Are you trying to flash the latest stock ROM?
Do you have a backup of the EFS directory? It's an important directory as that is where a lot of information, including the IMEI is stored.
Hi Audit 13, thnaks for replying.
No I don't have the back up for the folder you mentioned. I was trying to install the last stock rom downloaded from www.stockrom.net, which I suppose was the last one. The worst part is that to computer does not recognize the phone since then.... I do not know what to do. I suppose that there is not a way to back up the folder you mentioned. I think that I have to install something from the very begining, as if the phone was to receive the installation of the very first program, as if it was just coming from the factory, totaly clean. Is that so? Am I right? And, how to do it? I tryed to download the stock rom from Samsung, but I think it was difficult and could not have it accomplished.
Thanks a lot and I'm still waiting instructions of how to solve this problem.
You should try using different USB cables and different USB ports to recognize the phone.
I assume you are using Windows since you mentioned Odin. When you connect the phone, do you see any new devices appear under Device Manager?
What is the phone's model # in download mode?
Is the the ROM you used: https://www.stockrom.net/2015/11/stock-rom-original-de-fabrica-samsung_19.html ?
Did you try using Odin 3.07?
Hi Audit13!
Thanks a lot for your help! I've already got hte files you mentioned and am preparing for trying to do the procedure you taught me.
Thanks again and soon, I hope, to be back to confirm whether it succeded.
Bie....
Hi Audit13,
Unfortunately the computer is not recognizing the SGS device.
I was ready to install the sock rom you suggested, had downloaded the Odin 3.07. I use Windows 10 and the latest drivers have been installed. The phone was in the download mode and tryed all available USB port. I've waited some minutes in each USB port for recognition with no success.
I thank you for your help. Is there any other method we could try? If you could please indicate, I thank you again.
Is there a method available using ADB procedures?
Hope there is.
Thanks, anyway for the help.
Hi Audit13
I think that the situation got a little worse. I tryed to do some recovery on the emergency recovery mode, but none of them succeeded. Now, what I get when tryng to get to the recovery mode is an android robot with an open belly with a red triangle coming out of it.... It gets to thedownload mode, but no recognition from the computer. This happened after trying to ionstall the stock rom obtained from the site you mentioned. The only thing that I could do was through the Universal-Android-Diag-Enabler-V2, what made the qualcomm start. Is there a way to make a comand to the phone that could star the USB debbuging? I tryed the various ODIN versions but with no success.
There is another problem - I'm using Windows 10 and the PowerShell uses different command lines not recognized by adb. I tipped devices and the program indicated that there was an mistake.
Is ther an Instructions Booklet for Odin?
What is your opinion? Do you think that there still exists a solution for my phone's case? If so, what to do?
Please, I ask you to help me on solving this problem.
Thanks in advance...