hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
jojo665 said:
hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
Click to expand...
Click to collapse
First of all try adb push Name_of_Rom.zip /sdcard/
If that does not work try adb push Name_of_Rom.zip /system/media/
If that still does not work then download the correct TWRP blob file from the following link for your bootloader. http://www.teamw.in/project/twrp2/93
The fact that you are on CWM and was using CM 10 makes me believe that you are still on the ICS bootloader but to make 100 percent sure when you first power on the device look at where the "NVIDIA" logo is. If it is bottom center it is ICS, if it is bottom right it is Jellybean. (MAKE SURE YOU GET THE CORRECT TWRP VERSION FOR YOUR BOOTLOADER)
Now rename the blob file you downloaded to twrp.blob. Go into fastboot and type the following.
fastboot -i 0x0b05 flash recovery twrp.blob
This should install TWRP which will allow you to install a rom off an external micro sd.
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
jojo665 said:
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
Click to expand...
Click to collapse
What exactly did you do? I'm trying to extinguish all avenues before I have to RMA my tablet. Thanks for the help!
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.
so its been already 2 months no way i can fix this still doing the same thing turn on boots and then loops to CWM same thing over n over and no connection to my computer so basicly now i feel i waisted 500 billz and used it from feb till now and no way i can fix it no ideas and asking around how can i putit back to live no answers yet nada so my guessin is not way a big amount and send it to asus or is there still a way to save it? i really missed my prime u use it alot but since still stuck on loop from EEE Pad to CWM and no mount :crying:
klutch said:
so its been already 2 months no way i can fix this still doing the same thing turn on boots and then loops to CWM same thing over n over and no connection to my computer so basicly now i feel i waisted 500 billz and used it from feb till now and no way i can fix it no ideas and asking around how can i putit back to live no answers yet nada so my guessin is not way a big amount and send it to asus or is there still a way to save it? i really missed my prime u use it alot but since still stuck on loop from EEE Pad to CWM and no mount :crying:
Click to expand...
Click to collapse
I am having the same problem man......I can't get the PC to detect my prime so I can't push any .zip
if you get adb to work, this is a solution http://forum.xda-developers.com/showthread.php?t=1661128&highlight=boot+loop
@klutch
what have you done before your prime stuck in the boot loop?
tried to flash anything or something like that
if i remember correctly you can't mount the prime as a removeable disk in CWM unless they fixed it
your best bet is to go into CWM and use adb to push the flashable zip files in there
you can do that by the following commands
Code:
adb push [directory/file name.zip] [/mnt/sdcard/]
if your device is not recognized by windows, then ADB does not work. that's the OP's problem.... and mine as well. ~$230 to fix my prime.
have you already tried to enter fastboot mode and flash a fresh rom from there?
I was able to get the PC detect my TFP by installing the driver from this link
[ADB/FB/APX Driver] Universal Naked Driver 0.7
You should be able to adb afterwards....Then follow 'OPTION 1a" from this link
[HOW-TO] Unbrick your Transformer Prime (or not)
I installed nvflash to make sure this won't happen again
hope this helps!
naked drivers
urboy4mbx said:
I was able to get the PC detect my TFP by installing the driver from this link
[ADB/FB/APX Driver] Universal Naked Driver 0.7
You should be able to adb afterwards....Then follow 'OPTION 1a" from this link
[HOW-TO] Unbrick your Transformer Prime (or not)
I installed nvflash to make sure this won't happen again
hope this helps!
Click to expand...
Click to collapse
i dont get how to install naked drivers when everytime i plug in my prime it just says unknown device in device manager and when i try to update the driver it says i have the best or latest driver. plz someone help me!!!!
InkD_up_G33k said:
i dont get how to install naked drivers when everytime i plug in my prime it just says unknown device in device manager and when i try to update the driver it says i have the best or latest driver. plz someone help me!!!!
Click to expand...
Click to collapse
in CWM while the TFP is plugged to your PC, click "update driver" and make sure you point to the location where "android_winusb.inf" file is located.
if you are in CWM the TFP will pick up "android_winusb.inf" driver
if you are in fastboot mode the TFP will pick up "android_apxusb.inf" driver
Also, I had to try on 3 different computers to make this work.
i just found out wat happen the original usb asus was messed up and i brought one on ebay and it worked so all this for a USB cable i was going crazy
urboy4mbx said:
in CWM while the TFP is plugged to your PC, click "update driver" and make sure you point to the location where "android_winusb.inf" file is located.
if you are in CWM the TFP will pick up "android_winusb.inf" driver
if you are in fastboot mode the TFP will pick up "android_apxusb.inf" driver
Also, I had to try on 3 different computers to make this work.
Click to expand...
Click to collapse
Ok so wen i plug in my tfp while in cwm the only thing that pops up in device manager is unown device in the usb controllers section thats it and wen i try to update driver it says i i have the best driver already and im pointing it to a folder on my desktop with the naked drivers and nothing evn with have disk it says its not 64 bit or sumtn. im about ready to give up and just sell it to someone who prolly can fix it cuz i cant seem to get naked drivers to install to let the computer recognize my tfp so i can adb
InkD_up_G33k said:
Ok so wen i plug in my tfp while in cwm the only thing that pops up in device manager is unown device in the usb controllers section thats it and wen i try to update driver it says i i have the best driver already and im pointing it to a folder on my desktop with the naked drivers and nothing evn with have disk it says its not 64 bit or sumtn. im about ready to give up and just sell it to someone who prolly can fix it cuz i cant seem to get naked drivers to install to let the computer recognize my tfp so i can adb
Click to expand...
Click to collapse
as I asked earlier, did you try to set your prime into fastboot mode and flash a fresh rom from there?
if it does not work with windows, you could try linux, e.g. an ubuntu live cd. download the linux fastboot from here
you can flash a new rom with
fastboot -i 0x0b05 flash boot "path to rom blob"
or new recovery using
fastboot -i 0x0b05 flash recovery "path to recovery image blob"
unfortunately i'm not able to supply links to download fastboot, sorry for that.
klutch said:
i just found out wat happen the original usb asus was messed up and i brought one on ebay and it worked so all this for a USB cable i was going crazy
Click to expand...
Click to collapse
wow, I thought you tried a diff cable already?? well, glad it was just the cable for you! I tried 3 diff cables on mine and it still didn't work
apfel.kuchen said:
as I asked earlier, did you try to set your prime into fastboot mode and flash a fresh rom from there?
if it does not work with windows, you could try linux, e.g. an ubuntu live cd. download the linux fastboot from here
you can flash a new rom with
fastboot -i 0x0b05 flash boot "path to rom blob"
or new recovery using
fastboot -i 0x0b05 flash recovery "path to recovery image blob"
unfortunately i'm not able to supply links to download fastboot, sorry for that.
Click to expand...
Click to collapse
yea when i hold power and volume down it doesnt work as usual when it tells you to press up in the next five seconds. and ive tried restoring back up and flashing a new rom but it just boots up into cwm and my sdcard slot is ****ed up becuz of my lil cousins sticking **** inside the slot so it doesnt read anymore so i cant push files or put files on like that either.
pressing vol- + power and vol+ after 5 seconds should lead you into recovery (CWM) but fastboot is somewhat different. if you do not press vol+ after 5 seconds but either wait longer, you will see a screen where to select how to proceed (USB mode, android, and something else). if you select usb and then connect the tablet to your pc you are in fastboot mode and should be able to flash rom and recovery using the fastboot tool on your PC. using this you wouldn't need a working sd card, only a rom and/or recovery in blob format.
apfel.kuchen said:
pressing vol- + power and vol+ after 5 seconds should lead you into recovery (CWM) but fastboot is somewhat different. if you do not press vol+ after 5 seconds but either wait longer, you will see a screen where to select how to proceed (USB mode, android, and something else). if you select usb and then connect the tablet to your pc you are in fastboot mode and should be able to flash rom and recovery using the fastboot tool on your PC. using this you wouldn't need a working sd card, only a rom and/or recovery in blob format.
Click to expand...
Click to collapse
yes i know that but thats the problem im not able to go into fastboot i tried it, it reboots into recovery on its own and i know the only way im going to unbrick this is by adb but my device isnt showing up on my computer just unknown device under usb contollers which i tried to install the naked drivers but is unable to
hmm.. ok thats bad.
do you have a linux machine to check if it is a windows problem?
because it doesn't really make sense to me that CWM is working but adbd not.
i may have found a solution
this is just my experience but it seems like the different adb's that people are posting of the forums are outdated and dont work properly with some primes. I have tried several the windows task manager said "asus transformer prime adb interface" with the naked drivers as soon as i used the adb included in the sdk from <developer.android.com/sdk/index.html> it worked. so install the sdk then in the command prompt navigate to the platform tools inside where it was installed us the adb.exe found there.
as far as using the wrong drivers when you remove the device there might be the option to delete the device driver check that then scan for new devices......point it to where ever you unziped
this may not work for you but this is what finally resurrected my prime after 24 hours
Okay I just had the same problem ... after some research and some trial and error I was able to fix my prime.
First to make your life simple open a command prompt. You will have a flashing cursor next to the directory that you command prompt defaults to.
In my case it was c:/users/peter
You can put the sdk files anywhere on your computer but if you put them in the default command prompt folder you don't have to change the directory with dos commands.
Next with your prime not connected go into the device manager and delete any instances of the prime. Reboot your PC.
Next download the universal naked drivers
Connect your prime, if you go back into device manager you'll find it under USB devices. Click on upgrade drivers and navigate to the universal naked drivers. It should install if not your universal naked drivers might be outdated but uninstalling / deleting the previous instance of your prime should take care of any issues.
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
After this I recommend installing the androidroot.mobi custom boot loader and nvflash to make your prime unbrickable I also changed my recovery from cwm to twrp2 to help eliminate this from happening again.
Same here
What if you only have TWRP Recovery and not CMW? I have the exact same problem, but none of my machines will even detect a new device to find drivers for. I have a laptop with Ubuntu 12.04, another laptop with Windows XP, and an iMac with Snow Leopard. All have Android SDK and ADB but I can not get either to detect the device in Recovery mode. I tried fast boot, but every time I click the USB symbol, the TFP just locks up and freezes and still no detection. Can anyone help? I know if I can get it detected, I will be able to handle the rest.
pcdonovan said:
Okay I just had the same problem ... after some research and some trial and error I was able to fix my prime.
First to make your life simple open a command prompt. You will have a flashing cursor next to the directory that you command prompt defaults to.
In my case it was c:/users/peter
You can put the sdk files anywhere on your computer but if you put them in the default command prompt folder you don't have to change the directory with dos commands.
Next with your prime not connected go into the device manager and delete any instances of the prime. Reboot your PC.
Next download the universal naked drivers
Connect your prime, if you go back into device manager you'll find it under USB devices. Click on upgrade drivers and navigate to the universal naked drivers. It should install if not your universal naked drivers might be outdated but uninstalling / deleting the previous instance of your prime should take care of any issues.
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
After this I recommend installing the androidroot.mobi custom boot loader and nvflash to make your prime unbrickable I also changed my recovery from cwm to twrp2 to help eliminate this from happening again.
Click to expand...
Click to collapse
hi everyone,
I'm coming from this thread http://forum.xda-developers.com/showthread.php?t=1834761
I have been stuck for more than one week now and i didn't find any solution.
My problem is that I'm currently stock in a clockworkmod recovery boot loop on my Asus Transformer Prime without adb/fastboot connection:
1 - I had install CM9 stable on my Transformer Prime, after a wide data and then send throw "adb push" the CM9.zip,
2 - I reboot by CM9 in recovery mod to install Gapps,
3 - I install the Gapps zip,
4 - I ask to clockworkmod to reboot,
5 - Since then I'm in a clockworkmod recovery boot loop without adb/fastboot connection (witch used to be working),
If kown how can I get adb/fastboot connection back to be able to find my device with the adb command " adb devices " and then be able to send this command => " dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 "
Thank you for your understanding,
Kind regards,
Adb and fastboot are two different things... Fastboot is obtained buring booting process with vol down pressed, then not selecting recovery with volume up. So you should have fastboot access.
In this case I would suggest to fastboot flash TWRP (see on their website for instructions) it will perhaps fix things or at least give you adb access.
If you use cwm take the old 5.8.2.0 modded for not looping with reboot to recovery feature, or stay with twrp.
I would look at the following thread for unbricking the TF201:
http://forum.xda-developers.com/showthread.php?t=1514088
Sounds like you might fall into Option 1a.
I was having your same issue but it was because I rebooted into recovery from the reboot option on the CM10 rom. In any event, I couldn't get adb to work or recognize my device no matter what. I then decided to use my macbook pro. I can tell you that using adb on a mac is much easier as you don't have to download the drivers or sdk, just the platform tools. Here's a link: http://forum.xda-developers.com/showthread.php?t=1387527. I know this may not help if you or someone you know doesn't have a mac, but it saved me.
So I'm in the process of trying to Root my ZTE Smarttab 10 on firmware v03b.
Ive been following instructions on the following pages:
http://forum.xda-developers.com/showthread.php?t=1629630
http://forum.xda-developers.com/showthread.php?t=1473555
The instructions are spread out across those threads and my problem starts kind of early in the process.
My goal is to use ADB to boot in to the Bootloader and then use a recovery rom to use TWRP to install a rom.
What i have done:
I have installed the ZTE Drivers
I have installed the SDK tools and updated it.
Now when the tablet is running normally I can see it in ADB and is able to run the command.
ADB Reboot Bootloader
This reboots the devices to a black screen (I assume this is the bootloader) and windows recognizes that a device is there.
The problem is that when I try to see this from ADB i cannot see the device when running ADB Devices.
This makes the next step impossible as I need to use ADB to boot a recovery rom.
So I would have posted in the development treads listed above but as I dont have 10 posts (this being my first post) I cannot post in the threads above.
I'm confident that this is a driver problem and I have uninstalled and re-installed all the drivers related to this including SDK.
But no luck yet.
Where other people say they have succeeded is when in the device manager they have ADB interface and ZTE Handset ADB interface listed.
This is the state where I'm at but I still cannot see the device in ADB.
Anyone have any insight on this kind of problem and can offer any help for a solution or direction to get to the solution.
Thank you for your help and attention!
//Nagarutu
Vodafone (ZTE) SmartTab10 3.2 HoneyComb
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
matt4321 said:
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
Click to expand...
Click to collapse
Thank you for the help ! it cleared things up for me.
Now the trouble's continue.
With the firmware im on (v03b) you cannot use the fastboot flash method but only fastboot.
And they way it is supposed to be done is that you run
fastboot boot recovery.img (recovery being a twrp recovery for my device)
When its booted to TWRP i should be able to see it in ADB to be able to run the following commands to it:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
However I cannot get it to show in ADB (or fastboot) when its booted in to TWRP.
Any ideas?
I managed to solve the last bit to.
Now it was actually a driver problem, so i just updated the driver in device manager and located the ADB driver from ZTE and it worked to boot in to TWRP and then to flash the device.
Now I have CM10 installed and is smiling!
Took me 4 days but damn it its done!
Thanks for the help!
Glad you've figured it out
1a
2a
3a
4a
5a
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.