Develop Bugs

bricked fire phone need help sideloading by adb

some how i bricked my fire phone i still can get into stock recovery tryed side loading the update with adb but my computer keeps freezing the version im trying to flash is the 4.6.3 the same one my phone had, should i try updating using a 4.6.4 version or why does me computer keep freezing need help thx

C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-juniper-35.
4.6.3_user_463001420.bin
loading: 'update-kindle-juniper-35.4.6.3_user_463001420.bin'
* cannot read 'update-kindle-juniper-35.4.6.3_user_463001420.bin' *
C:\Program Files\Minimal ADB and Fastboot>adb sideload update.bin
loading: 'update.bin'
* cannot read 'update.bin' *

aamszia said:
C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-juniper-35.
4.6.3_user_463001420.bin
loading: 'update-kindle-juniper-35.4.6.3_user_463001420.bin'
* cannot read 'update-kindle-juniper-35.4.6.3_user_463001420.bin' *
C:\Program Files\Minimal ADB and Fastboot>adb sideload update.bin
loading: 'update.bin'
* cannot read 'update.bin' *
Click to expand...
Click to collapse
1. Try to run from folder without spaces (rename "Minimal ADB and Fastboot" to adb and move to C
2. After this, run cmd as administrator, and run command "adb devices". Do You see your device?

aamszia said:
[...] * cannot read 'update.bin' *
Click to expand...
Click to collapse
Are you using a PC with Windows OS (is it Windows 10, specifically)?
If so, please make sure that your device is listed as MahmudS already mentioned.
Take a look at this guide, if you need help with ADB related problems, drivers, etc...
Fire Phone ADB setup - an illustrated guide

Bingo Bronson said:
Are you using a PC with Windows OS (is it Windows 10, specifically)?
If so, please make sure that your device is listed as MahmudS already mentioned.
Take a look at this guide, if you need help with ADB related problems, drivers, etc...
Fire Phone ADB setup - an illustrated guide
Click to expand...
Click to collapse
i am using WIN XP and 7 .. same error ...
let me look at your link ..
---------- Post added at 03:00 PM ---------- Previous post was at 02:53 PM ----------
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
B0F10701425404HT sideload
C:\Program Files\Minimal ADB and Fastboot>adb sideload update-fire-phone-33.4.6.
1_user_461013320.bin
loading: 'update-fire-phone-33.4.6.1_user_461013320.bin'
* cannot read 'update-fire-phone-33.4.6.1_user_461013320.bin' *
C:\Program Files\Minimal ADB and Fastboot>
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
my phone is connecting perfectly via ADB .. but the BIN is not reading by CMD ..

aamszia said:
my phone is connecting perfectly via ADB .. but the BIN is not reading by CMD
Click to expand...
Click to collapse
If you have the BIN files in the "Minimal ADB and Fastboot" folder, try renaming them to something simple like "update.bin".
Maybe check the MD5 sum of the downloaded files, but I doubt that ALL 5 (or more) of the downloaded files are corrupted...

Bingo Bronson said:
If you have the BIN files in the "Minimal ADB and Fastboot" folder, try renaming them to something simple like "update.bin".
Maybe check the MD5 sum of the downloaded files, but I doubt that ALL 5 (or more) of the downloaded files are corrupted...
Click to expand...
Click to collapse
renamed many times .. same error ...
anything to do with SDK FILES ?

SDK is not needed for this to work, drivers alone are sufficient but it's also not a problem if you have an Android SDK installed.
I assume both operating systems are "clean" enough, so nothing else could interfere with the process. Use USB 2.0 ports for connecting, USB 3.0 is problematic sometimes with these things...
If you have a bootable windows live for a USB drive, you could try it from there...

@aamszia
aamszia said:
* cannot read 'update-fire-phone-33.4.6.1_user_461013320.bin' *
Click to expand...
Click to collapse
you just need more free Ram on computer than file size

Reverting the Fire Phone back to stock

If you are like me you are constantly fiddling and hacking with your phone. I’m also cheap so when I came across an Amazon Fire Phone from my local AT&T store for $150 I had to jump. After all I’m an Amazon Prime customer, so with the year of Prime it made the phone about $50. Anyways, I have been lurking on the Fire Phone XDA forum for a bit and have been using GGOW’s CM11 build since it came out. Every now and then, however, I want to go back to stock. After figuring it all out, I’ve kind of gotten it down to a pretty quick process and thought I would right a quick post on how to take your Fire Phone back to stock.
Ok so first off you have to prep your computer. You will need several things. First off you will need the Android Debug Bridge installed on your computer, also known as ADB. Instead of downloading the entire Android SDK to get ADB, you can follow the instructions on Lifehacker to install ADB pretty quickly. You will also need the OS files for your Fire Phone. You can download them from Amazon. For right now you need to make sure you download the correct file for whether your phone is unlocked or not. I believe the 4.6.6 update unifies the two, but for now it’s better to be safe.
Once you have installed ADB and have the .BIN file from Amazon, it is time to work. You need to make sure your phone is turned off and plugged in to your computer via USB. You will need to turn your phone on by holding down the power button and the volume up button and continue to hold them until you see the “Fire System Recovery” menu. You should see several options, you will need to select the “apply update from ADB” selection. Now with your phone plugged into your computer you need to go to a terminal/command prompt window. You will type
Code:
add sideload <filename>
where you replace <filename> with the path to your .BIN file. For instance on my computer (which runs OSX) I would type:
Code:
adb sideload ~/Downloads/update-kindle-32.4.6.5_user_465000520.bin
Now your update will begin and once it is done all you have to do is restart the phone.
Links:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550

th3rmite said:
If you are like me you are constantly fiddling and hacking with your phone. I’m also cheap so when I came across an Amazon Fire Phone from my local AT&T store for $150 I had to jump. After all I’m an Amazon Prime customer, so with the year of Prime it made the phone about $50. Anyways, I have been lurking on the Fire Phone XDA forum for a bit and have been using GGOW’s CM11 build since it came out. Every now and then, however, I want to go back to stock. After figuring it all out, I’ve kind of gotten it down to a pretty quick process and thought I would right a quick post on how to take your Fire Phone back to stock.
Ok so first off you have to prep your computer. You will need several things. First off you will need the Android Debug Bridge installed on your computer, also known as ADB. Instead of downloading the entire Android SDK to get ADB, you can follow the instructions on Lifehacker to install ADB pretty quickly. You will also need the OS files for your Fire Phone. You can download them from Amazon. For right now you need to make sure you download the correct file for whether your phone is unlocked or not. I believe the 4.6.6 update unifies the two, but for now it’s better to be safe.
Once you have installed ADB and have the .BIN file from Amazon, it is time to work. You need to make sure your phone is turned off and plugged in to your computer via USB. You will need to turn your phone on by holding down the power button and the volume up button and continue to hold them until you see the “Fire System Recovery” menu. You should see several options, you will need to select the “apply update from ADB” selection. Now with your phone plugged into your computer you need to go to a terminal/command prompt window. You will type
Code:
add sideload <filename>
where you replace <filename> with the path to your .BIN file. For instance on my computer (which runs OSX) I would type:
Code:
adb sideload ~/Downloads/update-kindle-32.4.6.5_user_465000520.bin
Now your update will begin and once it is done all you have to do is restart the phone.
Links:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
When I boot to recovery and adb sideload there is no adb device when I type adb devices.
Windows 7 64bit.
Cool I found easy solution...I downloaded this program and runned it when phone was in sideload mode, it installed drivers and voila
http://adbdriver.com/downloads/

everything is still installed and camera still doesnt work
did I miss a step or something? lol. all my apps including nova launcher are still installed and my camera still doesn't work, but it looks like 4.6.6 is installed

ianedward said:
did I miss a step or something? lol. all my apps including nova launcher are still installed and my camera still doesn't work, but it looks like 4.6.6 is installed
Click to expand...
Click to collapse
Since it is official update it won't perform factory reset...

ianedward said:
did I miss a step or something? lol. all my apps including nova launcher are still installed and my camera still doesn't work, but it looks like 4.6.6 is installed
Click to expand...
Click to collapse
you need to wipe the device after flashing the new rom

C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-35.4.6.6_u
er_466000820.bin
loading: 'update-kindle-35.4.6.6_user_466000820.bin'
* cannot read 'update-kindle-35.4.6.6_user_466000820.bin' *
---------- Post added at 09:15 AM ---------- Previous post was at 08:25 AM ----------
C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-juniper-35.
4.6.3_user_463001420.bin
loading: 'update-kindle-juniper-35.4.6.3_user_463001420.bin'
* cannot read 'update-kindle-juniper-35.4.6.3_user_463001420.bin' *
C:\Program Files\Minimal ADB and Fastboot>adb sideload update.bin
loading: 'update.bin'
* cannot read 'update.bin' *
---------- Post added at 09:16 AM ---------- Previous post was at 09:15 AM ----------
i download many files but all BIN files fails to sideload

aamszia said:
C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-35.4.6.6_u
er_466000820.bin
loading: 'update-kindle-35.4.6.6_user_466000820.bin'
* cannot read 'update-kindle-35.4.6.6_user_466000820.bin' *
Click to expand...
Click to collapse
You should be able to manually update your phone to Fire OS 4.6.6 by following the steps at this link: Update Your Fire Phone Software.

jack9955 said:
You should be able to manually update your phone to Fire OS 4.6.6 by following the steps at this link: Update Your Fire Phone Software.
Click to expand...
Click to collapse
Fire phone stucked on recovery .. only option i have is by sideload . .. and sideload is not working for me ..
i have downloaded 5 firmwares .. but same error in all files ..
.....

aamszia said:
Fire phone stucked on recovery [...]
Click to expand...
Click to collapse
Please stick to asking questions for one problem in one thread at a time, thank you.
I replied in the other thread (bricked fire phone / sideloading by ADB), since it's more related to your questions.

aamszia said:
Fire phone stucked on recovery .. only option i have is by sideload . .. and sideload is not working for me ..
i have downloaded 5 firmwares .. but same error in all files ..
.....
Click to expand...
Click to collapse
If you mean you are stuck in Safestrap recovery, then follow @ggow post to flash Fire OS. The links you will need for the flashable images are here and here.
If you are not stuck in Safestrap recovery and your phone is still under warranty, you may want to contact Amazon for a replacement phone.

jack9955 said:
If you mean you are stuck in Safestrap recovery, then follow @ggow post to flash Fire OS. The links you will need for the flashable images are here and here.
If you are not stuck in Safestrap recovery and your phone is still under warranty, you may want to contact Amazon for a replacement phone.
Click to expand...
Click to collapse
i am stuck on Stock Recovery ...

Is there anyway to boot in to safestrap recovery and not the stock recovery. I have a back up on safestrap boot stuck on amazon screen and I can omly get im to stock recovery.

th3rmite said:
If you are like me you are constantly fiddling and hacking with your phone. I’m also cheap so when I came across an Amazon Fire Phone from my local AT&T store for $150 I had to jump. After all I’m an Amazon Prime customer, so with the year of Prime it made the phone about $50. Anyways, I have been lurking on the Fire Phone XDA forum for a bit and have been using GGOW’s CM11 build since it came out. Every now and then, however, I want to go back to stock. After figuring it all out, I’ve kind of gotten it down to a pretty quick process and thought I would right a quick post on how to take your Fire Phone back to stock.
Ok so first off you have to prep your computer. You will need several things. First off you will need the Android Debug Bridge installed on your computer, also known as ADB. Instead of downloading the entire Android SDK to get ADB, you can follow the instructions on Lifehacker to install ADB pretty quickly. You will also need the OS files for your Fire Phone. You can download them from Amazon. For right now you need to make sure you download the correct file for whether your phone is unlocked or not. I believe the 4.6.6 update unifies the two, but for now it’s better to be safe.
Once you have installed ADB and have the .BIN file from Amazon, it is time to work. You need to make sure your phone is turned off and plugged in to your computer via USB. You will need to turn your phone on by holding down the power button and the volume up button and continue to hold them until you see the “Fire System Recovery” menu. You should see several options, you will need to select the “apply update from ADB” selection. Now with your phone plugged into your computer you need to go to a terminal/command prompt window. You will type
Code:
add sideload <filename>
where you replace <filename> with the path to your .BIN file. For instance on my computer (which runs OSX) I would type:
Code:
adb sideload ~/Downloads/update-kindle-32.4.6.5_user_465000520.bin
Now your update will begin and once it is done all you have to do is restart the phone.
Links:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
Please help me when i type adb sideload "filname.bin" , It gives me an error cannot read "filname.bin" ??
Please tell me how could i fix this ??

Hussain_97 said:
Please help me when i type adb sideload "filname.bin" , It gives me an error cannot read "filname.bin" ??
Please tell me how could i fix this ??
Click to expand...
Click to collapse
Did you have any luck reviving your phone?

why not just factory reset using the official recovery? this seems like an awful lot of extra work :|

i am stuck on Stock Recovery elso with my phone .
i test sideload tool give me his msg on CMD windows after type add sideload commend
C:\tools>adb sideload c:/tools/rom.bin
opening 'c:/tools/rom.bin'...
connecting...
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

@amr1406
try to find Android SDK Platform-tools v 25.0.3

ADB Sideload Cannot Read Issue, Searched Nothing worked

I am unable to flash anything even official firmware with official recovery, when in adb sideload mode. whenever i try to push a zip to install terminal says:
C:\Users\nd4ios\Desktop>adb sideload a.zip
loading: 'a.zip'
* cannot read 'a.zip' *
the file is named a.zip
it is in the Desktop folder
ive tried doing this like this:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb sideload C:\Users\nd4ios\Desktop\a.zip
loading: 'C:\Users\nd4ios\Desktop\a.zip'
* cannot read 'C:\Users\nd4ios\Desktop\a.zip' *
C:\Windows\system32>
but same issue
ive tried reinstalling the drivers -(adb, fastboot, and device)-
no avail
ive also tried moving the zip file to the system32 folder and still same error. ive tried multiple zips and nothing.
Ive looked at the ram - practically no ram usage on my pc
ive tried installing twrp recovery but it never can boot into it - just turns to black screen and stays there. (tried multiple different versions of twrp)
ive looked online for help and nothing has helped so far which is why im turning to here.

use this ADB . Yours is old
here
also use TWRP Recovery 3.0.2-1.28 if you are on Oxygen OS Open beta or 4.0 ( N)

it's a windows problem .. a simple restart will solve it ..

not windows probem but probably driver
Go to Computer/Devic manager /Kedacom USB devices or something similar...
change adb driver to ADB generic

thanks, well i was finally able to install the previous firmware via booting and transfering the zip file to the internal storage and installing it from there. so it was a windows problem or driver. im installing this now and hope it fixes it for the future.

I had the same problem with my computer not recognizing my phone with trying to transfer file and flash joints. I went to device manager > right click mtp > update driver software > browse my computer > let me pick > mtp USB device > happy me ??

ok well ive tried using the adb drivers you mentioned and it is still coming up with the same error, so im going to try booting into linux and trying it from there

It's because the ADB executable isn't large address aware and so it fails to allocate memory when you're trying to sideload something big (>1GB) like the OOS 4.0 for our OnePlus 3. You need an ADB that's been made large address aware or you can do it yourself if you have Visual Studio installed on your machine. I'd provide it myself but I've already sworn off posting files here.

i have Visual Studio Enterprise - i got it from being a student, so how would i go about making the adb large address aware? thanks

i found an app online to convert the adb to 64bit and see if that works on it.

ok so what you said is the issue, apparently my adb is not large address aware, as i tried pushing a zip file under a 1GB and it worked but when i push a file over it says it cannot read.

now if only if there was a thanks button so i could add a thank you

ok ive finally got it to work

heres what i did:
i used the original adb.exe in my C:\adb folder
then i right clicked the program and clicked properties and under compatability i chose run as administrator (probably dont need to do this but did it as an extra)
then used https://www.techpowerup.com/forums/threads/large-address-aware.112556/ to convert it to 64bit to allow for long address awareness. and viola it works.
also a side note:
does not work on the minimal adb and fastboot.exe adb program

Trying to Flash the Stock Rom Via ADB sideload

I am Trying to flash the stock rom via side load i flashed that few days back to at that time it was flashed success fully but now it always gives me error
Code:
"C:\android-sdk\platform-tools>adb sideload OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip
loading: 'OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip'
* cannot read 'OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip' *
C:\android-sdk\platform-tools>adb sideload <OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip>
The syntax of the command is incorrect.
C:\android-sdk\platform-tools>"

Mine would not sideload either. I downloaded the zip file to my PC, connected the phone to the PC, put the phone in USB mode, dragged the zip file from the PC to the phone root directory, disconnected from the PC, and flashed the ROM from the phone hard drive.

Faulty ADB drivers I guess. If you have TWRP you can try adb push name /sdcard/

Puddi_Puddin said:
Faulty ADB drivers I guess.
Click to expand...
Click to collapse
Isn't obvious this is not a driver problem?! Read the error message that is staring him in the face. He has not specified the correct file/path.

bulletmark said:
Isn't obvious this is not a driver problem?! Read the error message that is staring him in the face. He has not specified the correct file/path.
Click to expand...
Click to collapse
Second one is a invalid command because of those <> first command mainly happenda with wrong drivers, I and many other get the error it is quite unexplainable.

Any resolution to this? I'm getting the same problem, saying it cannot read the zip file when I try to sideload

trying to update my wifes phone now. getting the same issue. i typed in adb devices and it shows up, so i know its not driver related. wonder if its a faulty image? ill keep trying
---------- Post added at 03:59 AM ---------- Previous post was at 03:55 AM ----------
funny i think i just foud the issue. someone posted saying older adbs cant see larger than 1gb (i have a opo so never even heard of this). ill give it a try and report back...
this is the adb ill be using https://forum.xda-developers.com/showthread.php?t=2317790

Okay, now that may work for others but I could not get it... Sorry
I ended up just removing the encryption, flashing twrp, and flashing OOS that way. Make sure to make a backup... I made a backup of everything... Except contacts because I thought gmail handled that like on my phone. I left my wife a note saying sorry for when she wakes up ha.
At least the annoying updates available message will be gone that we've had since Aug or something

I was getting the exact same errors and was frustrated to no end..... till I figured out how to fix it =)
I had to use this program on my adb.exe to make it large address aware
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Grab the laa_2_0_4.zip from the website, open and run as administrator
Click on select executable and go to where your adb.exe is installed, for me it was in C:\adb\adb.exe
Then make sure the checkbox on step 2 is selected and then hit save
I rebooted my PC and upon using the adb on reboot I was finally able to flash the stock OOS roms via adb sideload on my phone
Yipeee!!

shoemocker said:
I was getting the exact same errors and was frustrated to no end..... till I figured out how to fix it =)
I had to use this program on my adb.exe to make it large address aware
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Grab the laa_2_0_4.zip from the website, open and run as administrator
Click on select executable and go to where your adb.exe is installed, for me it was in C:\adb\adb.exe
Then make sure the checkbox on step 2 is selected and then hit save
I rebooted my PC and upon using the adb on reboot I was finally able to flash the stock OOS roms via adb sideload on my phone
Yipeee!!
Click to expand...
Click to collapse
I used the same tool

Nexus 7 (2013) Stuck on boot loop: Android is starting - Optimizing apps.

I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.

corabict said:
I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.
Click to expand...
Click to collapse
if ok connect to computer then you can move files to computer

jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.

corabict said:
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.
Click to expand...
Click to collapse
reboot recovery and adb pull sdcard

corabict said:
No root or custom recovery.
Click to expand...
Click to collapse
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."

jjgvv said:
reboot recovery and adb pull sdcard
Click to expand...
Click to collapse
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
k23m said:
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."
Click to expand...
Click to collapse
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.

corabict said:
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.
Click to expand...
Click to collapse
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course

jjgvv said:
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course
Click to expand...
Click to collapse
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.

corabict said:
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.
Click to expand...
Click to collapse
adb pull /
and see What happened
avoid adb shell as it needs root.

jjgvv said:
adb pull /
and see What happened
avoid adb shell as it needs root.
Click to expand...
Click to collapse
Yes I tried that and returns this
>>c:\Adb>adb pull /
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: warning: stat failed for path /proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/222/task/1208/fd/15: Protocol not available