Related
I stupidly showed my teenage son how to use ROM Manager and CWM on my phone.
He has now completely deleted (and I feel formatted) ALL Data etc on the phone.
So, as I cannot use any software on my MAC to transfer ROMs to the phone CAN Someone please advise how to get a ROM on the phone?
I can still access CWM Recovery. I have Android SDK installed, including Eclipse.
Please remember I am using a MAC, when you helpfully pass on ideas or solutions
Go to adb and fastboot folder, boot into recovery and use the command from terminal:
Code:
adb push name-of-rom.zip /sdcard/
.
Remember to put the rom into adb/fastboot folder
Hey, thank you.
I will try that soon
Hmm, trouble getting this done
I keep getting "command not found" message. Everything is in the folder.
I have done a CD to the folder etc
aussie_boi said:
Hmm, trouble getting this done
I keep getting "command not found" message. Everything is in the folder.
I have done a CD to the folder etc
Click to expand...
Click to collapse
Are you doing it while in recovery?
Try 'adb devices' and see if it sees your device
Type exactly the command you're typing to try push your ROM so we can see if you've made a slight mistake...
Sent from my HTC One using xda premium
redbull123 said:
Are you doing it while in recovery?
Try 'adb devices' and see if it sees your device
Type exactly the command you're typing to try push your ROM so we can see if you've made a slight mistake...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Okies, I have tried adb devices and it comes back with no device listing. I was in CWM Recovery mode.
This is what I typed - /Users/Greg/Downloads/Android/sdk/platform-tools/adb push AR10.1.zip /sdcard/ for the push, and
I typed this for the adb devices command - /Users/Greg/Downloads/Android/sdk/platform-tools/adb devices
aussie_boi said:
Okies, I have tried adb devices and it comes back with no device listing. I was in CWM Recovery mode.
Click to expand...
Click to collapse
What does your adb folder have in it? I use a Mac and all I have is 2 files:
adb
fastboot
Try going into fastboot it should say FASTBOOT USB then try 'fastboot devices'
Also, try a different usb port...
Sent from my HTC One using xda premium
redbull123 said:
What does your adb folder have in it? I use a Mac and all I have is 2 files:
adb
fastboot
Try going into fastboot it should say FASTBOOT USB then try 'fastboot devices'
Also, try a different usb port...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
This is the response this time - homelatform-tools Greg$ /Users/Greg/Downloads/Android/sdk/platform-tools/fastboot devices
HT34LW912007 fastboot
aussie_boi said:
This is the response this time - homelatform-tools Greg$ /Users/Greg/Downloads/Android/sdk/platform-tools/fastboot devices
HT34LW912007fastboot
Click to expand...
Click to collapse
Now try recovery again
adb devices
Sent from my HTC One using xda premium
redbull123 said:
Now try recovery again
adb devices
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It's not playing ball at all - this is the response after "adb devices"
home:Android Greg$ /Users/Greg/Downloads/Android/adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
home:Android Greg$
aussie_boi said:
It's not playing ball at all - this is the response after "adb devices"
home:Android Greg$ /Users/Greg/Downloads/Android/adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
home:Android Greg$
Click to expand...
Click to collapse
Try finding the two files I said earlier in your sdk and make a new folder just with those two files and your ROM.zip and try opening your terminal window from that new folder.
Sent from my HTC One using xda premium
redbull123 said:
Try finding the two files I said earlier in your sdk and make a new folder just with those two files and your ROM.zip and try opening your terminal window from that new folder.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Okies, I have already done that. I copied the "adb and fastboot" files from the sdk and added the "ROM.zip" file there also.
In recovery, I still get no devices listed with "adb devices"
I have opened a terminal window from within the case folder ... etc etc
I'm in the same spot and I don't have acess to a windows computer, tried doing this for almost 3 hours last night
Sent from my HTC VLE_U using xda premium
rizzxx7 said:
I'm in the same spot and I don't have acess to a windows computer, tried doing this for almost 3 hours last night
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
I've seen this happen on my friend's HTC One a week ago. I was able to fix it by using the ALL IN ONE TOOL that was posted in this forum. I SIDELOADED a ROM, but only AFTER flashing the stock Boot.img and kernel. I dunno if this helps, but it certainly fixed the problem for me.... oh and also, I did this on a Windows 7 lappy and I'm not familiar with Macs.
MacHackz said:
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
Click to expand...
Click to collapse
I will try this once again when I get home, I've got a nandroid file from a stock tmobile Rom that I will try to install
Sent from my HTC VLE_U using xda premium
MacHackz said:
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
Click to expand...
Click to collapse
When I do this, I still get the error: device not found
This is what I did when in the directory using Terminal within that directory. I was in Fastboot USB for the ADB push
home:Android Greg$ ./adb push ar10.1.zip /data/media/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
And when I do Fastboot Devices and ADB Devices, I get this in Fastboot USB mode
home:Android Greg$ ./fastboot devices
HT34LW912007 fastboot
home:Android Greg$ ./adb devices
List of devices attached
home:Android Greg$
This has really got me puzzled
shinobix37 said:
I've seen this happen on my friend's HTC One a week ago. I was able to fix it by using the ALL IN ONE TOOL that was posted in this forum. I SIDELOADED a ROM, but only AFTER flashing the stock Boot.img and kernel. I dunno if this helps, but it certainly fixed the problem for me.... oh and also, I did this on a Windows 7 lappy and I'm not familiar with Macs.
Click to expand...
Click to collapse
@shinobix37
Can you give me the link for the AllInOne Tools etc and where to download the Stock Kernel etc and how you did the side load.
Seems the SDK ADB is not working for me. Fastboot obviously is. This is all really strange
aussie_boi said:
@shinobix37
Can you give me the link for the AllInOne Tools etc and where to download the Stock Kernel etc and how you did the side load.
Seems the SDK ADB is not working for me. Fastboot obviously is. This is all really strange
Click to expand...
Click to collapse
When you use the command make sure your in cwm not fastboot.
So go into cwm then use command that you said before
Sent from my HTC One using xda premium
Android The Greek said:
When you use the command make sure your in cwm not fastboot.
So go into cwm then use command that you said before
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks. I had been in CWM earlier, and the same as just now, when I try ./adb devices ... while in CWM, terminal returns no listing of devices.
It seems to me that ADB does work, as it identifies the "daemon is out of date" and restarts it successfully.
It is just that ADB does not recognise the HTC One, whilst "Fastboot devices" does, while not in fast boot usb.
I am still lost. CWM works. ADB cannot connect ...
Help
Hey, I looked on other threads but I did't find my problem or the description was too difficult for my ( I'm from Germany, my english is good but not perfect).
I installed TWRP but I also deleted my system, now I only can use the TWRP Menu...
But I think that I can use adb, when I type:
Code:
adb devices
then there comes:
Code:
List of devices attached
0123456789ABCDEF recovery
I used this Tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
And I found this thread with a similar problem: http://forum.xda-developers.com/showthread.php?t=2412932
The answer ther is:
stunts513 said:
You shouldn't nessasrily need fastboot to fix this, I'm assuming the drivers you don't have installed for twrp is the adb device, so try updating Ur drivers with this version of the drivers: http://forum.xda-developers.com/show...php?p=44446906
Once the adb driver work you should be able to go I to twrp, hit advanced, then hit side load, and swipe to start side load, and with it plugged I to your PC put either a cm ROM or the stock rooted amazon ROM from android development into the same folder as your adb command, and run a line with this syntax in a command prompt: adb sideload myrom.zip
If that doesn't work you might be able to use adb push when not in side load mode but I haven't tinkered to much with twrp. If you must resort to using fastboot you shouldn't even need a factory cable in this case, as u can just go into twrp and hit reboot and tap bootloader, that should put you in fastboot. Hope this helps.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
There I don't understand the part with sideloading a rooted stock or custom rom.
I hope that you can help me and thet you understand my question
EDIT: I have a factory cable mybe it's good to know for you.
Basically you put the file you want to flash in the same folder as adb unless your have adb in your system paths, and type "adb sideload filetoflash.zip". You still have to go into twrp before this and hit advanced, then hit sideload, then swipe the thing. Sorry if this seems repetitive, I'm not sure how to make it much simpler. If you can't figure out the side load just do what I would do, boot your kindle into twrp, and plug into your PC. Now with the file you want to flash to the kindle in the same folder as adb run "adb push filename.zip /sdcard/filename.zip". That should put the file onto the kindles sdcard, from there you can use the install button in twrp and choose the file.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Basically you put the file you want to flash in the same folder as adb unless your have adb in your system paths, and type "adb sideload filetoflash.zip". You still have to go into twrp before this and hit advanced, then hit sideload, then swipe the thing. Sorry if this seems repetitive, I'm not sure how to make it much simpler. If you can't figure out the side load just do what I would do, boot your kindle into twrp, and plug into your PC. Now with the file you want to flash to the kindle in the same folder as adb run "adb push filename.zip /sdcard/filename.zip". That should put the file onto the kindles sdcard, from there you can use the install button in twrp and choose the file.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
So I have the zip file of the custopm rom and the md5 file on the sd card, after I moved them from an other directionary to the sd.
Now it' said that the md5 file is missing... but I can't put them into one zip file, idk, do you now what I do wrong?
What do you need an md5 file for?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Basically you put the file you want to flash in the same folder as adb unless your have adb in your system paths, and type "adb sideload filetoflash.zip". You still have to go into twrp before this and hit advanced, then hit sideload, then swipe the thing. Sorry if this seems repetitive, I'm not sure how to make it much simpler. If you can't figure out the side load just do what I would do, boot your kindle into twrp, and plug into your PC. Now with the file you want to flash to the kindle in the same folder as adb run "adb push filename.zip /sdcard/filename.zip". That should put the file onto the kindles sdcard, from there you can use the install button in twrp and choose the file.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2388341 for this, I have the md5 file but I think it must be in the rom.zip
Edit: Thanks stunts513, I tried it with CM10.1 Tablet UI, succses.
Note: I would have posted this in the developement forum as I've tried following both threads. (These: http://forum.xda-developers.com/showthread.php?t=2271909 and http://forum.xda-developers.com/showthread.php?t=2128848). Everything works okay as far as CMD entries etc, and it boots up in fastboot, at which point KF First Aide says <waiting for device>, and the Kindle is just sitting on the fastboot logo. No errors or anything, it just sits there.
Holding power on the Kindle shuts it down, and it will boot up normally. But it doesn't look like flashing back to 7.2.3 is working, because it stills shows up as 7.4.6. (It is already rooted as well.)
Not really sure how to proceed from here, I'm trying to install CM10.2 on it ultimately.
Edit: Also, I did already make backups.
Sounds like the fastboot drivers aren't installing, once you see the fastboot logo, check the device manager for a device with a yellow triangle, if there is one its probably called tate-pvt or something like jem or otter2 then use the drivers in my signature by right clicking the device, hitting update drivers, and pointing it to where you extracted my drivers and once the the device is I stalled it should continue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Sounds like the fastboot drivers aren't installing, once you see the fastboot logo, check the device manager for a device with a yellow triangle, if there is one its probably called tate-pvt or something like jem or otter2 then use the drivers in my signature by right clicking the device, hitting update drivers, and pointing it to where you extracted my drivers and once the the device is I stalled it should continue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Looks like that was it, it's working now. Now to install PAC Man ROM.
Thanks!
Okay new problem.
"6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done."
I'm at this issue, and when I run adb it opens a cmd window which does something(lots of text scrolls), and then goes away(cmd then closes.). So I can't type the command in. Any ideas?
Well adb is a command line tool, so if you want to use it you need to run it from a command prompt...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Halo_003 said:
Okay new problem.
"6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done."
I'm at this issue, and when I run adb it opens a cmd window which does something(lots of text scrolls), and then goes away(cmd then closes.). So I can't type the command in. Any ideas?
Click to expand...
Click to collapse
You need to actually type command in your run box to open a dos prompt. THEN you can do the adb commands. Don't just try an adb command from your windows run box. It will run adb without modifiers, give you the help screen and then quit because windows thinks the program ran and completed.
NapalmDawn said:
You need to actually type command in your run box to open a dos prompt. THEN you can do the adb commands. Don't just try an adb command from your windows run box. It will run adb without modifiers, give you the help screen and then quit because windows thinks the program ran and completed.
Click to expand...
Click to collapse
Okay so here's what I didreplace *'s with h.)
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_36_38_376_zps0b71405b.jpg
Once in cmd, type adb and hit enter. Binary version looks good.
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_36_49_904_zps374e53f3.jpg
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_36_46_102_zpsaa0f7ff7.jpg
But then when trying sideload it doesn't work.
*ttp://i979.photobucket.com/albums/ae277/Halo_003/Desktop_2013_11_15_14_38_20_363_zps989da0dd.jpg
Am I doing it wrong?
Any ideas on how to get it working?
Halo_003 said:
Any ideas on how to get it working?
Click to expand...
Click to collapse
Stunts write up should get you there http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Halo_003 said:
Any ideas on how to get it working?
Click to expand...
Click to collapse
I got the chance to check out your DOS screenies.
There is no such command called sideload in some ADB versions. Here are the basic ADB commands.
3. Basic ADB commands
ADB push (sends files to your phone) -- adb push c:\example.apk /sdcard/example.apk
ADB pull (Receives files from your phone) -- adb pull /system/app/example.apk c:\example.apk
ADB install (installs application) -- adb install c:\example.apk
adb shell (Begins shell connection with phone)
adb reboot (reboots phone)
adb reboot recovery (reboots phone into recovery)
adb reboot bootloader (reboots the phone into bootloader/the white screen)
adb remount (remounts the system)
4. Commands to run while in ADB Shell
cd (changes directories) -- cd /system/app
ls (lists all files in the directory) -- cd /system/app
rm (removes files) -- rm /system/app/example.apk
cp (copies files) similar to cat -- cp /system/app/example.apk /sdcard/example.apk
cat (copies files) -- cat /system/app/example.apk > /sdcard/example.apk
exit (exits shell) -- exit
Click to expand...
Click to collapse
You have to make sure the ADB you have knows what the sideload command is.
Yep thank you guys! I got it working with that like LE gave me. Much appreciated!
LinearEquation said:
Stunts write up should get you there http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Click to expand...
Click to collapse
Ah yes! That was it! I wasn't doing the cd command so that's the issue I was having. Thank you!
Hello all.
Was tinkering around with my KF- And accidentally wiped everything from my internal storage and system. When it boots up I get the blue KF logo and it stays stuck there- Can't boot into recovery.
ADB doesnt recognize it.
Have a fastboot cable.
How do I atleast push files to it /boot into recovery??
Many thanks.
To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.
SilverRoxas said:
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.
Click to expand...
Click to collapse
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.
LinearEquation said:
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.
Click to expand...
Click to collapse
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.
SilverRoxas said:
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.
Click to expand...
Click to collapse
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.
LinearEquation said:
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.
Click to expand...
Click to collapse
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?
SilverRoxas said:
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?
Click to expand...
Click to collapse
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.
LinearEquation said:
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.
Click to expand...
Click to collapse
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.
SilverRoxas said:
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.
Click to expand...
Click to collapse
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).
SilverRoxas said:
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).
Click to expand...
Click to collapse
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, my Kindle is still recognized.
i dont os on my kindle fire hd 7
I am having a mare with my kindle fire hd 7
It all starrted when anything google related kept crashing.
I tried to find solutions to the problem but no joy.
I then tried to install a different update to cyanogenmod nightly software but i then had a major problem with not being able to turn on my wifi.
I went into Twrp and tried to restore to my previous software but when my kindle re-booted i got stuck with a flashing teamwin logo
After trawling for days i managed to get out of that but im now in a situation where i dont have any OS on my kindle.
I have followed instructions on how to push files onto my kindle but despiote finding some files on my sdcard i am unable to reboot past the blue and white Kindlefire logo.
I have tried using the kindle un-brick java option but no joy either
I would really appreciate some help solving this proble as it is really driving me crazy.
I can still access twrp and i can access bootloader to get the orange and white fastboot logo.
If someone can help guide me through how i can get my kindle working again id really appreciate it
cheers
JJ
Might be able to help.
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Hey Danny101
Danny101 said:
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Click to expand...
Click to collapse
Thanx for your response.
Sorry its taken me a while to reply but have had loads going one recently.
Shortly after making my post i did find that exact same youtube vid tutorial and was able to solve my problem.
I just wanted to say thanx for taking time to respond even so.
All the best.
JJ
Hello all !
First, i'm so sorry for my bad english ...
I just buy a Kindle fire HD 7", with 7.4.6 firmware.
I make root, and i try to install Cyanogenmod, but now, my kindle doesn't start.
When i push the "On" buton, i see the logo "Kindle Fire" in orange, after i see the blue, but the tablet doesn't arrive to the desktop.
I can acces when i push the volume buton to my TWRP menu, but my save doesn't work.
My windows 7 doesn't see the tablet, i don't know how save my kindle
I see on internet some peopple who speak about "fast boot cable". It's a solution to unbrick ?
I hope you can understand me, sorry for my little english.
Best regards
Martin
If you have access to twrp then you don't need fastboot to fix it. As long as you install the adb drivers in my signature for your kindle while it's in twrp, you can push a new ROM to it over adb and flash it and it should boot up must fine.I wrote a tutorial on how to do it here: http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If you have access to twrp then you don't need fastboot to fix it. As long as you install the adb drivers in my signature for your kindle while it's in twrp, you can push a new ROM to it over adb and flash it and it should boot up must fine.I wrote a tutorial on how to do it here: http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hello Stunts513, thanks a lot !
I try to make what you say.
1. I install the ADB drivers when the kindle is in twrp, i think it's ok :
2. i can try to push a new rom to the tablet, but i doesn't see the kindle on my computer :
I don't understand why i can't see my kindle in my computer.
In TWRP, i must activate some option to connect the kindle to the computer?
best regards
Martin
Because that feature is broken in twrp is why it doesn't show up as a MTP device. You need to download the adb command from that link I posted and run the adb push command to send then file to the device, its another method of transferring then file by using a command prompt instead of the usual windows explorer.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Because that feature is broken in twrp is why it doesn't show up as a MTP device. You need to download the adb command from that link I posted and run the adb push command to send then file to the device, its another method of transferring then file by using a command prompt instead of the usual windows explorer.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Ok, i will try.
I take the ROM and GAPP here :
http://forum.xda-developers.com/showthread.php?t=2543455
It's ok?
Yes that's the one, just push both of the files after you download them.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Yes that's the one, just push both of the files after you download them.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks Stunts
I try. When i tape the commande line, windows ask me : adbwinapi.dll not found.
You need to extract the dll's that were in the zip file to the same directory as the adb command, then it should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You need to extract the dll's that were in the zip file to the same directory as the adb command, then it should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Ok
And in TWRP, i must activate some options? Like "Mount" or other?
Nope, the stuff is setup fine as is. Just remember to do a factory reset(under the wipe button) before flashing the ROM. I personally would wipe the system partition as well but that's just me.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You need to extract the dll's that were in the zip file to the same directory as the adb command, then it should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I put ADB folder in c:/windows/system32/adb
In this folder i have :
- adb
-adbwinapi.dll
-adbwindusbapi.dll
-ROM CM11
-Gapps
Windows ask me adbwinapi.dll not found
Why'd you drop them into your system32 folder? Just make a folder on your desktop, drop the adb files and ROM into there, and CD into that directory from the command prompt and run the command, if it still does that then I'm guessing something like the command prompt wasn't being ran as admin or something.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Why'd you drop them into your system32 folder? Just make a folder on your desktop, drop the adb files and ROM into there, and CD into that directory from the command prompt and run the command, if it still does that then I'm guessing something like the command prompt wasn't being ran as admin or something.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Ok, on the folder in the desktop, i press shift, and run the command.
I type this into the command prompt: adb push rom-or-gapps-name-goes-here.zip /sdcard/
And it's ok, i think its on the kindle, but i dont find where is the rom and gapp
I found noting in SDcard folder in TWRP .
If it succeeded then in twrp hit wipe and do an factory reset, then hit install and it should let you navigate then internal memory, by default I think it starts out on /sdcard which happens to be where the ROM should have been pushed. So it should be there, if not then what did the command prompt say after you ran the push command?
Sent from my Amazon Kindle Fire HD using Tapatalk
---------- Post added at 06:41 AM ---------- Previous post was at 06:39 AM ----------
stunts513 said:
If it succeeded then in twrp hit wipe and do an factory reset, then hit install and it should let you navigate then internal memory, by default I think it starts out on /sdcard which happens to be where the ROM should have been pushed. So it should be there, if not then what did the command prompt say after you ran the push command?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Edit: i might have to continue this conversation in at least 4hours because I need to go to sleep. Sorry if I Don't respond for a bit.
Sent from my Amazon Kindle Fire HD using Tapatalk
Edit2: ah wonderful I double posted... This is why I hate switching between two apps when one starts messing up and the other one I'm not used to and hit the wrong button...
You can see here the command :
http://img15.hostingpics.net/pics/367766Sanstitre3.png
You can see here the command :
http://img15.hostingpics.net/pics/367766Sanstitre3.png
No pb, go to sleep Stunts, thanks a lot for your help
You must have a typo somewhere because it displayed the list of alp commands due to am syntax error. What exactly did you type into the command prompt? BTW for future reference if you right click in the command prompt and hit mark it let's you highlight the text so you can copy by pressing enter then paste it, though I'm kinda glad you didn't do that because without code brackets it would a been a mess. Yea I'll goto sleep now thanks.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You must have a typo somewhere because it displayed the list of alp commands due to am syntax error. What exactly did you type into the command prompt? BTW for future reference if you right click in the command prompt and hit mark it let's you highlight the text so you can copy by pressing enter then paste it, though I'm kinda glad you didn't do that because without code brackets it would a been a mess. Yea I'll goto sleep now thanks.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I will see for the syntax, thanks a lot for all :good:
I am very happy, cyanogenmod works! :good:
Thank you very much Stunts is thanks to you I won!
My problems were related to syntax.
My Kindle is save by you
Good to hear you managed to fix it while I was asleep.
Sent from my Amazon Kindle Fire HD using Tapatalk