Hi guys. I'm trying to modify a Samsung stock recovery image so that ADB is enabled on boot. For my SM-G360G. Code named Emergency Poor Mans Recovery or EPMR for short and want of a better acronym, such as ER. For like minded people who broke their screen, on a mobile with default settings, such as mine is.
So I've managed to extract a stock recovery.img, modify it and repack it. I then converted it to a tar.md5 for Odin. And used Odin to flash it from Windows. To which it responded with a pass. All good.
So then I shut it down and rebooted phone into recovery. But there was no change. The ADB shell tools could not see my phone. I issued an "adb devices" to no effect. I've tested my ADB install with another working phone, an SM-570Y, so my drivers look okay, as that was found. I just tested it from that with USB debugging on by shelling to it from ADB. Cool. I use ADB from Linux as I found it more reliable than Windows and it installs easier.
I've been practicing "blindly" putting my broken phone into download mode and since I have been able to download images to it that "looks" like it works. So I'm sure I have been getting it into recovery mode. At least after I press the start keys there is no aural evidence of it booting. I feel the vibration after it turns on then release the keys. So it should be in recovery.
I modified the default.prop file in the root of the recovery initrd. And changed/added these settings to the following:
Code:
ro.secure=0
ro.debuggable=1
ro.adb.secure=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Are these settings correct and should enable adb from recovery? And if so should adb then work once recovery is running? No need for selecting any menu items I can't reach? TIA.
Related
device : Dupad K1
android version: 4.2.2
baseband version: MOLY.WR8.W1315.MD.WG.MP.V1.P7,2013/09/10 17:18
built number: SPMTK6572M431WP02V07
CPU MOdel: ARMv7 Processor rev 3 (v71)
I had install boot animation app after rooted my device and installed a boot screen... after restart device got stuck in boot screen that i installed....
have online nandroid backup but dont know how to restore it
dont have cwm...
please someone help me to regain my device
Recovery mode
Go to recovery mode.
Do you have Android SDK installed in your machine or any Linux substitute in case you are a Linux user? You'll need it.
Read before attempting.
-Find the key combinations that applies to your phone.
-Get into recovery mode pressing the specific keys.
-Connect your device through USB port.
-Write in terminal or cmd:
Code:
adb devices
-if a device is connected proceed, if not, find what's going on.
-Write in terminal or cmd:
Code:
adb reboot recovery
-Find the desired ROM (The one made for your device or a previous system backup that you have made when the phone still worked), ensure it's safe and specific made for your phone.
-There must appear some options showing in your phone screen or maybe the Android robot laying on its back, you'll need to see the options, click buttons until you see them.
-Choose the line that says "apply update from ADB".
-Use the command in Terminal or cmd:
Code:
adb sideload yourzipfile.zip
-It must be a zip file, sometimes you need to unzip the zip file just to find another zip file (usually named update.zip)
-It must show the robot in a different position and some yellow lines showing you the progress, if something goes wrong you'll know, if everything goes fine, good.
-Restart the phone and you're done.
If you can't load the file with adb sideload command, copy the zip file in the SD card and choose apply update from SDcard from the recovery menu, locate the zip file and apply it.
You should be fine if you use the right Android version or backup.
Good luck. If this doesn't works or goes easy as I say, let me know.
Prerequisites:
Can boot into recovery
A working bootanimation.zip
Adb....if you dont have it download minimalistic adb and fastboot for windows.
Okay lets get down to business....
1.First boot into recovery and then select apply update from adb and type -'adb devices'
This will open up the comms port and start adb comms with the device.
2.Now type adb push <bootanimationfile>.zip system/media/
3.and voila you will have revived youtlr device.
Hit thanks if this helped.
Hi all,
Problem description :
Black screen after showing Samsung S5 logo. In this condition, ADB Devices will show my device as being "offline".
I can enter recovery mode (note that I'm still using stock recovery i.e no CWM), and the device itself is already rooted with USB Debugging under Developer Section : Enabled.
In stock recovery mode, I can go to ADB Sideload mode but I can't access ADB Device mode, which I hope will be able to push my previously backed-up and working build.prop located both in PC and the device's internal storage.
This issue happened after I modifed my build.prop file (I edit it in Windows text editor) and then replaced it back to the device using Root Explorer. I didn't set any CHMOD after that, which I suspects being the culprit here.
Question :
Is there any way I can do to replace the edited build.prop with my backed-up version without having to factory reset or flashing ROM ?
I've managed to get it working again.
Although the device seems to be in offline state i.e black screen with no User response whatsoever, if you try the ADB command it will actually still work.
If this is the case, then you can simply flash a custom recovery e.g TWRP or CWM (preferably those which can provide you with a file manager) using ODIN in download mode.
After flashing the custom recovery, then you can change the build.prop permission using CHMOD 644.
Hi,
I'm stuck here on a large problem : I've got an I9300 with broken screen and digitizer. I just wish to enable adb in normal use so I can take control of it and install a VNC app for future projects, thus I don't care about erasing all data.
I managed to flash CWM via Odin on it, then I was disappointed to see that Odin could not help me flashing a custom ArchiDroid (zip file) on it, on which I enabled adb as shown in thread n°2335799 (sorry can't post links yet), by editing default.prop in boot.img and build.prop also.
Then I booted my S3 in recovery mode, I did Vol- and Power, "sideload" appeared in the list of
Code:
adb devices
I then did
Code:
adb sideload rom.zip
waited for it to finish.
After that I boot it in "normal" mode, and surprise, adb is still not activated!
I have no clue of what could possibly be wrong!
Thanks in advance for any help!
My e970 got smashed, and touch screen is out.
I cannot get into the phone as the lock screen is impossible to swipe. I tried the ADB method of editing the lock screen settings of the ROMs . However I am not able to get into the ADB shell to execute the commands. ADB only works in recovery and lists device as a recovery and not as a device proper.
There a way thru the ADB in recovery by executing pull command but ADB cannot access the System / data folders for the Build.prop file to be edited. In my situation, as ADB only connects in recovery mode, it is not entering the sytem area and file cannot be found.
Please advise on the way forward, as I cannot find a guide in this situation, most guides show the ADB pull command, which in my case does not work.
Milind
milindchitale said:
My e970 got smashed, and touch screen is out.
I cannot get into the phone as the lock screen is impossible to swipe. I tried the ADB method of editing the lock screen settings of the ROMs . However I am not able to get into the ADB shell to execute the commands. ADB only works in recovery and lists device as a recovery and not as a device proper.
There a way thru the ADB in recovery by executing pull command but ADB cannot access the System / data folders for the Build.prop file to be edited. In my situation, as ADB only connects in recovery mode, it is not entering the sytem area and file cannot be found.
Please advise on the way forward, as I cannot find a guide in this situation, most guides show the ADB pull command, which in my case does not work.
Milind
Click to expand...
Click to collapse
Hmm, what are you planning to do after unlocking the phone? If it's to back up files, I think TWRP automatically mounts your phone storage (it does for me) when plugged in and started up.
Vampir1c said:
Hmm, what are you planning to do after unlocking the phone? If it's to back up files, I think TWRP automatically mounts your phone storage (it does for me) when plugged in and started up.
Click to expand...
Click to collapse
NO there is a specific app from the Govt. in Singapore that is not compatible with my standby Samsung s3. It requires synching my data by blue tooth, which I am not able to do without my e970 touch functionality. Hence need this help:
I need to be able to get into the phone unlock, then enable bluetooth to sync my data to the app.
Hope that explains why I need to get more than data which I also knew long back.
regards.
Milind
try http://forum.xda-developers.com/showthread.php?t=2620456
Hi there,
does anybody know how I can boot into safe mode at LegacyXperia SEMC 2011 ?
My ROM is lineage-14.1-20170514-UNOFFICIAL-LegacyXperia-urushi of AdrianDC.
Kernel: 3.4.0-LX+, [email protected] #1, May 2017.
But I suppose that the right key combination at boot start is all the same at all SEMC 2011, isn't it?
I tried a lot of key combinations but failed so far.
The only way I know to get into safe mode so far is at shutdown (long press of option 'restart'). But this doesn't help cause in most cases you have the situation that the system doesn't properly boot up at all.
I am absolutely sure that there is a method existing but really NOWHERE I can find any info about it. Strange.
Hope, anybody of you knows?...
Thank you guys.
Addendum:
Now my experiments for safe mode were successful:
Press volume down from the darkening of the load animation until the very short vibration.
Activating boot log
However, safe mode didn't help. My sudden boot problem still exists in safe mode.
The boot animation keeps endless after its darkening... So strange.
So I am dependent on the log script to find out which modification I should do with TWRP's file manager to solve the boot problem...
Is there anybody who knows how to activate AND check the boot log to find out at which point a boot process failed?
After some research I found the folders system/bin/log or system/bin/logcat.
Are those the right one?...
However, TWRP's file manager does not even seem to support a file reader to review files. Can that really be true? So how could I check logs?...
Could I possibly be successful with its 'terminal' function?
But so far I didn't find out which commands it supports... ('vi' obviously not)
Addendum:
Meanwhile I could access and read the mentioned files above via USB-OTG. But I cannot recognize any useful log info. Almost control characters.
Can anybody tell me please where I can find proper boot logs?...
How to transfer files by adb command?
And there is still a third point:
There is no problem to flash files via 'adb sideload filename.zip'.
The command 'adb devices' before properly finds a device.
But I am just failing to send or receive files via 'adb push...' or 'adb pull...'.
Sample: "adb pull sdcard/download/app3.zip" or "adb push F:/stetups/filename.exe sdcard".
However, I always get the error message: "error: closed".
What is the mistake?...
Is it possibly because MTP doesn't seem to work?
Cause I can activate and deactivate MTP in menu 'Mount' again but there is no drive icon appearing in the Windows file manager. And also no USB device at the device manager. Just the USB-off sound.
Or is it possible that TWRP 3.1.1-0 does not support other adb commands at menu option 'sideload' at our SEMC 2011 devices?...
I also don't know which commands TWRP menu option 'terminal' supports. ADB it doesn't seem to!
E.g. if I use any adb command like 'adb ...' it's returned "adb: not found".
Addendum:
The third method USB-OTG finally works, REALLY the only one of the three?...
Thank you for commenting my results here!...