Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
Hi mates,
My TF300t(unlocked) is bricked:crying: Im only able to go into TWRP(2.6.3) but i can't go into the bootloader(for using fastboot and co)
BTW, there is no Rom installed, so if i start the tablet (no matter if i press Power+Vol Down or not) i allays end in TWRP.
My TWRP is also "buggy". It has some problems, like: Unable to mount... / Unable to set emmc bootloader message.... / unable to find partition size for xyz.... So i cant use TWRP to flash/install something and factory resets didnt work.
There are a lot of good guides how to UNBrick the tf300t, but they all need fastboot. Does someone knows how i could Fix fastboot with ADB? ADB is working fine. Maybe i can use ADB to fix TWRP or even better Fastboot.
Sry for my bad english, please help my
Have you tried
adb reboot-bootloader
?
alponte said:
Have you tried
adb reboot-bootloader
?
Click to expand...
Click to collapse
Thanks to you, it worked!!! with adb i could killed TWRP and after i used this:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
After:
fastboot -i 0x0B05 flash system blob
now i back in Asus Stock rom, and i will stay there^^
THX
Access via adb on twrp 2.4.4.0
Hi folks - time to activate an really old post
I do have also problems like manckosy in 2014:
The TF300t I have here has TWRP 2.4.4.0:
- Android booting is not possible
- it's not possible to mount SD-Card
- I don't have the permission to enter the tab via adb
Does anyone of you have an idea how I can get access with adb?
Thx a lot in advance!
f_lux said:
Does anyone of you have an idea how I can get access with adb?
Click to expand...
Click to collapse
Yes, I do! Hopefully you have "Minimal ADB and Fastboot" installed on your PC.
First of all, check whether you are able to reach fastboot protocol by pressing Power and Volume down together. Fastboot protocol should appear. That means now you have ADB access via USB and you will find further help here: https://forum.xda-developers.com/sho....php?t=2179759.
ebonit said:
Yes, I do! Hopefully, you have "Minimal ADB and Fastboot" installed on your PC.
First of all, check whether you are able to reach fastboot protocol by pressing Power and Volume down together. Fastboot protocol should appear. That means now you have ADB access via USB and you will find further help here: https://forum.xda-developers.com/sho....php?t=2179759.
Click to expand...
Click to collapse
I Have a similar problem and the link above goes to a 404 page.
In my case, My Tablet boots directly to the TWRP splash screen, and freezes. I can get status and serial number via ADB, but that's all.
If I try to reboot (via ABD) I get no response.
The device appears on Windows10 devices list, but Fastboot can't see it (I get that "<waiting for device>" message). I guess that my TWRP is damaged somehow, only part of the ADB protocol is getting up.
That happened when I tried to clean up the cache and ended up messing it all up.
The Status on ADB says that the tablet is on recovery mode.
Is there a way of flashing TWRP with ADB only? Or it is bricked forever?
Thanks for any help
mau0968 said:
I Have a similar problem and the link above goes to a 404 page.
Click to expand...
Click to collapse
Sorry for the dead link. Here we go: https://forum.xda-developers.com/showthread.php?p=44244313#post44244313
Please note if you cannot reach fastboot or recovery, your device is bricked for good!
Hello everyone, I urgently need help, brought this tablet to repair, hangs on the download logo, does not start any further, customers do not have a cable to connect to the computer, I have tried all possible ways to download recovery, fastboot, and indeed where Either it does not give out, a permanent download logo, tell me who knows what, maybe I'm doing it wrong
Hi everybody,
So, there is my problem, I bought the nexus 5 in November. I rooted it.
And the last wednesday, while using my phone, the power button decided to not respond anymore.
The phone still worked but two days ago the batery became empty and now I can just go in the "bootloader menu" and the "download mode".
Google accepted to replace my phone, but I really want to save my files. And like you certainly know we can't save our files with the phone Off.
But my phone is detected in this two modes.
I installed the nexus driver but I still can't open my files.
I pretty sure there is a way to save my files, I searching and trying but nothing work, I would open my phone if I can activate the power button manually but I don't know how.
If you have any solution, I'll take it.
Per-haps the ADB can help me ? But I don't know how to use it.
Thanks a lot for reading.
Have a good day !
Ps : I'm new here please be gentle if I don't understand directly
And sorry for my poor english.
PeauMorte said:
Hi everybody,
So, there is my problem, I bought the nexus 5 in November. I rooted it.
And the last wednesday, while using my phone, the power button decided to not respond anymore.
The phone still worked but two days ago the batery became empty and now I can just go in the "bootloader menu" and the "download mode".
Google accepted to replace my phone, but I really want to save my files. And like you certainly know we can't save our files with the phone Off.
But my phone is detected in this two modes.
I installed the nexus driver but I still can't open my files.
I pretty sure there is a way to save my files, I searching and trying but nothing work, I would open my phone if I can activate the power button manually but I don't know how.
If you have any solution, I'll take it.
Per-haps the ADB can help me ? But I don't know how to use it.
Thanks a lot for reading.
Have a good day !
Ps : I'm new here please be gentle if I don't understand directly
And sorry for my poor english.
Click to expand...
Click to collapse
Hoping you have enabled the usb debugging you can indeed backup through adb: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
Can you enter into recovery mode from the bootloader menu?
Primokorn said:
Hopping you have enabled the usb debugging you can indeed backup through adb: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
Can you enter into recovery mode from the bootloader menu?
Click to expand...
Click to collapse
The usb debugging is enabled I hope too, I'll try it immediatly, thanks you.
But I can't enter in any thing in that menu.
PeauMorte said:
The usb debugging is enabled I hope too, I'll try it immediatly, thanks you.
But I can't enter in any thing in that menu.
Click to expand...
Click to collapse
You can use a fastboot command to boot into recovery: fastboot boot path/to/TWRP.img if you have TWRP Recovery.
Then you will be able use to use adb commands to backup your data.
Primokorn said:
You can use a fastboot command to boot into recovery: fastboot boot path/to/TWRP.img if you have TWRP Recovery.
Then you will be able use to use adb commands to backup your data.
Click to expand...
Click to collapse
Hmm, Have I to start eclipse ? Where can I find the "sdk platform" ?
I found a folder who have that name but nothing happens when I run the exe files.
And in eclipse nothing had that name.
Edit : Sorry I did'nt understand before. I'm trying your command in this folder, but it say me that there is no such files in this directory. Could you explain me ?
Edit 2 : Okay I have to read better i guess, I don't have TWRP, I'm downloading it, could you just explain me a little how does it work ?
Edit 3 : With the command "adb devices" I can't see my phone :/ Have I to surrender ?
PeauMorte said:
Hmm, Have I to start eclipse ? Where can I find the "sdk platform" ?
I found a folder who have that name but nothing happens when I run the exe files.
And in eclipse nothing had that name.
Edit : Sorry I did'nt understand before. I'm trying your command in this folder, but it say me that there is no such files in this directory. Could you explain me ?
Edit 2 : Okay I have to read better i guess, I don't have TWRP, I'm downloading it, could you just explain me a little how does it work ?
Edit 3 : With the command "adb devices" I can't see my phone :/ Have I to surrender ?
Click to expand...
Click to collapse
1. First off, you have to install and set up adb & fastboot on your PC. Here is a great tutorial: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
However you can use this tool instead: http://forum.xda-developers.com/showthread.php?t=2588979
2. To boot into recovery mode from bootloader, connect your phone to PC then enter this command into cmd:
fastboot devices (check if your N5 is connected otherwise)
fastboot boot path/to/TWRP.img (you can download the latest TWRP img from this website)
Primokorn said:
1. First off, you have to install and set up adb & fastboot on your PC. Here is a great tutorial: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
However you can use this tool instead: http://forum.xda-developers.com/showthread.php?t=2588979
2. To boot into recovery mode from bootloader, connect your phone to PC then enter this command into cmd:
fastboot devices (check if your N5 is connected otherwise)
fastboot boot path/to/TWRP.img (you can download the latest TWRP img from this website)
Click to expand...
Click to collapse
With the two methods, no devices are found. But when I try with an other phone, nothing is dected too (debug mod enabled).
I tried to remove driver and update with all sources but nothing apparently work per-haps my debug mode is disabled ? ...
Edit :
Okay fastboot device detected my phone !
The guaranty will stop if I use the second command ?
And last thing, where I need to put the img ?
Thanks a lot I looking at the end of that problem *o*
PeauMorte said:
With the two methods, no devices are found. But when I try with an other phone, nothing is dected too (debug mod enabled).
I tried to remove driver and update with all sources but nothing apparently work per-haps my debug mode is disabled ? ...
Edit :
Okay fastboot device detected my phone !
The guaranty will stop if I use the second command ?
Click to expand...
Click to collapse
Nope because you only BOOT and not FLASH TWRP.img. Actually I say TWRP because I have this recovery but I think you can use this command with the stock recovery. You just have to use recovery.img file from the factory images instead of TWRP.img.
---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------
PeauMorte said:
And last thing, where I need to put the img ?
Thanks a lot I looking at the end of that problem *o*
Click to expand...
Click to collapse
Put the file into your platform-tools folder (where you have fastboot.exe file)
Primokorn said:
Nope because you only BOOT and not FLASH TWRP.img. Actually I say TWRP because I have this recovery but I think you can use this command with the stock recovery. You just have to use recovery.img file from the factory images instead of TWRP.img.
---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------
Put the file into your platform-tools folder (where you have fastboot.exe file)
Click to expand...
Click to collapse
Okay, nice !
But I put the twrp.img in the adb folder, but it doeasn't found the file, where i need to put it ?
path/to means what ?
PeauMorte said:
Okay, nice !
But I put the twrp.img in the adb folder, but it doeasn't found the file, where i need to put it ?
path/to means what ?
Click to expand...
Click to collapse
Did you rename the downloaded file to "TWRP.img"? The file name must be the same into your command prompt.
Copy TWRP.img into your platform-tools folder then open a command prompt from this folder and enter: fastboot boot TWRP.img
The path is the directory of your file you want to use. If you open the command prompt from the folder you have TWRP.img (platform-tools) then you don't need to mention the path.
I think the bootloader needs to be unlocked first for "fastboot boot twrp.img" to work? Isn't it? If unlocking wasn't necessary, everyone would've just booted recoveries to root their phones. (so that the sdcard doesn't get erased).
I sincerely doubt that the OP has an unlocked bootloader.
vin4yak said:
I think the bootloader needs to be unlocked first for "fastboot boot twrp.img" to work? Isn't it? If unlocking wasn't necessary, everyone would've just booted recoveries to root their phones. (so that the sdcard doesn't get erased).
I sincerely doubt that the OP has an unlocked bootloader.
Click to expand...
Click to collapse
Actually I never tried fastboot boot command on a locked bootloader. If it requires an unlocked bootloader and OP has a locked one I have no idea to recover his data.
Primokorn said:
Actually I never tried fastboot boot command on a locked bootloader. If it requires an unlocked bootloader and OP has a locked one I have no idea to recover his data.
Click to expand...
Click to collapse
Please guy ! You're a genius !
I love you !
I just used the reboot comand and my phone goes On !
Now I can back up my files
(Ps : For the people who'll have the same problem, you have to use your charger with you're computer and keep pressing the volume down while putting the charger in the phone to go in boot menu, but be carfully, you can't shutdown after that only solution, remove batery !)
:fingers-crossed:
PeauMorte said:
Please guy ! You're a genius !
I love you !
I just used the reboot comand and my phone goes On !
Now I can back up my files
(Ps : For the people who'll have the same problem, you have to use your charger with you're computer and keep pressing the volume down while putting the charger in the phone to go in boot menu, but be carfully, you can't shutdown after that only solution, remove batery !)
:fingers-crossed:
Click to expand...
Click to collapse
Happy for you... and your data
Primokorn said:
Happy for you... and your data
Click to expand...
Click to collapse
I'll just ask a last question because you're a super user of twrp, the back up fonctionality could work if I use it on this phone and the put it in my new nexus sent by google ?
Thanks a lot again and have a good day, you made mine.
PeauMorte said:
I'll just ask a last question because you're a super user of twrp, the back up fonctionality could work if I use it on this phone and the put it in my new nexus sent by google ?
Thanks a lot again and have a good day, you made mine.
Click to expand...
Click to collapse
Yes, you can! Just make sure you don't restore the /efs partition which contains the imei and other files which are unique to every device!
- Sent from an IceCold Hammerhead!
Hi guys,
I have a rooted Device with CM and TWRP installed, but someting happenend using the device and my Moto G got stuck on startup logo and Recovery TWRP logo, with adb I have acess to adb shell but everything else like adb reboot bootloader etc doesn't seems to work, with adb shell I have realized that the TWRP wasn't running 'cause when I use the interface on shell I get this message
$twrp wipe cache
"TWRP does not appear to be running. Waiting for TWRP to start"
Is there any way to install a new recovery via adb shell or reinstall a new rom, factory reset or something like that to make my cellphone work again?
Thanks,
If you are okay to wipe internal storage, the following fastboot command will probably make TWRP load again:
fastboot erase userdata
fastboot flash recovery newrecovery.img - is a way to reflash recovery, however the above command may still be required.
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
gconsentini said:
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
Click to expand...
Click to collapse
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
lost101 said:
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
Click to expand...
Click to collapse
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
gconsentini said:
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
Click to expand...
Click to collapse
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
lost101 said:
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
Click to expand...
Click to collapse
Sorry, I'm using Windows 10, if I use only wipe data, the command wipe is not reconigzed.
Can you enter fastboot mode by holding vol down and powering phone on?
lost101 said:
Can you enter fastboot mode by holding vol down and powering phone on?
Click to expand...
Click to collapse
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
gconsentini said:
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
Click to expand...
Click to collapse
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
lost101 said:
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
Click to expand...
Click to collapse
Yes, I thought about that too =x
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
gconsentini said:
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
Click to expand...
Click to collapse
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
thomasswan5547 said:
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
Click to expand...
Click to collapse
Install the Minimal Fastboot & ADB package and the Motorola USB drivers, use the mfastboot package and install the stock ROM as per the instructions provided, but ignore the disassembly part, unless you have your phone does not respond to keypresses.
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
so my mi4i is stuck in boot loop i flashed the stock firmware miui 6 using miflash . my volume down buttons dead so i cant use it to boot in fastboot . i could go in recover (stock ) at best .
You can use adb commands to boot into fastboot mode. Check Google for instructions.
hell1134 said:
You can use adb commands to boot into fastboot mode. Check Google for instructions.
Click to expand...
Click to collapse
kanishk @Mi4i said:
so my mi4i is stuck in boot loop i flashed the stock firmware miui 6 using miflash . my volume down buttons dead so i cant use it to boot in fastboot . i could go in recover (stock ) at best .
Click to expand...
Click to collapse
According to what he said open a terminal and type adb reboot-bootloader
But u must have adb drivers installed. But without booting into Android I don't think ADB will work
If this does not work try booting into recovery and check if ADB works. Good luck!
sharan.nyn said:
According to what he said open a terminal and type adb reboot-bootloader
But u must have adb drivers installed. But without booting into Android I don't think ADB will work
If this does not work try booting into recovery and check if ADB works. Good luck!
Click to expand...
Click to collapse
thanks .
PC can read my internal storage when i reboot to recovery mode [[in this case i'm using TWRP, i'm not sure whether stock recovery is readable too]] as long as the usb driver have installed on my PC .
Try it, if you can acces your internal storage on your PC, you can download your device ROM and flash it via recovery .