I'm in the middle of restoring an HTC One M7 Sprint phone to stock from CM11. Since I don't have S-Off, I tried using the minimal package from HTC1Guru, the Reset Download. I have TWRP Recovery, so I copied the Reset Download utility to the phone and ran it. That went ok, except the screen was unresponsive and I had to use a mouse. So, I tried to get an OTA (after relocking the bootloader) to get all current stock. A few minutes into the install of the OTA, it just locked up and there I sat, with the White HTC screen and nothing happening.
So I've tried several things. But a side effect of this condition is I could NOT run ADB. Now I do have a USB connection and it works; In Fastboot if I issue the FASTBOOT DEVICES command I get the device id back. But I could not get ADB to work at all, even though the cable is connected and all that (since Fastboot works). Oh, and ADB worked before this locked up. ADB Devices returns no devices. BUT (it gets weirder) I went back to Fastboot and flashed TWRP REcovery again, and if I enter RECOVERY, I can issue ADB Commands from recovery fine. But outside of recovery, I can't. And, more importantly, PROGRAMS CAN'T DETECT ADB. I tried Rumrunner's program to turn S-OFF, and I tried the ARUWizard RUU utility from Viperboy, and both said to check the USB cable, that ADB could not be found. But I went right to it, booted recovery, and there was ADB!
So, what could cause ADB to be present if I'm booted to recovery, but not from bootloader screen? since right now I can boot to REcovery but not to the ROM, I'm totally dead in the water.
Steve
Steve Thomas said:
So, what could cause ADB to be present if I'm booted to recovery, but not from bootloader screen?
Click to expand...
Click to collapse
ADB never works in the bootloader (that's why you have fastboot to talk to it). ADB talks to the ADB daemon, which is running when a ROM or a recovery is booted.
_that said:
ADB never works in the bootloader (that's why you have fastboot to talk to it). ADB talks to the ADB daemon, which is running when a ROM or a recovery is booted.
Click to expand...
Click to collapse
I thought I must be doing something wrong running ADB with the phone in Recovery since Rumrunner keeps failing with "No ADB Connection". But maybe it's something else.
Thanks!
Related
Hi xda,
I was unlocking and installing AOKP ROM this week and I've hit a problem that I can't get past. I apologise that this seems like so many other questions already posted, but I haven't found a solution in the threads I've read. I also apologise that I write verbose explanations; I just want to be as clear as possible.
My new TF201 was on ASUS firmware .21 so I used bpear's viperMod/Wolf849-based tool to downgrade to ASUS firmware WW .15.
I then used bpear's tool to root it after downgrading, and then unlocked the bootloader using ASUS' tool. Before anyone asks why I bothered to root if I was going to unlock, I didn't entirely understand what was required to flash a custom ROM on the TP; the process was much simpler on my HTC Desire.
After unlocking the TF201 I used bpear's tool to flash CWM. I downloaded AOKP (aokp_tf201_build-38.zip) and put it on the internal space - I don't have an SD card in it. I rebooted the device into CWM and wiped Dalvik cache, reset factory settings, then went to "Install from zip" and selected the AOKP zip. It ended successfully (i.e: no errors, all messages on the screen appeared normal), so I reboot the device.
And after rebooting it hangs at the splashscreen. I tried to reflash AOKP but there was no change, so I rebooted into the bootloader menu and, without thinking about the consequences, selected to wipe the device. Now I can't reflash AOKP because I wiped the device, and I can't restore a nandroid backup because I didn't take one before flashing AOKP.
I rebooted to the bootloader and selected Fastboot mode while the device was connected to my computer (Windows 7 x64). In Windows, I can see in the taskbar that a device is recognised as "fastboot", and drivers are installed successfully, so I type in the command 'fastboot devices' which simply returns a new line. I reboot into CWM and try to use adb to connect to the device, but there is no device detected in Windows and the command 'adb devices' indicates there is nothing found.
At this point I'm unsure what step to take next. Any tips would be useful.
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
cam30era said:
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
Click to expand...
Click to collapse
there is no 'adb fastboot' command
@OP, you have to reinstall/point windows again (while in recovery) to the drivers manually. it's the same drivers, yes.
Hi xda,
I got everything sorted a couple of days after this thread was started.
I followed the same procedure described in the OP, with two changes:
1. I swapped AOKP for Virtuous Prime.
2. I installed the Universal Naked Drivers .
My TF201 is functioning very well on Virtuous Prime ROM. I am pleasantly surprised with the battery life but sufficiently annoyed with the wireless that I set up an AP at the other end of the apartment just for the TF201.
cam30era said:
The command "adb devices" will not show your device unless it's booted, so what you're seeing is normal. You may want to try pushing a ROM to your TFP via adb fastboot.
Click to expand...
Click to collapse
While I was searching for a solution, I read on several sites that it was possible to push files to the tablet while in recovery mode/CWM. An example is this thread. I have to wonder: am I misunderstanding the steps being provided, or is the information being provided is incorrect or incomplete?
With regards to fastboot, I did mention in the OP that fastboot wasn't functional.
Cheers.
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
anyone knows?
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
Yes, you can access ADB while in a bootloop.
Theonew said:
Yes, you can access ADB while in a bootloop.
Click to expand...
Click to collapse
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
runingwild said:
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
Click to expand...
Click to collapse
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
yes you can I have this before and it's working
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again
Click to expand...
Click to collapse
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
mustafah822000 said:
yes you can I have this before and it's working
Click to expand...
Click to collapse
that can be helpful for me. How did you do it?? was it in bootloop too? not rooted?
Theonew said:
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
Click to expand...
Click to collapse
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
Click to expand...
Click to collapse
Theonew said:
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
Click to expand...
Click to collapse
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
runingwild said:
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
Click to expand...
Click to collapse
Its a driver issue. Check device manager for your "unknown device," then associate adb drivers with it.
you can use adb once the kernel has loaded so root or any other factor shouldn't affect it
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
if u are bale to get into fastboot flash a stock ruu and it should work fine
well, what if i cannot access recovery mode or fastboot menu as you have said so. my HTC desire 310 is having bootloop and cant enter recovery. HELP PLEASE!!
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Esploded said:
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Click to expand...
Click to collapse
Do you have adb? If you do the command is adb reboot recovery. Need to know more it just cycles? If so then try to push both power button and and both volumes until it has lights flashing at the bottom and reboots dont let go until it reboots. Other then that I am not sure. I tried to boot to recovery the manual way and it doesnt work. Which is why i Always use that to reboot recovery. Wait, I figured it out. Hold down volume power dont let go until bootloader comes up then let go of both. use volume down and select recovery and bam!
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
jhr5474 said:
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
Click to expand...
Click to collapse
I'll give the fastboot utility a shot, hopefully it works. Thank you
Esploded said:
I'll give the fastboot utility a shot, hopefully it works. Thank you
Click to expand...
Click to collapse
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
jhr5474 said:
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
Click to expand...
Click to collapse
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Esploded said:
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Click to expand...
Click to collapse
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
jhr5474 said:
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
Click to expand...
Click to collapse
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Esploded said:
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Click to expand...
Click to collapse
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
sdamark said:
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
Click to expand...
Click to collapse
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Esploded said:
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Click to expand...
Click to collapse
No, If you have twrp use adb push and push a rom to your phone and then flash it and your fine.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
If you can get into your rom, go to settings..power and at the bottom disable fastboot
Esploded said:
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
Click to expand...
Click to collapse
1. Charge your phone (about 24 hours).
2. Let him rest (about 24 hours) without turning on.
3. Connect device to PC with original wire (Win7 preferred).
There is possibility that your BB will recognize phone.
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Bump, need help ASAP
Alex311360 said:
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Click to expand...
Click to collapse
If you can enter safestrap recovery, check if you can establish adb access:
so enter safestrap and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try:
adb devices
it should return:
list of devices attached
xxxxxxxxx recovery
if you can achieve that your kindle in safestrap recovery is recognized by win/linux, you can try this:
1. Download this 13.3.1.0 (Kindle HDX 7") update - pure amazon FireOS so OTA updates enabled - do not connect to wifi/register your kindle if you want root and use of custom recovery after flashing this
A. Now, since I am not expert for adb installing pushing repairing etc., read this thread [HOWTO] Unbrick your device
B. If that for whatever reason wont work, you can try sideload update-kindle-13.3.1.0_user_310079820.bin (rename .bin to .zip before sideloading) through safestrap recovery, but because Safestrap is only TWRP "based", I cant guarantee that this will work either (it should, but this is one way ticket, your working safestrap recovery will be destroyed in the process of update and if things dont go as they should, your kindle is bricked for good):
0. connect kindle to pc/laptop
1. enter Safestrap, tap Advanced -> ADB Sideload -> Swipe slider to start Sideload
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX sideload
3. type adb sideload update-kindle-13.3.1.0_user_310079820.zip
4. You will see a progress bar in the command prompt indicating that the Zip file is being copied to the device. Once the file is transferred, the Zip is automatically installed on your device.
OK fingers crossed, I hope something will work, but things can go wrong, so it is up to you if you try this or not ...
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Alex311360 said:
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Click to expand...
Click to collapse
You can also try to unlock your bootloader (since you have compatible FW) and proceed to flash cuber signed recovery (TWRP 2.8.5.0) through fastboot and then from TWRP you can do necessary steps to recover your kindle quite easily - if you are familiar with TWRP flashing...
Regarding sideloading I honestly dont know how it will react - never try it - it was developed exactly for quick system recovery, but you must be flashing 100% working rom ...
Personaly I would go for bootloader unlock and then flash TWRP 2.8.5.0 from which sideloading feature (If you want use that) must working... :good:
Do you require a factory fastboot cable for that?
Alex311360 said:
Do you require a factory fastboot cable for that?
Click to expand...
Click to collapse
No, standart USB cable is enough.
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Alex311360 said:
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Click to expand...
Click to collapse
Sure, here is original post from dpeddi.
... and here is how to for windows ... :good:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Alex311360 said:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Click to expand...
Click to collapse
If your OS is Windows 7, you can try install these drivers and then try again.
jeryll said:
If your OS is Windows 7, you can try install these drivers and then try again.
Click to expand...
Click to collapse
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Alex311360 said:
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Click to expand...
Click to collapse
On which FW you were before downgrading to 13.3.1.0?
Weird thing with windows and these drivers is it sometimes command fastboot -i 0x1949 devices does nothing, while actually direct commands like
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 getvar version
fastboot -i 0x1949 getvar kernel
works as expected...
Anyway to restore system on your kindle you need working connection between kindle and PC/laptop, so you can use adb commands to restore your system, or after bootloader unlock, you can use fastboot commands to flash required/missing components. I have tested while in safestrap kindle is recognizable by adb devices, if you can achieve that, you can continue with how to unbrick thread I posted before.
You can also learn how to install/use Linux, where adb and fastboot device recognition/commands works 100%...
I must leave for work now ...
So, some kind of miracle happened, and I found the source of the problem.
Upon trying to update to 13.3.2.4, it reboots the phone instead of installing it. I try booting into Safestrap, and it does Open Recovery Script, causing it to boot to a black screen upon booting to the actual thing.
I don't know how to fix Open Recovery Script doing that, but all I had to do to get it back to normal was reflash the 13.3.1.0 amazon OS onto stock.