Hi alltogether,
I am know here and need some help for noobs. Bought an old S7 to try and practice to install e/os do do it later on a fairphone. I does not work. I read a lot of articles and help stuff but am still stuck. Maybe because of lack of understanding or skills though.
Already tried:
used easy installer …goes only to step 7.
tried command line install: e recovery tool 2.7 does not do the adb install
(debugging, oem turned on, cleared adb keys 20 times)
tried to go the way with twrp. No connection to the device.
I long as the smartphone is on or in the original recovery mode, the connection works and can see the device in the command line looking up for adb devices. But when I change to Bootloader mode or the e recovery mode it says “device unauthorized”.
Dear aibd,
thanks for reply. I fear erecovery is installed. Please see pictures. As you see the connection is there as long the phone is not in erecovery mode or odin download mode.
As a new user I am only allowed to post one picture per post. So here is the one of the console and the next post will be the smartphone screen.
So on the device in e-recovery, now tap Apply update, then Apply from ADB. Now you will see ADB sideload and text at the bottom of the screen saying send the package by sideload.
I did of course. Nothing happens. Erecovery reports time out after some time. During sideload command there is no connection beetween device and pc…unothorized device. I can proof it all with screenshots. Looks like in the screenshot.
I believe that problem also causes the easy installer to fail at step 7.
As said by @piero Advanced >Enable ADB should correct Unauthorised.
Have you already Format data on the phone or Factory reset? Factory reset has the effect of undoing the Developer option, USB debugging, causing “unauthorised”.
Did you remove all accounts from the phone before you started.
I cannot tell what Easy Installer step 7 is. Is it this same sideload command?
I enabled the adb in advanced settings. Tried it with and without factory reset and all accounts were removed. As soon as phone is in erecocery or odin download the connection gets lost. I can reproduce it every time and I can hear with trough the windows system sound and see it trought adb devices command.
Yes, Easy Installer Step 7 is where the rom should be pushed to phone via adb.
I think I tried all the “standard stuff” exactly like described in the tutorials and wikis. I tried every step at least 10 times. It is always the same point where I get stuck.
Isn´t there a posibility to install via app with running android? If I´d have the install files on the phone the adb would not be needed, right? By the way, instaling twrp does not function either because it is not possible to push in Odin mode through Odin software (unauthorized device).
Interesting is that with the stock bootloader the adb connection works.
Thanks for the help so far. The picture of the Odin download mode is included.
“You can explore exactly where you can navigate to …” I am not sure where to explore.
" e-Recovery does have the ability to Apply Update > Apply from sdcard." …so it means that I need to get a card reader for pc and to copy the e.2.7 and the rom itself and then run the e-Recovery from the sdcard?
I did enable adb before flashing (please see screenshot 2 posts before). Also monitored adb devices and as said: always works despite in Odin or e-Recovery…no matter if adb is activated or not, there is no connection, Maybe there is a bug in e-Recovery which does not activate adb sideoload when you go do advanced > enable adb. Screenshots are included.
How can I find out if the internal storage is supported and if so what would be the next steps?
cable: yes. tried several and since there is always a working connection despite with Odin and e-Recovery…also in the normal recovery. Cable works.
Thanks for the howto. Step 9 is the only one I did not try so far and did´t know how. Will try to install from internal storage and thus without cable.
I am sorry @Viki but somehow you are not demonstrating exactly where the problem is, although I hear well how frustrating it must be and what you have seen.
In the section below, I take a phone with USB debugging OFF and demonstrate how I move to sideload. What I would really like to find out is where exactly does your device deviate.
Blow by blow
Device presented in Recovery with USB debugging disallowed
:~$ adb devices
daemon not running; starting now at tcp:5037
daemon started successfully
List of devices attached
XYZxxxxxLR unauthorized
debugging is on. When I plug in cable in Android OS, abd devices command gives the phone as output. So the device is authorized. The same is the case when I am in the OEM Bootmenu, where I also can push something via sideload.
But when I install e-Recovery and enable adb (like in your second screenshot) or not enable adb, a connection is not established, so adb devices command leads to “device unauthorized”
This results in the same screen like your second screenshot: Enabled ADB. …Now send the package… but nothing happens becuase the adb sideload connection between the phone which is in e-Recovery mode and the PC does not exist, hence the ROM does not get from the PC to the Phone trough the cable.
Is the problem more clear with this explanation?
Also thanks for reading all my stuff
