Hi,
I really need some help on this one. I wiped everything using TWRP recovery in preparation of installing a custom ROM.
I then realised I forgot to transfer the custom rom to my phone! When I went to reboot the system it says "No OS installed! Are you sure you want to reboot?"
No it's stuck on the google logo.
Is there a way to see if any Rom is still installed on on my phone or if it deleted my stock rom also?
I tried to push the rom through adb but it says error read only.
Also USB debugging is not enabled but I can't boot to enable it.
Please help.
Thanks
Go into fastboot and ensure your fastboot devices command shows your s/n. If so then grab the stock image from xda and flash it.
fastboot flash bootloader BOOTLOADERNAME.img
fastboot reboot-bootloader
fastboot flash radio RADIONAME.img
fastboot reboot-bootloader
fastboot -w update IMAGENAME.zip
Alternatively, using ADB.
from command prompt: adb remount
adb push <FILE PATH> /sdcard/0/
Boot into recovery (I use CWM) and then install it.
Thanks for the quick reply.
I managed to solve it by using the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2010312
It's all in fastboot so I had no problems
Problem solved.
Related
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?
Tips & Guides About Moto G 2014 ADB and FastBoot
The most of people have problems with fastboot and ADB. Here will explain some tips and guides.
- Do u know can use ADB in recovery mode?
Yeah if u have bricked your phone or deleted system or can't put the Debug Mode have a alternative. This happens the Device ADB have two modes. The USB mode and Debugging Mode, using two different drivers. When you download Motorola Device Manager he installs the Debugging Drivers. In Motorola is really hard obtain the correct drivers.
- Can I flash zips with fastboot?
Yeah but isn't recommended the people try that:
- fastboot flash zip myzip.zip
This is incorrect he will try to flash a .IMG in a partition called zip.
- fastboot -I flash system myzip.zip
This is incorrect. When you download a ROM backup to flash in Recovery he have some partitions making that will create a partition into a partition. Bricking your device.
The correct way to flash ROM is in recovery.
- I can't transfer file on my device.. Can I flash?
Yes using two methods
- ADB push
You push to your device a .zip with the Rom eg.:
- adb push my file.zip /sdcard or /sdcard1
This will push your file to the device and you can after that flash in recovery.
Is normal after digit the command nothing happens. Differently fastboot the ADB doesn't shows progress of transfer.
- ADB side load
You can flash sideload the zip
Using adb sideload myzip.zip
Must enable sideload mode on your recovery.
- my device doesn't appear on the list.
When you are on boot loader mode the ADB doesn't runs. Only in recovery mode or system mode.
Most times you have incorrect drivers. But if u are on recovery mode try that on cmd:
adb kill-server
adb usb
This will enter the daemon service in USB mode.
- can I reboot my device in recovery? Yes, adb reboot recovery
- can I wipe my firmware with fastboot? Yes, using these cmds.
fastboot erase userdata
fastboot erase cache
- can I get my device info?
Yes with ADB.
adb get-imei
adb get-serialno
adb get-deviceno
If u have more questions write here. I will add on OP.
Downloads:
- Moto G drivers: https://mega.co.nz/#!IY0mUBDL!tukY40l9_GlYpJVuSxahYBXhDjXDBfhG-bfG0oIvEa8
- Minimal (really minimal) ADB & fastboot: https://mega.co.nz/#!NJUVlIwI!uiRi4UAdU-8ZKEeQ1gquGDYbSSG9rWIWeMElUcMD4e0
Impressive, n tnks for sharing
sent From My XT1068{LP} using TapatalK
plez help me
OEM unlock failure! :crying:
adel pro said:
OEM unlock failure! :crying:
Click to expand...
Click to collapse
Dont type UNIQUE_KEY in the command. Its just the syntax.
KrishnaSagar said:
Dont type UNIQUE_KEY in the command. Its just the syntax.
Click to expand...
Click to collapse
I totally did that before lol
adel pro said:
OEM unlock failure! :crying:
Click to expand...
Click to collapse
Hello tipe
fastboot oem unlock TheKey
But u can check if is unlocked in the boot loader is is status code 3
Ah.. If the unlock doesn't work:
fastboot oem get-unlock-data
Pick the code without the word (fastboot)
And put all the code in one line.
THE MOTOROLA PAGE DOESNT VALIDATE YOUR ENTERED CODE ONLY GENERATE A CODE WITH YOUR INPUT.
If u put a wrong code. He will generate a wrong code.
Cheers
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Flash Latest NON-HLOS.bin before flashing any volte ROM.
Flash through fastboot
File link
https://drive.google.com/file/d/0B8Vodzmhc0GlXzdtOUFjb29EOFU/view
Extract .zip
Copy NON-HLOS.bin in adb folder
Open command prompt here
Connect phone into fastboot mode
Type command
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Wait till process done.
Disconnect phone
Remove battery and insert again
Goto twrp recovery.
Install any volte enabled ROM.
Enjoy.:good:
OEM unlock command not found
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
nischait said:
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Click to expand...
Click to collapse
nithin1664 said:
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
Click to expand...
Click to collapse
Try without using 0x1ebf and report.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Yogesh1969 said:
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Click to expand...
Click to collapse
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
nischait said:
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
Click to expand...
Click to collapse
I couldnt find the ygdp version of Cynogen, any way I found a way from youtube which solved my problems.
Link : https://www.youtube.com/watch?v=2Gpz65r2pNM
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
For drivers problem install pdanet. And you can refer to the youtube video link (above post) if you want for all needs.
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
Getting your device connected is a very important stage, whether it is system,recovery or fastboot. From what I read , you can connsct through fasatboot, since you flashed cyanogen. Just flash TWRP 3.2.1 or so which is the latest, through fastboot:
fastboot flash recovery twrp.3.2.1 .img ( Remember the spaces, the name twrp.xxx.img should be same as you downloaded. If flash is successful, you can see twrp when you boot to recovery. Then flash supersu file and/or whichever rom you want.
Sorry for late answers.
I was lil busy and sorry for wrong address also.
You could get it from firmwarefile.com
I can't post link here but select yu yureka plus variant and download oldest CBP
Hi,
When my S7 Edge boots up it jumps to twrp but it's stuck on the teamwin logo screen and does not advance to menu.
This happened after I tried to format the data partition to ext4 via twrp and it just got stuck there too so when I rebooted it landed in this situation.
Unfortunately reflashing twrp or reflashing the stock rom via ODIN does not work as COM3 is recognized but then when I press start it doesnt do anything....
Also tried the suggestion I read online of:
fastboot format cache
fastboot format userdata
These commands just get stuck on <waiting for device>.
Also tried adb shell recovery --wipe_data but it gets stuck at I:LANG: en
Any help will be much appreciated!
Thanks
This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
redirts1978 said:
Hi,
When my S7 Edge boots up it jumps to twrp but it's stuck on the teamwin logo screen and does not advance to menu.
This happened after I tried to format the data partition to ext4 via twrp and it just got stuck there too so when I rebooted it landed in this situation.
Unfortunately reflashing twrp or reflashing the stock rom via ODIN does not work as COM3 is recognized but then when I press start it doesnt do anything....
Also tried the suggestion I read online of:
fastboot format cache
fastboot format userdata
These commands just get stuck on <waiting for device>.
Also tried adb shell recovery --wipe_data but it gets stuck at I:LANG: en
Any help will be much appreciated!
Thanks
Click to expand...
Click to collapse
HELP!!!! cant get my phone to be recogniced by adb, I have the same problem,
if its on TWRP boot screen or RECOVERY (blue downloading.... screen) its the same!!!
please help
redirts1978 said:
This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
Click to expand...
Click to collapse
i have exactly the same problem but cant boot to twrp or to OS ...only download mode...tried to flash twrp again not worked now try to flash stock firmware via odin ....PLEASE HELP ME
Kackwuerstchen said:
i have exactly the same problem but cant boot to twrp or to OS ...only download mode...tried to flash twrp again not worked now try to flash stock firmware via odin ....PLEASE HELP ME
Click to expand...
Click to collapse
I don't know what are you doing wrong but when I was stuck in this situation, I flashed stock firmware from sammobile and it fixed the problem.
Make sure you downloaded correct firmware.
Hi,
I know, its quite long time you solved this, but in which mode should be phone to use adb commands?
redirts1978 said:
This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
Click to expand...
Click to collapse
dankovac1999 said:
Hi,
I know, its quite long time you solved this, but in which mode should be phone to use adb commands?
Click to expand...
Click to collapse
Same problem and question here
I've a big problem, and I hope someone can help me
I wanted to change the rom, so I've rebooted my phone in recovery mode and executed a full wipe, after that I've updated TWRP, everything seemed to have gone well so i restarted my phone, but at this point it neither boot the rom(obviously, it is full wiped) nor the TWRP can start...
What can I do? I can only start the Fastboot screen...
How'd you update TWRP? If you did it through fastboot commands, you can just flash TWRP to the recovery partition, or boot it directly.
If you didn't do it through fastboot commands, you'll need to get that to fix it. Google has links to the latest android-tools for Windows and Linux on their Android site somewhere.
From there, you'll need TWRP (either official or codeworkx's), and then you use the flashboot executable to flash it: fastboot flash recovery TWRP.img
espionage724 said:
How'd you update TWRP? If you did it through fastboot commands, you can just flash TWRP to the recovery partition, or boot it directly.
If you didn't do it through fastboot commands, you'll need to get that to fix it. Google has links to the latest android-tools for Windows and Linux on their Android site somewhere.
From there, you'll need TWRP (either official or codeworkx's), and then you use the flashboot executable to flash it: fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Thanks, I solved reflashing it via ADB with fastboot command