While rooting my i9505 i ran into a little issue with adb.
Code:
List of devices attached
8e0fe3ad unauthorized
It didn't effect what i needed to do, but it did raise the question, how do i authorise and get adb access when booted into a ClockworkMOD based recovery?
Anyone know?
It's probably because it needs RSA authentication. You can do it by making sure USB debugging is enabled in developer options and running adb then tick the "always allow from this computer" check box. It then should work in ClockworkMod Recovery.
-=nezero=- said:
While rooting my i9505 i ran into a little issue with adb.
Code:
List of devices attached
8e0fe3ad unauthorized
It didn't effect what i needed to do, but it did raise the question, how do i authorise and get adb access when booted into a ClockworkMOD based recovery?
Anyone know?
Click to expand...
Click to collapse
first be sure that you have latest adb file version installed http://forum.xda-developers.com/showpost.php?p=45698254&postcount=9
when you are booted in os, enable usb debuging, connect your phone, open command prompt in adb folder(look at your phone screen, to allow adb) and type "adb devices"
now you can turn off usb debugging. boot into custom recovery and try the "adb device" command, it should recognize your phone in recovery mode.
Can't Load OS
samersh72 said:
first be sure that you have latest adb file version installed http://forum.xda-developers.com/showpost.php?p=45698254&postcount=9
when you are booted in os, enable usb debuging, connect your phone, open command prompt in adb folder(look at your phone screen, to allow adb) and type "adb devices"
now you can turn off usb debugging. boot into custom recovery and try the "adb device" command, it should recognize your phone in recovery mode.
Click to expand...
Click to collapse
What if you can't boot into your OS? I'm in CWM recovery, and I need to push a zip of my operating system to my phone, so I can have a bootable operating system. I'm bricked right now. Is there any way to authorize it in CWM?
mikechase3 said:
What if you can't boot into your OS? I'm in CWM recovery, and I need to push a zip of my operating system to my phone, so I can have a bootable operating system. I'm bricked right now. Is there any way to authorize it in CWM?
Click to expand...
Click to collapse
Just reflash the rom you are on. You don't need adb.
Lennyz1988 said:
Just reflash the rom you are on. You don't need adb.
Click to expand...
Click to collapse
I don't think I can do that, because I don't have any zips. I have a factory zip on my PC, and I simply need to get it on the phone. I can't find a image of CWM or TWRP for my Asus ZenPad S 8.0, but I found a script that temporarily flashes some version of CWM recovery to my phone. I have a custom recovery available for use, but now need some way to get my zip to my tablet so I can extract it. That's where I'm stuck. If ADB was authorized, I would just push the file and install it. Here's the options as I see them
1: Authorize RSA via CWM Recovery (Which is why I'm here..)
2: Find a version of CWM or TWRP or some other recovery compatible with my tablet, and try again. Hope it's more updated, and cross my fingers.
3: Use an external microSD card to move the zips. (Doesn't work. E:Can't mount /external_sd/. I tried FAT32 and tried formatting with a different android device which used exFAT. No luck)
4: Somehow fix operating system to approve RSA. (Safe mode failed)
I hate to say it, but I think the tablet may have won this war unless I'm missing something. Thanks for your help though! And Merry Christmas! I'll be over at XDA Assist...
@mikechase3: Some clarification needed here. What device are you trying to restore, and what brand? Your initial post doesn't mention, and your latest mentions an Asus device. If it is Asus, then the help we can provide is going to be limited, since this is a Samsung device forum.
Strephon Alkhalikoi said:
@mikechase3: Some clarification needed here. What device are you trying to restore, and what brand? Your initial post doesn't mention, and your latest mentions an Asus device. If it is Asus, then the help we can provide is going to be limited, since this is a Samsung device forum.
Click to expand...
Click to collapse
Hey! I didn't realize this was a Samsung Galaxy Forum. Sorry about that. Specifically, I'm referring to my Asus ZenPad S 8.0 CA, and I made a more detailed post over at XDA Assist here if you have time to take a look. Thanks a bunch!
@mikechase3: I can't reply to that thread as XDA frowns on doing so while it is located in XDA Assist, but regarding the MicroSD card, format it as FAT32 in your PC, using SDFormatter from sdcard.org, and then try using the card to load the file. This will be easiest to do if you have a laptop, but can be done on a desktop if you have a card reader.
Strephon Alkhalikoi said:
@mikechase3: I can't reply to that thread as XDA frowns on doing so while it is located in XDA Assist, but regarding the MicroSD card, format it as FAT32 in your PC, using SDFormatter from sdcard.org, and then try using the card to load the file. This will be easiest to do if you have a laptop, but can be done on a desktop if you have a card reader.
Click to expand...
Click to collapse
I figured it out. So I went through the forumn again on this forum. Somewhere, deep down, I saw a little tid-bit that said the sd card had to be less than 32gb. I was using a 64gb card, and that's probably why it didn't work. I also used the tool you recommended, so it could have been that too. I'm extracting the files now, but now I'm getting somewhere. I'll let you know how everything goes once I'm finished.
---------- Post added at 11:13 PM ---------- Previous post was at 10:36 PM ----------
@Strephon Alkhalikoi I fixed my problem, but it looks like I'm going to be returning it anyways. I was able to install the zips, but now I can't even boot up the device. It's a paperweight. Nothing is showing up on the display. No low-battery or even a boot logo, and I can't even access the bootloader anymore. I'll be returning it as a defective unit (even though I was so close!!!) I'll charge it overnight and see if anything happens, but that's a bummer. Thanks for all of your help and ideas! And Merry Christmas if you celebrate it. :good:
Related
Can anyone extend some help to a TF300T n00b?
I flashed the unofficial CM10 Jellybean ROM to my tf300t, and since the storage isn't working I can't move another ROM or even the stock firmware file to my SD card to flash. So, basically I'm stuck on the unofficial CM10 for now...
posted here because I can't post in the actual developement thread
just connect the tablet to a pc and copy the rom to the tablet. I dont rember if windows sees the internal storage. If it dosent linux should or you can install adb and push the file to /sdcard from your computer.
go here and dl the prog:
http://www.google.de/url?sa=t&rct=j...sg=AFQjCNG5sMnAkUGOfTZHgHJLFBARtdiyPg&cad=rja
extract it
boot into tecovery.
open the prog
choose the rom you like and push it to your tablet.
It is not possible to do it when you are in system, cause you cant write anything to the internal space.
mikaole said:
go here and dl the prog:
http://www.google.de/url?sa=t&rct=j...sg=AFQjCNG5sMnAkUGOfTZHgHJLFBARtdiyPg&cad=rja
extract it
boot into tecovery.
open the prog
choose the rom you like and push it to your tablet.
It is not possible to do it when you are in system, cause you cant write anything to the internal space.
Click to expand...
Click to collapse
I couldn't get the fast ADB pusher to work, nor the actual ADB. Fast pusher said it succeeded a few times but I couldn't find the new ROM on my SD card in CWM.
http://forum.xda-developers.com/showthread.php?t=1680570
Check here it has instructions on how to setup and use adb
MegaNoob said:
http://forum.xda-developers.com/showthread.php?t=1680570
Check here it has instructions on how to setup and use adb
Click to expand...
Click to collapse
looks promising. I hadn't been attempting to push the files while the tablet was in recovery because adb wouldnt recognize the tab when it was in recovery. I don't have my tablet cable, but I will try tomorrow morning. Thanks again.
ljungberg3 said:
looks promising. I hadn't been attempting to push the files while the tablet was in recovery because adb wouldn't recognize the tab when it was in recovery. I don't have my tablet cable, but I will try tomorrow morning. Thanks again.
Click to expand...
Click to collapse
if adb doesn't recognize the pad when it's in recovery, the drivers may not be installed correctly
paedz718 said:
if adb doesn't recognize the pad when it's in recovery, the drivers may not be installed correctly
Click to expand...
Click to collapse
I installed the drivers exactly as the guide directed, then tried using regular ADB, which didnt work. So I tried to use the ADB fast push and it didn't work either, under the "information" tab on the fast adb program it says
"Failed to mount as R/W"
is this a problem?
I got files to push via ADB, installation was aborted on the stock rom
I will try to find another stock rom to flash and update you guys. thanks for all the help so far
Can you still get to fastboot mode?
---------- Post added at 10:53 PM ---------- Previous post was at 10:44 PM ----------
If yes, dl the latest. Asus. STOCK, extract the blob, put it in the Fastboot Folder and. Open cmd
cd to the fastboot directory and write
fastboot -i 0x0B05 flash system blob
This will flash stock.
Don't give up, when it's not working. Just rewrite and try again and again.
A, user in the German Forum needed 20 times till it finally run through.
mikaole said:
Can you still get to fastboot mode?
---------- Post added at 10:53 PM ---------- Previous post was at 10:44 PM ----------
If yes, dl the latest. Asus. STOCK, extract the blob, put it in the Fastboot Folder and. Open cmd
cd to the fastboot directory and write
fastboot -i 0x0B05 flash system blob
This will flash stock.
Don't give up, when it's not working. Just rewrite and try again and again.
A, user in the German Forum needed 20 times till it finally run through.
Click to expand...
Click to collapse
I was able to push and flash a stock firmware! thank god! haha, and thank you guys for all the help!
ljungberg3 said:
I was able to push and flash a stock firmware! thank god! haha, and thank you guys for all the help!
Click to expand...
Click to collapse
Np
So, much of the stuff in this and other threads has been a tremendous help. I did pretty much exactly what OP did in this thread http://forum.xda-developers.com/showthread.php?t=1779080.
That thread lead me to this one, as I was having trouble getting my computer to recognize the usb drivers. I was able to finally get ADB to see the tablet, however, when I go to push the stock rom, I get an error message of "Protocol Failure" in cmd.
Any ideas?
http://s12.postimage.org/unt8ag1vh/adbcmd.jpg
Created new thread as OP solved his problem.
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
danman132x said:
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1781250
follow that guide, will get you back to stock then start again, and dont erase sd card next time! just factory reset to go from stock to CleanROM
danman132x said:
I just unlocked/rooted my Nexus 7. I downloaded CleanROM3.0, but before I wanted to flash it, I wiped everything. Now there is No Rom installed and my Clean ROM file is gone. I want to put it back on my device through TWRP but the mount to my PC is not working. I can see it in device manager, but it's unknown and no file explorer opens up for it. How can I get the file back on it??? Help please. Is there a driver I'm missing for it to mount properly in TWRP?
Click to expand...
Click to collapse
Put the ROM zip file in your Android SDK/platform-tools directory on your computer. Open a command prompt window, change directories to your Android SDK/platform-tools location (for me that's: cd sdk/platform-tools) and type in:
Code:
adb push <name of ROM zip> /sdcard
Wait about 30-60 seconds until it's done, then flash your ROM. It'll be on the root of your internal storage (/sdcard).
I think, you have to flash a factory image by using adb.
Sent from my Nexus 7 using xda premium
I'm in my bootloader and hooked up the USB cable. Trying to use adb, but the device is not showing up when trying to pull up the list of ADB devices. Starting to get worried now. Can't mount in TWRP, and now it can't find the device in my ADB. It found the device just fine when I had it booted up before while I was doing the unlock/root process.
Nico_60 said:
I think, you have to flash a factory image by using adb.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
danman132x said:
I'm in my bootloader and hooked up the USB cable. Trying to use adb, but the device is not showing up when trying to pull up the list of ADB devices. Starting to get worried now. Can't mount in TWRP, and now it can't find the device in my ADB. It found the device just fine when I had it booted up before while I was doing the unlock/root process.
Click to expand...
Click to collapse
You need to use fastboot commands to flash .img files via the bootloader. Try typing in:
Code:
fastboot devices
Please review this thread: http://forum.xda-developers.com/showthread.php?t=1907796
RMarkwald said:
You need to use fastboot commands to flash .img files via the bootloader. Try typing in:
Code:
fastboot devices
Please review this thread: http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I am having the same problem, but with a Kindle Fire 2. When I wiped, it took out my new Rom, and I cannot mount in TWRP...
And, it won't boot the stock ROM. To make matters worse, I cannot see the device in ADB!
Joe
yudanjah said:
I am having the same problem, but with a Kindle Fire 2. When I wiped, it took out my new Rom, and I cannot mount in TWRP...
And, it won't boot the stock ROM. To make matters worse, I cannot see the device in ADB!
Joe
Click to expand...
Click to collapse
You should ask in the kindle fire 2 forums as some advice may be hardware specific.
Hi there.
I have a Nexus 4 with a failed root through Nexus 4 Root toolkit.
The toolkit unlocked the bootloader with no problems but it failed at applying SuperSU-v1.45.zip through ADB through CWM
I am pretty certain that this process failed because I did not Enable USB debugging before starting.
So, I think the question I want to ask is: Is it possible to Enable USB debugging so I can apply perform adb sideload SuperSU-v1.45.zip
Do I have any other options? At present the device won't boot into Android OS. The states I currently have are either
1. fast boot mode
and then Recovery Mode -> CWM
2. Just a black screen, the Google logo, and an unlocked padlock
Any pointers would be greatly appreciated
Thanks!
jon.
Why CWM? TWRP is a lot better.
And Android USB debugging has no job in recovery so it isn't necessary if you're sideloading
Oh, and a few extra bits of info:
* I am on a mac
* I am pretty sure it's the adb ruining the party because when I do this:
(null) latform-tools jonwhittlestone$ adb devices
List of devices attached
(null) latform-tools jonwhittlestone$
Ahh thanks Lawstorant. Maybe my question isn't warranted then, or I'm barking up the wrong tree with ADB/USB debugging. Needless to say, I didn't enable it and surely this is not going to stop me rooting?
How can I get replace CWM with TWRP bearing in mind I can't get into the OS anymore - I'm a total Android root newbie as of this morning?
jonwhittlestone said:
Ahh thanks Lawstorant. Maybe my question isn't warranted then, or I'm barking up the wrong tree with ADB/USB debugging. Needless to say, I didn't enable it and surely this is not going to stop me rooting?
How can I get replace CWM with TWRP bearing in mind I can't get into the OS anymore - I'm a total Android root newbie as of this morning?
Click to expand...
Click to collapse
You shouldnt have used a toolkit.
Anyways, i think that you are misunderstanding this. You DO NOT need usb debugging enabled for adb to work while in a custom recovery. Adb works by default in a custom recovery.
I would suggest pushing a rom onto your phone (download a rom on your mac, put the phone into cwm, and run "adb push rom.zip /sdcard/").
After that go back to the phone and choose: wipe data/factory reset, wipe cache partiiton, advanced> wipe dalvik cache. Then go to install zip from sdcard and install the rom that you just pushed.
*Download the newest TWRP .img file from TWRP website
*Rename it to recovery.img to get rid of that long name
*Go into bootloader but don't choose anything (fastboot mode)
*In ADB type: fastboot flash recovery file_location/recovery.img
Sideloading in TWRP is in Advanced menu
consonant edbreach
Chromium_ said:
You shouldnt have used a toolkit.
Click to expand...
Click to collapse
Thanks Chroumium_, the procedure is becoming clearer. I should have known better to use a toolkit for sure.
I had actually followed Lawstorant's advice and put on twsrp, nevertheless - when I try to push a zip with adb, I get the following
(null)latform-tools jonwhittlestone$ adb push cm-10.2-20130815-rootandboot-mako.zip /sdcard/
error: device not found
Is this because I don't have the correct Nexus 4 drivers? The way I've always handled File transfers is with Android File Transfer so presumably I have go the correct drivers.
I am guessing if I had removable media, I could have put the zip on that...
jonwhittlestone said:
Thanks Chroumium_, the procedure is becoming clearer. I should have known better to use a toolkit for sure.
I had actually followed Lawstorant's advice and put on twsrp, nevertheless - when I try to push a zip with adb, I get the following
(null)latform-tools jonwhittlestone$ adb push cm-10.2-20130815-rootandboot-mako.zip /sdcard/
error: device not found
Is this because I don't have the correct Nexus 4 drivers? The way I've always handled File transfers is with Android File Transfer so presumably I have go the correct drivers.
I am guessing if I had removable media, I could have put the zip on that...
Click to expand...
Click to collapse
Im pretty sure that mac doesnt require any drivers to be installed. Try running these commands first:
Code:
adb kill server
adb start server
Also make sure that your adb is up to date (using the sdk manager). If its still not working try other usb ports or cables if you have any.
At this point adb is the only way to move the zip onto the phone, since the nexus 4 doesnt not support usb mass storage.
Chromium_ said:
Im pretty sure that mac doesnt require any drivers to be installed. Try running these commands first:
Code:
adb kill server
adb start server
Also make sure that your adb is up to date (using the sdk manager). If its still not working try other usb ports or cables if you have any.
At this point adb is the only way to move the zip onto the phone, since the nexus 4 doesnt not support usb mass storage.
Click to expand...
Click to collapse
Thanks to both - I've now solved and rooted
I reflashed with the stock google image
Followed androidpolice.com/2013/07/24/how-to-flash-your-nexus-4-to-android-4-3-jwr66v-and-root-it-right-now/
And - got the official TRSW from Gooapps on the Market
Flashed the SU update using the shell script - all details in the link above.
current supersu is 1.65
Can i enable usb debugging via locked phone [pin screen lock]
ok so i have a phone its an lg k5 or in mexico lg q6 a friend has asked me to unlock it with out doing any kind of hard reset or format so he he can access the pictures and other things on the phone since it belongs to his brother who passed away. anyways does anybody know of any way i can enable usb debugging so i can reset the lock screen via ADB ?? or maybe some other way?
Hello.
I was attempting to install a new KitKat ROM. The installation failed, and now the phone only sits at the Samsung boot logo. Since I downloaded the ROM using my phone, I figured the download was corrupt.
I put my phone into recovery to sideload a new ROM .zip downloaded from my pc.
Computer gives me a USB error sound
In device manager on windows, the phone displays as "SAMSUNG_Android" with an exclamation point.
I have correct drivers installed, computer recognizes when its not in recovery mode.
So if anyone could explain why it isn't being recognized it would be of great help!
Also, if I tried to mount the device as USB from recovery I get this
"E: Unable to mount '/usb-otg' "
I assumed that had something to do with it not being recognized.
I Googled this for about an hour and a half now... few people are having this with even fewer people responding to help. I may just be awful at searching though...
I assume you have a custom recovery? If so, boot into recovery and restore a nandroid
jd1639 said:
I assume you have a custom recovery? If so, boot into recovery and restore a nandroid
Click to expand...
Click to collapse
Yeah I forgot to make one... And formatted previous ones a while back...
INSM Sin said:
Yeah I forgot to make one... And formatted previous ones a while back...
Click to expand...
Click to collapse
Well, lesson learned, always have a nandroid. If you have kies, uninstall it then reinstall your usb drivers. You know you have to push a rom onto the device, now you need to figure out how to get the device recognized on your pc.
jd1639 said:
Well, lesson learned, always have a nandroid. If you have kies, uninstall it then reinstall your usb drivers. You know you have to push a rom onto the device, now you need to figure out how to get the device recognized on your pc.
Click to expand...
Click to collapse
Deleting Kies as we speak. I did manage to get windows to recognize it while its in recovery. Now, after attempting adb sideload "filename" I get
"failed to write data 'protocol fault <no status>'" in command prompt.
And yes... lesson learned.
Hi am looking for custom Rom for my 9020a trek 2 HD device. Seeing on how to install it on a my device that isn't working. Can it be done on laptop or is a SD micro memory card needed. Thanks
Johnlock777 said:
Hi am looking for custom Rom for my 9020a trek 2 HD device. Seeing on how to install it on a my device that isn't working. Can it be done on laptop or is a SD micro memory card needed. Thanks
Click to expand...
Click to collapse
For flashing custom rom you need custom recovery installed on your android or rom package in your android internal storage or in sd card
Ashwinrg said:
For flashing custom rom you need custom recovery installed on your android or rom package in your android internal storage or in sd card
Click to expand...
Click to collapse
Hi thanks for the reply. How is done and can it be done on a device that won't boot up. I cleared the cache and tried factory reset. But doesn't go past the powered by android screen. Says on that screen until it goes off or i hold the home button for ten seconds.
Johnlock777 said:
Hi thanks for the reply. How is done and can it be done on a device that won't boot up. I cleared the cache and tried factory reset. But doesn't go past the powered by android screen. Says on that screen until it goes off or i hold the home button for ten seconds.
Click to expand...
Click to collapse
What did you do to the device before you cleared cache and factory reset, something you did caused this. The best/easiest way to fix it depends on what you did.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
What did you do to the device before you cleared cache and factory reset, something you did caused this. The best/easiest way to fix it depends on what you did.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Was uninstalling apps from twrp manager because since I rooted the device was very slow. I accidentally uninstalled a system file. After it uninstalled froze wouldn't do anything. I hold power button and turned off and been in current state. Won't do anything but stay on the powered by android screen. Does this even after a factory reset roboot device. Am thinking without putting a clockwork mod on device because I can't access googleplay on the device. Custom recovery for installing a custom rom. Nothing I can do to fix the device. I sent the device to manufacturer for repair and sent it back was unrepairable. Even knowing they could of put the stock system on the device. No clue what to do next.
Johnlock777 said:
Was uninstalling apps from twrp manager because since I rooted the device was very slow. I accidentally uninstalled a system file. After it uninstalled froze wouldn't do anything. I hold power button and turned off and been in current state. Won't do anything but stay on the powered by android screen. Does this even after a factory reset roboot device. Am thinking without putting a clockwork mod on device because I can't access googleplay on the device. Custom recovery for installing a custom rom. Nothing I can do to fix the device. I sent the device to manufacturer for repair and sent it back was unrepairable. Even knowing they could of put the stock system on the device. No clue what to do next.
Click to expand...
Click to collapse
Does your PC even recognize the device? Does it show anything device manager?
Have you tried anything by searching for:
"How to unbrick (your model number)"
Have you tried connecting to adb while the device is in bootloop, you may have to create some sort of script to run in adb to echo and interrupt boot cycle while in bootloop to stay connected to adb, if you can get it to accept adb commands, you can try adb pushing copies of the apps you removed or maybe even push a copy of your stock system.img with a dd command, just make absolutely sure that use the correct command to dd the .img to the correct partition(mmcblk0) on your internal sd.
If your device is a fastboot device you can use adb to get to fastboot and flash the device.
There is also the possibility that you can use the stock firmware for your device or a .img dumped from another rooted device like yours to create or pull an .img that can be "burned" to a micro sd card to create a type of "boot disk" that will boot your device from extsdcard and then use that to restore the device. I don't know the software and methods to achieve this on your specific device, I'm just telling you the different tricks that can be used to restore a device.
These are just possibilities.
Droidriven said:
Does your PC even recognize the device? Does it show anything device manager?
Have you tried anything by searching for:
"How to unbrick (your model number)"
Have you tried connecting to adb while the device is in bootloop, you may have to create some sort of script to run in adb to echo and interrupt boot cycle while in bootloop to stay connected to adb, if you can get it to accept adb commands, you can try adb pushing copies of the apps you removed or maybe even push a copy of your stock system.img with a dd command, just make absolutely sure that use the correct command to dd the .img to the correct partition(mmcblk0) on your internal sd.
If your device is a fastboot device you can use adb to get to fastboot and flash the device.
These are just possibilities.
Click to expand...
Click to collapse
It will show on laptop like serial number unavailable but keeps saying USB needs to be debugged but can't because I can't access developer settings on device. I haven't search unbricked with model number. Didn't know what bricked met. I screenshot options with what I have on device. Have no clue on commands and how to do this?
Johnlock777 said:
It will show on laptop like serial number unavailable but keeps saying USB needs to be debugged but can't because I can't access developer settings on device. I haven't search unbricked with model number. Didn't know what bricked met. I screenshot options with what I have on device. Have no clue on commands and how to do this?
Click to expand...
Click to collapse
Do a Google search for:
"USB drivers for (your model number)"
Make sure you get those fully installed.
Then do a Google search for:
"adb/fastboot 15 second installer for windows"
If you have issues getting it installed and working correctly, just do a Google search for:
"How to setup adb/fastboot on windows"
There should be many guides to follow, once you're set up, boot to recovery to the menu in your screenshot, select "reboot bootloader", that will probably boot you to fastboot mode, then connect to PC
Open a cmd prompt, in that terminal type:
fastboot devices
Press enter, if it returns a serial number you're connected, from there you can fastboot flash your stock firmware.
To understand fastboot flashing, do a Google search for:
"How to fastboot flash stock firmware (your model number)"
Droidriven said:
Do a Google search for:
"USB drivers for (your model number)"
Make sure you get those fully installed.
Then do a Google search for:
"adb/fastboot 15 second installer for windows"
If you have issues getting it installed and working correctly, just do a Google search for:
"How to setup adb/fastboot on windows"
There should be many guides to follow, once you're set up, boot to recovery to the menu in your screenshot, select "reboot bootloader", that will probably boot you to fastboot mode, then connect to PC
Open a cmd prompt, in that terminal type:
fastboot devices
Press enter, if it returns a serial number you're connected, from there you can fastboot flash your stock firmware.
To understand fastboot flashing, do a Google search for:
"How to fastboot flash stock firmware (your model number)"
Click to expand...
Click to collapse
I took screenshot of what I get when device is connected to PC. But can't find the USB drivers for this device online. Didn't continue the steps you provided because of that.
You can delete or close thread. With everything I heard there was no hope in fixing the device. So I destroyed it and tossed it. Thanks for advice appreciated it.
A little late now but since I saw that you could boot recovery, so the easy fix would have been using jasminetool with edl to install a custom recovery(twrp ). Once twrp is installed its just simple enough towipe system partition and flash a stock ROM or flash a custom ROM and get it working again. This is a fix For anyone else who messes up there system partition.