Database Users

Help! Trackball doesn't work anymore/How to flash a ROM with terminal?

I flashed Evil Eris 3.0 couple days ago and could out get the A2SD function to working so I decided that I want to go back to a previous version where A2SD works. When I reboot into recovery menu, I found that everything else works fine with the trackball except the downward direction. That really pissed me off because no matter how hard I try to scroll it down, it does not work. Now the recovery menu does not work for me anymore except the reboot function. It seems that it is the problem with trackball itself because when I reboot it into the system the downward direction still does not work. Anyway, I am thinking about flashing the ROM with terminal commands. Anyone who can help me with this? I'm using recovery image 1.6.2. Whats the command line for wiping the four things(I am not even sure if there is four or five because I cannot get into it! aaahhh) under the wipe function? For partitioning SD card? For upgrading from ext 2 to ext 3(if i remember this function right)? And finally whats the command line for flashing a ROM from SD card? Thanks!!!! Now I really wish that I had the Droid cuz theres a physical D-pad on it!

This will solve your issue:
http://www.xda-developers.com/android/trackball-transplant-on-htc-droid-eris/

Don't forget that when Amon_RA recovery is booted up, "adbd" is running on the phone.
That means that you can get your restore operations done by using ADB on the PC, and the
/sbin/nandroid-mobile.sh
script in Amon_RA to perform all the operations that you would have with the menu system.
do a /sbin/nandroid-mobile.sh --help
with Amon_RA recovery booted, and have a look at the
--listbackup
--subname
--restore
options for more information.
Obviously, this won't fix your trackball. But it does give you access to restore and backup operations in the meantime.
bftb0

I am a newbie with terminal and command lines, so I hope you don't mind if I ask some questions here. I checked the help list of nandroid-mobile script, but I think all the functions are to do with nandroid backup file? it is either to back up or to restore a backup file? I have successfully backed up though. But how do I wipe my dalvik cache and other misc. stuff in the recovery menu? How do I partition my sdcard using the script? and flash an img?

My trackball went out on me the other night when I was working on it. Or so I thought. Just before I called Verizon to send me a replacement, I tried one last ditch effort. I used my tshirt to wipe whatever was on the ball and pressed it kind of hard when moving the trackball around and what do you know, it fixed it. I only use my trackball for when flashing, which is a lot. So hopefully this might help you.

lacrisexistentielle said:
I am a newbie with terminal and command lines, so I hope you don't mind if I ask some questions here. I checked the help list of nandroid-mobile script, but I think all the functions are to do with nandroid backup file? it is either to back up or to restore a backup file? I have successfully backed up though. But how do I wipe my dalvik cache and other misc. stuff in the recovery menu? How do I partition my sdcard using the script? and flash an img?
Click to expand...
Click to collapse
That script only does a couple things in addition to nandroid backup and restores - it is not a replacement for the Amon_RA menu.
Your original post indicated that you were trying to restore a previously saved ROM backup, so that I why I suggested it.
Obviously, it would be better if you got your trackball fixed.
As far as wipes go, here is what happens during a wipe:
Code:
mount /system
cd /system
rm -rf /system/* >>/dev/null 2>&1
cd /
umount /system
mount /data
cd /data
rm -rf /data/* >>/dev/null 2>&1
cd /
umount /data
Since - as you said - you are a newcomer to command lines, you probably shouldn't be doing the above. In particular, the "rm" commands above are extremely dangerous if you don't know what you are doing (although I tried to minimize the danger with the superfluous-looking "cd" commands.
If you would like to learn more about using the command line, or scripting, just pull that file to your PC
adb pull /sbin/nandroid-mobile.sh nandroid-mobile.sh
and study it intently (shell scripts are plain text files). You will learn a lot about what goes on "under the hood" that way.
cheers
bftb0

I'm in the same boat as the original poster. Just need the code to push a stock or closer to stock ROM so I can return to Verizon.
-------------------------------------
Sent via the XDA Tapatalk App

thanks so much! I think I will replace my trackball just for safety. I don't want to temper with the command line that I have no idea of yet! I will certainly look into the shell script later. Also, if I want to learn more basic stuff with the terminal language, what should I do? is there any wikis or websites or even books teaching the language? I am intrigued by all these custom ROMs available for android system and I would love to learn how to build one on my own!

WOW, that is awesome! I never thought that I would be able to do that but this looks so simple!

I tried to push it really hard but nothing changed. I start to wonder if this is a common problem seen in Eris owners? I just couldn't imagine why the trackball will be senseless. Thanks for your tip though!

[SOLVED] How to Delete System Apps after Loosing Root Access From 1.72.405.3 ROM

Ok so after much lots of frustration realising I'd lost access to the delete system apps after installing HTC 1.72.405.3 (in LeeDrOiD 1.3) I've finally figured out a way to do it and without needing to use ROM Cleaner then re-flash a ROM wich would remove all my data/apps/ect I've loaded. Now this may well be a guide for you guys like me who are very new to Unix commands and the whole Android system. I hope that it helps someone coz honestly the last couple of days I've searched high and low and haven't gotten any answers that worked until I worked it out tonight.
Just as a quick note I was able to delete apps from the /system/app folder before this update when I was still on 1.32.405.6 using Visionary+ in loading R/W access to the system folder on boot and a simple file manager like Astro or AndroZip to delete. Since updating to 1.72.405.3 without Radio S-Off I've tried the following methods and found they don't work:
- Flashing rmk40's Super User/Root patch for 1.72.405.3 as in this thread http://forum.xda-developers.com/showthread.php?t=886999
- Visionary+ selecting R/W system access then using a file manager like Astro or AndroZip to delete.
- Terminal Emulator after getting "supposed" super user access after typing su then going to the /system/data folder and typing rm Facebook.apk ect... also using the other unix commands to try and change the system apps from read only to writable still no access.
- Using Root Explorer which is granted "supposed" super user access does not want to mount as R/W the system/app folder and of course then won't let me delete the apps.
- One click Radio S-Off doens't work as obviously I'm already locked out as I've loaded 1.72.405.3 (LeeDrOiD 1.3) before running Radio S-Off.
- Re-flashing to a previous 1.32.405 ROM then trying to run Radio S-Off followed by all the steps above. Nope nuthin...
Okay and here is is here's how it's done. I had to have the Android SDK installed with USB drivers (HTC Sync has the USB Drivers). I then in windows I opened up command prompt and using the good old DOS commands like "cd\program files (x64)" I go to my android sdk folder platform-tools. Once in the platform-tools let the foreign Unix commands begin
Without the exclamation marks type I type "adb remount shell"
Then "adb shell rm /system/app/Facebook.apk"
Now Facebook.apk being an example of the app you want to delete. I use a file browser such as Astro on my phone to go the the /system/app folder and easily look around and get the file names of the apps I want to delete. An important thing to remember for all the other's unfamiliar with Unix commands like myself, this ain't DOS. Unlike DOS, files and commands are case sensitive so if you try to delete the Facebook app and type it in "facebook.apk" all lower case it won't delete. Make note of any letters uppercase or lowercase in the folder name and file and type it in correctly in the Unix commands or they won't work.
The other two important things to note before you go on a Spring cleaning, delete frenzy (like I will be after I finish typing this up ) is: 1) If you delete some certain system apps (for example TelephonyProvider.apk) Android will **** itself and after booting enter a loop where you can't access anything & you can't stop it complaining about blah blah app failed. So make sure you have on your microSD card either a Nandroid backup done recently using the Backp/Restore function under the Bootloader installed with Clockwork Recovery or a working ROM that you've tried and know works such as the stock ROM or a custom ROM from LeeDrOiD, Cyanogen, ect. If you get into one of those non recoverable loops you'll need to flash the ROM and of course loose any data and apps not backed up. Okay this brings me to my next point. 2) If you want to copy any of the system apps off to your microSD card either to backup or just if you're not 100% sure if you may want to install it again later then in command prompt type this:
"adb shell cp /system/app/Calculator.apk /sdcard/"
Obviously here Calculator.apk is the app we are copying but you can choose any app to copy. Also /sdcard/ means it will go to the root folder of your MicroSD card.
Stick it to tha man and have fun cleaning up your ROM and deleting all that crap bloatware your service provider and HTC don't wanna give you access to and now without the cripple of HTC update 1.72.405.3 stopping you!

Are these persistent changes? If so I think you will be the saviour of many on here!

Are you sure the apps are not back when you reboot your phone?

I'd be pretty surprised if they're persistent.

sorry i can't see how this has worked. unless by some weird chance when trying to get s-off, gain root and what esle you have try to do. has caused you to be able to r/w to the system partition.

cattleprod sorry i can't see how this has worked. unless by some weird chance when trying to get s-off, gain root and what esle you have try to do. has caused you to be able to r/w to the system partition.
Click to expand...
Click to collapse
Ok I assure you it has worked and continues to work. One possible major difference I've just been told supposedly the stock HTC RUU 1.72.405.3 reverts you back to original hboot eng s-on. Me on the other hand I never loaded a stock HTC ROM 1.72.405.3 or an update. I loaded LeeDroiD 1.3 which has in it the base as 1.72.405.3 but also his modifications to that. So never lost clockwork recovery hboot. I can still load ROMs fine, I just lost functionallity from Visionary+ or anything else for that matter on the phone to access System folder R/W access. Using ADB on my PC as described above however did solve this. Unfortunately the other issue is after loading LeeDroid 1.3 it's permanently done something to my phone and even after flashing back to previous stock 1.32ROM the 1click Radio S-Off patch does absolutely nothing. Luckily Vodafone supposedly offers a free SIM unlock and there are also cheap alternatives on ebay.
dr.m0x I'd be pretty surprised if they're persistent.
Click to expand...
Click to collapse
Eddie1506 Are you sure the apps are not back when you reboot your phone?
Click to expand...
Click to collapse
andyharney Are these persistent changes? If so I think you will be the saviour of many on here!
Click to expand...
Click to collapse
Yes guys these are all persistant. I've rebooted quite a few times and none of the apps I've deleted have come back. These are the apps I've deleted from the "/system/app" folder and they 4 sure have not come back to annoy me: Facebook (crackbook as I like to say ), Twitter & Flickr including any widgets of the same name, stock or shares trading apps, default internet browser (replaced it with Dolphin HD), Flashlight (replaced it with moddified HTC one that says "torch" as I'm not a fan of US English), HTC Likes, HTC coin, probably some others I can't remember now.
So anyway go for it just use your clockwork recovery (modified hboot) to do a full backup first as if you remove the wrong system apps it goes in a non working error loop.
I'm only real new to the whole Android thing. Only had the phone 4 bout 2 weeks and never hit up any Unix commands before then. I'm happy to help out if I can though. Just message me and when I'm on next I'll try to help.

[Q] NAND Operations always causing hard-reset

I apologize if this has been answered before, I have been searching for days (on XDA and Google) but to no avail.
My problem is that, whenever I perform any WRITE operation to my Wildfire's system/ folder, the phone will do a hard-restart. Here are some examples:
a) Titanium Backup's "Uninstall" for any system app
- I have tried every "Root/Stock Uninstaller" app on the market, all cause hard-crashes.
b) Manually deleting or renaming an APK file under system/apps/ using any file manager, or DroidExplorer on PC
- What happens here, is that the file manager will appear to succeed the delete/rename, but upon refreshing the folder the APK returns. Within ten seconds the phone will hard-crash.
c) Running NinjaMorph, the "startup checks" causes a hard-crash (AFTER I have allowed it with SuperUser)
d) Many more which I cannot remember at the moment.
I am using the Sunaabh v1.1 ROM, and I unlocked it with unrevoked3. I did make a backup of the original Telstra Pre-Paid Eclair ROM, but really don't want to have to go back until last resort. What can I try to do?
Should I go through the unrevoked method again? Is my phone somehow NAND locked or S-ON or something? Should I try a different ROM? Could it be HTC Sense or some other "protection" service that is blocking me out? Or maybe the busybox or clockworkmod on the NAND is bad... if so, where can I find a new recommended one?
Last night I did a full reset/cache-clear/dalvik-erase in Nandroid, then reflashed Sunaabh v1.1, and did NO other flashing or mods or installs, but - (a) connect to WiFi (b) Let market update itself (c) Install Titanium Backup Pro (d) Try to uninstall system app, and the crash still occurred.
Thanks in advance for any help. I am quite new to Android so I apologize if there's any confusion or nonsense here
EDIT: Oh, also, Titanium Backup is using it's own copy of BusyBox via the option, which doesn't help, so I assume the BusyBox on NAND (from unrevoked3 I believe) is fine.....

you won't be able to do anything to the /system folder, or ninjamorph, or metamorph while your phone is booted since we still have s-on.
when we get s-off, you'll be able to do all these things while your phone is booted.

And for the completeness: if you want to change something in that folder, reboot your wildfire in recovery and select "mount /system" in the option "mount". Then you can push and pull as many files in and out that folder as you like.
Erwin

Aha, I see! Thanks for the clarification, silly newbie mistake! So in conclusion, mount in nandroid to mess with the system until an S-OFF method for Wildfire is devised. Thanks heaps guys I was worried my phone was borked!
Sent from my HTC Wildfire using Tapatalk

[Q] Why can I not delete my /sdcard/clockworkmod folder?

So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.

Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7

BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..

I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.

erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?

I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app

Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.

Failed EFS restore

Ok, I'm officially in trouble. I have a SM-G900F rooted with towelroot, SuperSu and BusyBox installed. I tried flashing with Mobile Odin Pro the latest NG2 firmware to keep root and not trip Knox. It failed twice (or three times), both times I was able to restore the original firmware with desktop Odin (http://forum.xda-developers.com/galaxy-s5/help/mobile-odin-pro-4-20-issues-t2834671).
Then something strange happened: I noticed that on 4G I had only data but no signal bars (http://forum.xda-developers.com/galaxy-s5/help/help-4g-data-signal-bars-t2837031). Then I had problems connecting to Wifi and a message appeared telling me I am in "Factory Mode" and some things are limited.
It was clear that my EFS partition is corrupted. I installed Root Explorer and there is nothing in my EFS folder (still I can use the phone in 2G/3G/4G for data and 2G/3G for calls but no Wifi).
I have 2 backups for EFS: one is made using Samsung Tools (http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325) and it's an efs.img file, the other is made using some EFS backup tool and it's just a copy of exactly what was in EFS folder (a few folders and files). I tried using Samsung Tools to restore the backup but no luck. When I restart the phone, EFS folder is still empty.
I rebooted in recovery mode and it said "failed to mount /efs". That's probably why Samsung Tools can't do it's job but I'm not sure. At this moment I'm not sure of anything. I think that someone with some knowledge (knowledge that unfortunately I'm missing) can help me fix this.
I really need for some help, so any ideas are welcomed.
Thank's,
Mihai Raducan

..

fffft said:
No TWRP backup, huh? How did I know that was going to be the case? 10 demerits. Okay, you seem to have been on the right track in recognizing that your EFS partition was unmounted and therefore inaccessible in recovery mode.. but you didn't mount it? You didn't give us much detail to work with, but assuming that you have a custom recovery like TWRP, you could go to the advanced /mount menu and check the mount EFS partition. Or if you don't have that option for some reason, mount it yourself e.g.
.
Click to expand...
Click to collapse
It's only stock recovery, no TWRP or CWM.
I didn't mount the EFS partition before because I didn't know how. I'll follow your guide and report back.
Regarding the exact copy of EFS (efs.img): It's done with Samsung Tools but never had a chance to test it, so... I don't know. But let's take it one at a time. First problem: mount efs partition.
PS: My Windows laptop is playing tricks on me so it's going to take a while to reinstall Windows, adb, etc. But I'll be back.
Thank's.

..

Ok, I installed Adb, phone is recognized.
The first line of code
Code:
# ls -al /dev/block/platform/msm_sdcc.1/by-name
gave me a list with the location of efs (and more). EFS is at dev/block/mmcblk0p12.
The second line of code
Code:
# /sbin/mount /dev/block/mmcblk0p12 /efs
gives me : tmp-mksh: /sbin/mount: not found
Am I missing something?

is img of /efs partition enough for restore?
here, it says, that we need to have 3 partitions for full restore..??..: http://forum.xda-developers.com/showthread.php?t=2737448
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/efs.img.ext4
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/modemst1.bin
dd if=/dev/block/mmcblk0p14 of=/mnt/sdcard/modemst2.bin
but Samsung tool only makes efs.img..??.. who is right who is wrong?

..

fffft said:
Personally, if an EFS backup program made an image (.img} file and it was the same size as your EFS partition I'm sure that it was an exact copy and try writing it back. It's unlikely to make anything worse. But don't blame me if it somehow goes wrong. I'm just describing an option of last resort and commenting on what I would do with my own phone.
You can check the size of your EFS partition with the cat command (EFS should be partition 12)
Code:
$ su
# cat /proc/partitions
.
Click to expand...
Click to collapse
I checked the size of my efs.img and the size of the partition with the command you gave me. They are both 14MB but on a closer look, adb shows 14336 and Windows reports 14680kb. So I don't know....
fffft said:
You're using ADB instead of a terminal emulator app which is a new variable. There are a lot of ADB variants around and I have no idea what your command interpreter (mksh) or you have done with the shell environment.. which may require syntax adjustments.
Not found implies that the /system partition isn't mounted. But it could also be an ADB syntax quirk, path or symlink error, a typo or.. well, could be a lot of things. Perhaps try the syntax below. Or run the command from a terminal emulator instead of ADB shell.
Code:
$ su
# adb shell mount /system
# adb shell mount /efs
.
Click to expand...
Click to collapse
I installed Android Terminal Emulator and Shell Terminal Emulator (PlayStore) but I got the same thing. What's strange is that in both of them when I run the command "adb devices" they both give me nothing while in adb shell on desktop I get a number (as it should).
I understand that the syntax is for a specific terminal emulator. Tell me please what is that terminal emulator (that you know syntax is correct) so I can try with that one.

..

fffft said:
Try this terminal emulator app.
If you have continued difficulties, you should describe step by step what you are doing. In exhaustive detail or as close as you can get to that. Then someone in the forum will have a good basis to see where you are going astray. Or alternately where I made a typo or whatever the impediment turns out to be.
.
Click to expand...
Click to collapse
This is one the apps I tried with.
I'm describing step by step what I do. What I start with: SM-G900F rooted with towelroot, stock recovery, SuperSU and BusyBox installed, Knox 0x0.
I download and install https://play.google.com/store/apps/details?id=jackpal.androidterm.
Using this app:
Code:
su
and it changes to [email protected]:/#
I enter:
Code:
# ls -al /dev/block/platform/msm_sdcc.1/by-name
and it gives me a list with paths to different things. EFS apears to be at /dev/block/mmcblk0p12
I enter
Code:
# /sbin/mount /dev/block/mmcblk0p12 /efs
and it says: "tmp-mksh: /sbin/mount: not found"
When I try
Code:
adb devices
it gives me no number.
I attached a file where you can see what I did.
One more thing: when I enter (stock) recovery, every time it says "Installing system update" for about 20 seconds and then enters recovery where it says "failed to mount/efs : invalid argument". The CSC part is apparently ok.

..

It doesn't work. From ADB it says "mkdir failed for /efs, File already exists".
And from terminal emulator, (with busybox) it asks for an argument (pic atached).
Is there any way of using Odin to fix this, because it seems that nothing works.

fffft said:
Who is right about what? You didn't give much of a context for your question. The OP said that his EFS was corrupt, so we have been talking about EFS which is self contained in partition 12 or exported as efs.img.
Click to expand...
Click to collapse
i thought there could be more to the problem, not just /efs partition, since he said it was clear to him, and not beeing 100% fact..

..

Thank's for your time. I'm flashing now the original firmware (so I can start fresh) and I'll document every step I take. I'll report back.

Ok, I tried flashing the original firmware (ANE2) and this time I can't even get pass the Samsung authentication screen (the first time you boot your phone and asks for language, Google account, etc), It asks me for the Samsung account and password that this phone was registered with) and it tries for a couple of minutes to verify the credentials (on data network) then it fails saying it is a network error.
I tried wipe cache/factory reset (from recovery) and reinstall a different firmware. Same thing. It seems now it's really messed up.

As mentioned earlier, we did not expect a firmware image to fix your EFS. And the EFS is critical to normal phone operation.
The purpose of stock firmware is so that your phone is stable, reduce variables that might interfere and facilitate fixing your EFS. So I'm not why you apparently expected it to be an outright fix in and of itself?
Having installed the stock firmware should help you achieve your remaining goals. Now you need to decide if you are going to install a custom recovery or not. A custom recovery will increment your Knox flag if it isn't already. That affects very little, but it's your decision. It may affect the private mode feature or warranty claims, however many carriers don't care about Knox and E.U. legislation bars Samsung from invalidating a warranty unless they can demonstrate that root damaged your phone.
Whether or not you install a custom recovery, you will want to try writing your 14 MB EFS backup image to your phone. I believe that you'd find it easier to do so with a custom recovery. But it can be done with a stock one too, you will just have to deal with a bit more syntax in the latter case.
.

fffft said:
As mentioned earlier, we did not expect a firmware image to fix your EFS. And the EFS is critical to normal phone operation.
The purpose of stock firmware is so that your phone is stable, reduce variables that might interfere and facilitate fixing your EFS. So I'm not why you apparently expected it to be an outright fix in and of itself?
Having installed the stock firmware should help you achieve your remaining goals. Now you need to decide if you are going to install a custom recovery or not. A custom recovery will increment your Knox flag if it isn't already. That affects very little, but it's your decision. It may affect the private mode feature or warranty claims, however many carriers don't care about Knox and E.U. legislation bars Samsung from invalidating a warranty unless they can demonstrate that root damaged your phone.
Whether or not you install a custom recovery, you will want to try writing your 14 MB EFS backup image to your phone. I believe that you'd find it easier to do so with a custom recovery. But it can be done with a stock one too, you will just have to deal with a bit more syntax in the latter case.
.
Click to expand...
Click to collapse
I didn't expect to fix the problem, I wanted a fresh start so I can try again the adb/terminal emulator commands. But what I didn't expect was not being able to, basically, start the phone. When you first start a new phone (or after a factory reset) it asks you language, Wifi, Google account and, in my case, for a Samsung account that this phone was paired with.
If I try to connect to a Wifi network the phone reboots itself. If not, it tries via data connection. Google credentials are ok but when it tries to verify Samsung credentials it gets stuck saying that it's a network problem and it doesn't go futher. So I get stuck at this point, between booting and actually being able to use the phone. I can't install anything, I can't receive or make phone calls (like before). I can't go to USB debugging so ADB doesn't see the phone.
I don't want to install a custom recovery because my Knox is 0x0 and my warranty is intact. I live in EU but in this case, it's clear that root access is what got me in trouble and brought the phone in this state. Actually not root access got me in trouble, but what I did with root access

raducanmihai said:
I didn't expect to fix the problem, I wanted a fresh start so I can try again the adb/terminal emulator commands. But what I didn't expect was not being able to, basically, start the phone. When you first start a new phone (or after a factory reset) it asks you language, Wifi, Google account and, in my case, for a Samsung account that this phone was paired with.
If I try to connect to a Wifi network the phone reboots itself. If not, it tries via data connection. Google credentials are ok but when it tries to verify Samsung credentials it gets stuck saying that it's a network problem and it doesn't go futher. So I get stuck at this point, between booting and actually being able to use the phone. I can't install anything, I can't receive or make phone calls (like before). I can't go to USB debugging so ADB doesn't see the phone.
I don't want to install a custom recovery because my Knox is 0x0 and my warranty is intact. I live in EU but in this case, it's clear that root access is what got me in trouble and brought the phone in this state. Actually not root access got me in trouble, but what I did with root access
Click to expand...
Click to collapse
The only way to get your phone to work again and gain access to networks/wifi is by installing a new motherboard if you can`t restore the old EFS folder somehow.
Next time try this method to backup and restore your EFS folder http://forum.xda-developers.com/showthread.php?t=2737448 if you are rooted.

raducanmihai said:
I didn't expect to fix the problem, I wanted a fresh start
Click to expand...
Click to collapse
Sorry that you found it a surprise.. but if reinstalling the stock firmware eliminated your phones problems, that would make it a solution, whereas it's a stepping stone. I did try to explain this earlier, where I told you that installing the firmware would not fix your EFS. And the EFS is essential to normal phone operation.
Regardless of the surprise, you are now on a better footing to finish fixing your phone. But for clarity, your problem started when your EFS got corrupted somehow. And your EFS needs to be restored before the problem will be resolved.
On the positive side, you appear to have a EFS backup, even if the backup app won't easily restore it to you phone. If you stick with it.. you just have some minor hurdles remaining - syntax or whatever - in getting your 14 MB EFS backup restored (written) to your EFS partition.
If you want that done painlessly, then pack a case of beer and your phone into a box and ship it to me. And I'll return it fixed. As it seems unlikely that you'd do that though.. then try to provide as much info as you can here and someone will try to help you finish fixing your phone in this thread.
.