Hello,
I install z4mod, and I patch kernal, and it's fine, after that I don't what I do , I do convert to filesystem, after that open till galaxy s come the shutdown.
I use froyo 2.2
please help me?
I can not open phone in download mode or recovery by using 3 buttons.
All I can say is that if you cannot access download mode you're in trouble. :/
so what can I do,
any idea
If you can't get into download mode you may have bricked your phone, the only way to fix it is to make a homemade jig or put your phone in the oven. I'm not sure what your preference may be...
EDIT: In future please do not post in this section just to get your thread more attention .
I use
Z4mod over in I9000 converts data to ext2
and it's not open download mode from begening when it normal mode,
any news,,,,
PaulForde said:
If you can't get into download mode you may have bricked your phone, the only way to fix it is to make a homemade jig or put your phone in the oven. I'm not sure what your preference may be...
EDIT: In future please do not post in this section just to get your thread more attention .
Click to expand...
Click to collapse
NEVER do that nonsense.
dnsp said:
NEVER do that nonsense.
Click to expand...
Click to collapse
yeah, not with the oven
but the trick with the hair blower works and also just recently has rescued another unfortunate soul (not me)
Isn't it possible to get into download mode by adb? I did it a few times, but i can find the tutorial only on a german forum called android-hilfe.de.
It worked for me a few times:
1: Install Kies (probably you did already)
2. install adb for windows ( don't know where to get it, sorry)
3. install odin 1.3
4. open command line and navigate to adb folder
5. start odin
6. place command line-window and odin window so, that you can see both.
7. write in command line: "adb reboot download" and press enter ( starts daemon)
8. remove battery
9. connect the phone to pc using usb cable
10. put the battery in the phone again
11. write in command line: "adb reboot download", DO NOT PRESS ENTER
12. wait until it shows the battery symbol on your phone, indicating that its loading. press power button
13. now look at odin. when the Com-Port becomes yellow, press the enter button in command line, where you wrote "adb reboot download" before.
Now you are in DL-Mode.
Hope it works and someone maybe can give you a better written tutorial with a link to adb. Like i said, it worked for me.
eeegamer said:
Isn't it possible to get into download mode by adb? I did it a few times, but i can find the tutorial only on a german forum called android-hilfe.de.
It worked for me a few times:
1: Install Kies (probably you did already)
2. install adb for windows ( don't know where to get it, sorry)
you mean adbRecovery
3. install odin 1.3
4. open command line and navigate to adb folder
you mean by command prompt, can give me simple,
5. start odin
6. place command line-window and odin window so, that you can see both.
7. write in command line: "adb reboot download" and press enter ( starts daemon)
8. remove battery
9. connect the phone to pc using usb cable
10. put the battery in the phone again
11. write in command line: "adb reboot download", DO NOT PRESS ENTER
12. wait until it shows the battery symbol on your phone, indicating that its loading. press power button
13. now look at odin. when the Com-Port becomes yellow, press the enter button in command line, where you wrote "adb reboot download" before.
Now you are in DL-Mode.
Hope it works and someone maybe can give you a better written tutorial with a link to adb. Like i said, it worked for me.
Click to expand...
Click to collapse
thanx bro,,
Plz plz don't do stuff to your phone if you don't have 3button working.
I beg you.
Apply the 3button patch to get it working then proceed.
thanx eeegamer
but give me
error: device not found
I do what you said
Daneshm90,
the 3 butons not work with me, before the I got this problem, it's from the factory,
almuhajir said:
Daneshm90,
the 3 butons not work with me, before the I got this problem, it's from the factory,
Click to expand...
Click to collapse
Yes but there are patches on this forum that fix that.
Research and the world is yours
Daneshm90 said:
Yes but there are patches on this forum that fix that.
Research and the world is yours
Click to expand...
Click to collapse
please help, my head was broken, from morning I research,
Well firstly your original post is very confusing.
Im assuming english isn't your first tongue, if not plz use something like google translate which might do a better job.
Is ur situation that you want to flash something and don't know how ? Or you flashed something and can't boot into the os and have neither download mode / recovery mode at ur dispense ?
I assume you are saying that now when you are switching on your phone you are not getting startup screen of I9000 and you are getting a small icon showing broken connection with phone and PC.
If this is the case, you can try doing following trick
1. switch off phone and remove battery
2. Plug your USB with phone and PC
3. Start ODIN V3
4. Now press vol down + menu (Centre button) and power on
5. Insert your battery
6. If Odin will show your phone connected you are safe
7. if not try it again (do it 10 times)
Once Odin will detect your phone...flash any stock ROM from forum.
If unfortunately this does not work, then use hot-blower option.
1. Switch off your phone take out battery
2. use hot blower (hair dryer or something else) on the part where battery is placed.
3. Heat till the time you can tolerate...dont worry nothing will happen to Galaxy
4. Now press vol down + menu (Centre button) and power on
5. Insert your battery
6. Your phone should show yellow screen of downloading
Above trick seems insane but believe me it saved me (Thank God)
Galaxy S can not be unbricked (at least easily by any RM) I have faced this situation many times and come over it.
Let me know how it goes.
Before all of these I install OneClickLagFix v2.2, but I got same problem, and I use adbRecovery and I solve the problem.
First I install z4root and i root my device, then I install z4mod and I patch device kernel, after that, I choose converts data to filesystem, then the device rebooted automatically, until show logo GALAXY S, then the screen come black and vibrate allways,
The problem also when I connect it to USB my computer does not get the device,
But in the problem I have it now the adbRecovery not do any thing
Oh you are safe then...
Press vol up + menu + power button
once it shows Samsung logo leave the power button but keep pressing menu + vol up. After 4 seconds leave these button also.
Your phone should go to recovery mode.. then flash any rom..
If this does not work then use below:
1. switch off phone and remove battery
2. Plug your USB with phone and PC
3. Start ODIN V3
4. Now press vol down + menu (Centre button) and power on
5. Insert your battery
6. If Odin will show your phone connected you are safe
7. if not try it again (do it 10 times)
Once Odin will detect your phone...flash any stock ROM from forum.
almuhajir said:
thanx eeegamer
but give me
error: device not found
I do what you said
Click to expand...
Click to collapse
C:\android-sdk-windows\tools>adb ls
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
C:\android-sdk-windows\tools>
C:\android-sdk-windows\tools>adb devices
List of devices attached
1000efxxxx758 device
C:\android-sdk-windows\tools>
Originally Posted by Spin Dr Wolf
Gah. I can't get adb running, i keep getting the message below whenever i try any adb command.
" 'adb' is not recognised as an internal or external command, operable program or batch file. "
I have no idea where its going wrong though, i have the USD drivers installed got the SDK kit unzipped on the drive too, using the commands in the right place. Anyone got any ideas ?
I'm using Vista sadly if that makes any difference ?
HI! I understand you reading this part:
Section 3: Running ADB from Command Prompt
Running Command Prompt:
Windows XP: Select Start or Tap the Windows Key on your Keyboard, select "Run" and type "CMD" then hit "Enter".
Windows Vista/Win7: Select Start or Tap the Windows Key on your Keyboard, select the search box on the left and type "cmd" then hit "Enter".
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-x.x_rx\tools "x = version you are using"
The Value is WRONG!!! It has changed. It should be C:\android-sdk-windows-x.x_rx\platform-tools\
Dont forget to x10christian
I haven't found anything about this yet so I am going to post it as it caused me a lot of hell until I got it right. Admins feel free to remove if need be.:laugh:
When installing the adb drivers for your KFHD on Windows 8 you will almost always run into the error where the driver refuses to install. Simple fix:
Open an elevated CMD prompt (hit the Win key, type in CMD, right click cmd and click run as admin)
Type in or paste:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Next Reboot
This sets your PC in Test mode and is vulnerable to almost anything.
Install your drivers again.
Go to device manager and right click on your KFHD.
Click update driver.
Browse my Computer for driver software.
Let Me pick from a list of device
Show all and hit next
Hit have disk and browse to your directory where your driver is stored at.
After you click ok there will be a few adb choices. Always select adb composite device. Else half the dev adb tools cant detect the KFHD.
After that it will install the appropriate driver(64 or 32 bit)
Whallah you have installed the drivers.
***NOTE****
If you have already plugged in your KFHD and windows has already installed the incorrect driver don't panic. Right click the Kindle and click uninstall. Check delete driver and ok. Then you can proceed to install the right one.
After the drivers are done installing then open up another elevated CMD prompt and type or paste in:
Code:
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
And reboot again.
Now you should have no issues with your KFHD not showing up in device manager.
ADB Driver Install Using bcdedit Command
CoB_Mike said:
I haven't found anything about this yet so I am going to post it as it caused me a lot of hell until I got it right. Admins feel free to remove if need be.:laugh:
When installing the adb drivers for your KFHD on Windows 8 you will almost always run into the error where the driver refuses to install. Simple fix:
Open an elevated CMD prompt (hit the Win key, type in CMD, right click cmd and click run as admin)
Type in or paste:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Next Reboot
This sets your PC in Test mode and is vulnerable to almost anything.
Install your drivers again.
Go to device manager and right click on your KFHD.
Click update driver.
Browse my Computer for driver software.
Let Me pick from a list of device
Show all and hit next
Hit have disk and browse to your directory where your driver is stored at.
After you click ok there will be a few adb choices. Always select adb composite device. Else half the dev adb tools cant detect the KFHD.
After that it will install the appropriate driver(64 or 32 bit)
Whallah you have installed the drivers.
***NOTE****
If you have already plugged in your KFHD and windows has already installed the incorrect driver don't panic. Right click the Kindle and click uninstall. Check delete driver and ok. Then you can proceed to install the right one.
After the drivers are done installing then open up another elevated CMD prompt and type or paste in:
Code:
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
And reboot again.
Now you should have no issues with your KFHD not showing up in device manager.
Click to expand...
Click to collapse
CoB_Mike,
We use it in our tutorial but not in this much detail. Remember, you have a right to post any though that you may
find will help others. Do not be shy of posting, if you do not see the topic POST your thoughts please.
http://forum.xda-developers.com/showthread.php?p=35957305
I am grateful we such a deserve community with a vast amount of information. Thank you again for taking
the time to post this information. You are a good writer!:good:
Appreciate it. Yeah I didnt see it in the root guide /facepalm. I have pics to add to this just need to upload as well. Thanks for the support. I usually write teardown and repair guides for game systems or computers or cell phones just moving my focus here. And I grad in Dec with my BS in Software Engineering as well. THANKS!
Follow Up - Feedback
CoB_Mike said:
Appreciate it. Yeah I didnt see it in the root guide /facepalm. I have pics to add to this just need to upload as well. Thanks for the support. I usually write teardown and repair guides for game systems or computers or cell phones just moving my focus here. And I grad in Dec with my BS in Software Engineering as well. THANKS!
Click to expand...
Click to collapse
CoB_Mike,
Great work! Congratulations on the BS Degree. I have been a software developer for over 25 years. When I was your age
we did not have the internet or Android or this! What I have sen the last 25 years is awesome, almost mind boggling.
Anyway, we are happy to have you as part of the XDA Developers Team. When you have time, take a peek at our new
software for the Kindle Fire: http://forum.xda-developers.com/showthread.php?t=2096888
The software is in it's infancy and will be changed to C# next month, then the feature will grow through the roof.
CoB_Mike said:
I haven't found anything about this yet so I am going to post it as it caused me a lot of hell until I got it right. Admins feel free to remove if need be.:laugh:
When installing the adb drivers for your KFHD on Windows 8 you will almost always run into the error where the driver refuses to install. Simple fix:
Open an elevated CMD prompt (hit the Win key, type in CMD, right click cmd and click run as admin)
Type in or paste:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Next Reboot
This sets your PC in Test mode and is vulnerable to almost anything.
Install your drivers again.
Go to device manager and right click on your KFHD.
Click update driver.
Browse my Computer for driver software.
Let Me pick from a list of device
Show all and hit next
Hit have disk and browse to your directory where your driver is stored at.
After you click ok there will be a few adb choices. Always select adb composite device. Else half the dev adb tools cant detect the KFHD.
After that it will install the appropriate driver(64 or 32 bit)
Whallah you have installed the drivers.
***NOTE****
If you have already plugged in your KFHD and windows has already installed the incorrect driver don't panic. Right click the Kindle and click uninstall. Check delete driver and ok. Then you can proceed to install the right one.
After the drivers are done installing then open up another elevated CMD prompt and type or paste in:
Code:
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
And reboot again.
Now you should have no issues with your KFHD not showing up in device manager.
Click to expand...
Click to collapse
Nice guide. Ill be using that tonight
Bryan
Reduce Windows 8 Security - BCDEDIT
bryanchapman9999 said:
Nice guide. Ill be using that tonight
Bryan
Click to expand...
Click to collapse
bryanchapman9999,
It does indeed work, it is a part of our tutorial: http://forum.xda-developers.com/showthread.php?t=2069117
We receive feedback everyday, Windows 8 users claim this opens the door. The command bcdedit is the
Windows Boot Configuration Data.
BCD files provide a store that is used to describe boot applications and boot application settings. The objects and
elements in the store effectively replace Boot.ini.
BCDEdit is a command-line tool for managing BCD stores. It can be used for a variety of purposes, including creating new stores, modifying existing stores, adding boot menu options, and so on. BCDEdit serves essentially the same purpose as Bootcfg.exe on earlier versions of Windows, but with two major improvements:
BCDEdit exposes a wider range of boot options than Bootcfg.exe.
BCDEdit has improved scripting support.
BCDEdit is the primary tool for editing the boot configuration of Windows Vista and later versions of Windows. It is included with the Windows Vista distribution in the %WINDIR%\System32 folder.
BCDEdit is limited to the standard data types and is designed primarily to perform single common changes to BCD. For more complex operations or nonstandard data types, consider using the BCD Windows Management Instrumentation (WMI) application programming interface (API) to create more powerful and flexible custom tools.
Hi,
I have been able to 'master' HTC Desire, Xperia T, Xperia Z3C and even LG Optimus Black.
Except from HTC Desire (if you ever want to learn about ADB and Fastboot, use HTC Desire, the best) it is always a bit tricky to get into Fastboot mode.
I have found the easyest way to access Fastboot mode in this howto: https://goo.gl/hzyB2H
Simply stated:
- Enable USB debugging in Developer Options
- Install Minimal ADB and Fastboot from here: https://goo.gl/d5BSc7 or use the solid option using FWUL (see below)
- Open command window in Minimal ADB and Fastboot directory (Window Flag + right-click on the folder)
- Plugin your device (which is on)
- Type: adb devices and your device answers with its serial number.
- First answer is serial number and 'unauthorized'
- On your device you will see a popup like shown below
- Type: adb devices and your device answers with its serial number and device
- You're there
If you just need adb you can stop here, if you want to go on to fastboot, continue.
- Type: adb reboot-bootloader
- Type: fastboot devices
And you're there.
No more hassling around with Vol-Down and plugging in.
- Type: fastboot reboot to end the session nicely
Uninstall (system) apps using adb
Uninstall Sony Xperia 'What's New'
adb uninstall --user 0 com.sonymobile.entrance
Let's uninstall Facebook
- type: adb shell pm list packages | grep 'acebo' (I don't know if it spells with F or f) (see REMARK)
- You will receive an answer like:
com.facebook.katana
com.facebook.system
com.facebook.appmanager
- type: adb uninstall --user 0 com.facebook.katana etc.
- do the same for the other lines
- Done for the moment
- Check on your device. Goto settings->apps->Facebook and you will see 'uninstalled' behind it
- Reboot your device ( do it the adb way and issue the command <adb shell reboot>
- After the reboot you won't find Facebook anymore in the apps list
REMARK sometimes it is hard to find the name of the app you want to uninstall.
F.i. the app Playstation bears the name com.scee.psxandroid.
You can retrieve the name using the Play Store app Application Inspector
I had quite a lot of trouble with adb and Windows 10, the solution lies in using Linux.
Recently XDA senior member steadfasterX released “Forget Windows Use Linux” (FWUL) – a bootable GNU/Linux ISO geared specifically towards Windows users who need to communicate more reliably with Android. https://goo.gl/PxvS9p
If you want to play with adb then this is your chance.
Create a live CD or a bootable USB stick with FWUL and everything works like a charm. Forget Windows!
Remember:
Don't blame me if anything goes wrong.
Following these instructions is at your own risk.
And if.... then normally Xperia Companion is your friend.
Enjoy!
Picture shows an example
- how to find the location of an apk
- how to pull the apk to your computer
- how to uninstall the apk
- and the failure that shows that the apk is gone
You can use adb to record your phone screen
- adb shell screenrecord /sdcard/screenrecord.mp4
Stop with Ctrl-C
You can use adb to make a screenshot
- adb shell screencap -p /sdcard/screendump.png (-p stands for: create png file)
- adb pull /sdcard/screendump
alternative
- adb shell screencap -p > screendump.png (which sends the file to your computer)
ADB can be used to backup yout device (apk's and data)
- adb backup -f c:/backups/phonebackup.ab -all
- on the device you have to give permission
Of course you can restore the backup
- adb restore <filename>, but for restoring you need to have root access.
There are a lot of options, all explained elsewhere on XDA: https://goo.gl/KtVd1n
W10 is a bit tricky when it comes to running adb on your Xperia device.
To install the necessary drivers, follow this instruction:
To install the official Sony Xperia drivers you need to download them from here.
- Unpack the Zip file
- goto the directory
- right click on sarndis.if and click on install
To install the Flashtool drivers for Windows 8/8.1/10, please follow the steps below.
A) Press the Windows key + R together and in the ‘Run’ box type: shutdown.exe /r /o /f /t 00
– Now make the following selections to boot into the Start Up Setting Screen: Troubleshoot > Advanced options > Start Up Settings > Restart
– Then, when the machine restarts, select number 7 i.e. “Disable driver signature enforcement”. Your machine will start with Driver signing enforcement disabled until the next reboot.
B) Now you can install the Flashtool drivers.
– Windows will warn that the driver is not signed and will require you to confirm the installation.
– Once the installation is complete, reboot the machine.
This text is copied from Xperia blog
PS
Just adding another uninstall.
Using PiHole to block ads, people have noticed that on Android adds are not blocked.
More specific: Ads in Chrome on Android are not blocked.
Reason: Chrome denies your DNS settings
Solution:
adb uninstall --user 0 com.android.partnerbrowsercustomizations.chromeHomepage
From now on ads in Chrome on Android will be blocked as well.
Hi,
I am a real noob here, I have adb and fastboot. I would like to unlock my Z3 tablet compact bootloader. I have the code, it shows when I use the command adb devices but when I try fastboot devices I get not response. I'm not really sure what the issue is, can you help?
Did you try using Flashtool to unlock it? Never done it myself, but it seems pretty simple, and no command line required.
https://xperiafirmware.com/unlock-bootloader-sony-xperia/
sony xperia z3 no os installed android 6 bootloader cant be unlocked
hey guys my z3 has been soft bricked coz i flashed a system img that i extracted from its firmware i have tried to flash it using flashtool but it gives me this device connected with usb debbuging off 2011 make sure mtp is disabled
Use Flashtool to flash a stock .ftf file.
Disable the Driver signature enforcement on your PC by following these steps:
Open the Command Promt window by clicking the Start button, clicking All Programs, clicking Accesories, an the right clicking Command Prompt and select "Run as Administrator".
On the Command Prompt type enter the following command:
Code:
bcedit.exe /set nointegritychecks ON
This will disable the Digital Signature
Download Drivers for related tools
Install All Drivers provided and please click any prompt that mentions to Skip obtaining driver software from windows update
UnZip driver package(QUD.WIN.1.1 Installer-10030.1)
Run setup.exe as administrator setup.exe and Click next button step by step to finish.
Make sure device is powered off and battery is inserted
Press and hold the volumen up button. While the volumen up is being held coonect the device to your PC and continue holding the volumen up button until it shows a lightning bolt “flash”
If drivers are installed correctly, you should see a port called WinUsbDevice in the Device Manager (Start > My PC or Computer > Right Click > Manage > Device Manager)
Download and unZip FFUTools folder to the root of your Local Disk (C drive.
UnZip of software that you attemting to flash and inside the zipped software software file should be a file called Flash.FFU
The Flash.FFU file needs to be copied to C:\ffutool
Once the Flash.FFU file is copied to C:\ffutool double click the Flash FFU.bat file to start flashing the device.
A command prompt should be open and begin to flash your device.
Once the device is flashed, the device will power on by itself and you may closet he command prompt.
End.
Links dead please share elsewherr
Enviado desde mi SM-G930F mediante Tapatalk