Related
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
We tried a different computer and solved the ADB problem, then I did just like you told and it's OK now.
Thank you.
You're welcome. glad it's all all OK for you
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Same problem as you --> fixed
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
If you found that adb worked from a different machine, you might check whether you had any tethering drivers installed (eg EasyTether) on the machine that was not able to see the phone via adb. I found that they interfered with adb's operation on my Macbook previously; it was maddening.
woraz said:
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Click to expand...
Click to collapse
if you have problems always use Hasoon All-In-One_Kit for HTC
Am having the same issues, have tried everything I can think off and everything google has suggested. I'm beyond stuck any and all help would be greatly appreciated
my bad exp
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Was he by chance having issues charging his phone before he wiped it?
Myself and my brother both a had issues with the USB port going. Couldn't charge while phone was on. PC wouldn't pick it up so no adb. However was able to pickup fastboot and charge while in fastboot mode.
If that's the case you could try running a zip in oemRUU mode just to get an os on there.
Is he soff?
Sent from my HTC One using xda premium
makkasi said:
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Click to expand...
Click to collapse
This worked for me. Thanks!!
Once I removed all the extra crap from control panel and used the latest I was able to do adb devices successfully from bootloader / recovery.
I was just having the same problem on the new LG G2 (D803). It was perplexing because the computer *bleeped* every time it attached so I knew that it saw something. Based on the tips here I went to the Device Manager and sure enough there it was... I reinstalled the drivers inside device manager and then I got an easy adb hit on the phone... hmmm :fingers-crossed:
EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
timekills said:
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
Click to expand...
Click to collapse
Man, I just wanted to say thank you. I've been stuck on this for hours and this did the trick!
Worked
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
the drivers mentioned here worked for me.
Device : HTC One M7
Recovery : TWRP
Thanks
Thank you so much! This universal driver worked for me! (HTC One Mini with TWRP, soft-bricked)
NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
Years later, thank you sir, for helping a noob with "adb kill-server"
I was so freaked as to why TWRP wasn't sideloading but PhilZ was.
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
ADB didn't recognize my Xperia SP in Clockworkmod. That driver worked like a charm Thank you!
This worked for me...
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
Thank you so much for this. This really helped me out.
Hi everyone, today i would like to ask for your help with a pretty big problem i have with my Kindle fire HD, you see, i was updating from my current rom 7.4.4 to CM 10.2. to achieve thi i followed this tutorial http://forum.xda-developers.com/showthread.php?t=2271909 , everything was going fine until i installed 2nd-Bootloader and TWRP recovery. The problem came up here, when i realized that i forgot to move the rom and the files for google play into the SD card, now whenever i try to do this i can't seem to get my PC to recognize the Kindle with TWRP (i can browse my files and such with TWRP directly through the kindle itself) i tried to move the required file with adb and fastboot but i can't get it to work.
The kindle is rooted and running version 7.4.6 from amazon.
i have a backup for the rom and the files but i can't use fastboot.
i have a backup for each of the following files: boot0block, stock-boot, stock-recovery, stock-system
all the adb drivers and sdk are functioning perfectly.
When i connect it to my PC with windows 7 i can see the kindle recognized by the device manager but it has yellow triangle next to the icon.
i also tried using an otg cable but the kindke did not recognize it.
any and all help is appreciated, i don't want my tablet to die Dx
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Ph0enix_216 said:
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Click to expand...
Click to collapse
I tried this but the problem is that the pc not find device , it show me in device manager yellow triangle next to the icon of kindle
When i send a adb command , the adb say "Device not found"
Thanks you anyway!
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
stunts513 said:
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Click to expand...
Click to collapse
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Shur'tugal said:
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Click to expand...
Click to collapse
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for your help your save my tablet
Thanks you very much
Finally i exit for this bricked
Enviado desde mi GT-I9300 usando Tapatalk 4
I have a dude im install CM 10.2 perfect , but i dont remember install de google apps as i have to do now?
Thanks
One step further
My apologies for hijacking this thread. I had made the same error as the OP. however, instead of searching here for solution, I panicked and wiped the cache and user data using the SR tool and wiped everything. Now unfortunately my kfhd tells me it can't boot, which my incompetent mind tells me is likely because I have no rom?
I've tried to use first aide to do a system recovery but I get told the files are too large and it can't do anything.... Any suggestions or thoughts from people? Appreciate any help I can get. Been up late the last 3 days trying to sort this out, while I thought I was going to provide m wife with a slick android device!!
That's odd, I wouldn't think wipe your data partition and cache would cause that to happen, then again there are some files stored under data the system uses out side of apk's so I guess that could be why. Did you get your kindle into fastboot? If you did I would suggest trying to use kfhd system restore tool if kffa didn't work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
deeman77 said:
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
Click to expand...
Click to collapse
All the files, or just the system.img?
soupmagnet said:
All the files, or just the system.img?
Click to expand...
Click to collapse
each one of them unfort.
Do you have twrp installed?
hloomsc some
soupmagnet said:
Do you have twrp installed?
Click to expand...
Click to collapse
I did. Not sure i do now post trying to do a wipe. Don't see any blue when I start up, just the original kindle letter coloring, after which I get a message saying it can't boot
any suggestions anyone or is my kfhd pretty much killed? there's got to be a way to load some rom on to it!!
You should be able to load the original images over fastboot, something just isn't working right. I would say its far from hard bricked, it should still be fixable, its just a matter of troubleshooting it. If you have the kindle fire system image I would try manually flashing it but you need to know what you are doing. If you CD into the SRT folder where im assuming the IMG files are in the same folder as fastboot, try running "fastboot -i 0x1949 flash system system.img" think I got the syntax right, haven't had to ever use fastboot myself, anyways if you run that what does it report back? Hopefully not the same error, or it might be something messed up with the image.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
thanks for the advice. ended up re downloading the images again and this time it worked. go figure.
back to starting again to get my custom rom on.
once i have a custom rom, guessing there are no amazon bits left in there that would cause any updates to come through right?
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Good afternoon: I bricked a nice 8.9 tablet several weeks ago using ADB sideload...
I used ADB Sideload to install Gapps since I was already in TWRP and was too lazy to reboot and transfer the gapps.zip file to my tablet.
The sideload installed the gapps.zip as I expected it to and I was brought back to the main TWRP screen.
When I clicked on reboot/reboot system, the tablet started flashing the three partitions (boot, recovery and system) as I was watching. TWRP then left me at the booting screen doing nothing. I did not know why the tablet decided to flash the three main partitions but, I opted to push the power button and that was the last time I saw my tablet.....
Apparently ADB sideload is only for ROM's? I had only used it to flash ROMs prior but, I thought ADB Sideload should be able to install any properly zipped file designed to flash with TWRP?
Regards
Hello,
I've rooted my Kindle fire HD 7 and installe TWRP recovery and then installed PAC-man rom, but it has had some problems, and I'm going to recovery and wipped all, the system too, for reinstall all from zero, but now i'm unable to connect the usb storage at pc and tranfer the .zip of rom on the memory of my device.
I can only enter in the recovery but I'm unable to use the usb storage, maybe I think the trouble is the driver, how can I resolve?
Thanks you, and sorry for my bad english
Fefe94
fefe94 said:
Hello,
I've rooted my Kindle fire HD 7 and installe TWRP recovery and then installed PAC-man rom, but it has had some problems, and I'm going to recovery and wipped all, the system too, for reinstall all from zero, but now i'm unable to connect the usb storage at pc and tranfer the .zip of rom on the memory of my device.
I can only enter in the recovery but I'm unable to use the usb storage, maybe I think the trouble is the driver, how can I resolve?
Thanks you, and sorry for my bad english
Fefe94
Click to expand...
Click to collapse
Hello, you can use this tutorial to get a ROM pushed onto TWRP http://forum.xda-developers.com/showthread.php?t=2459498 also here are some updated drivers that will be useful to you http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Try sideload with ADB in recovery.
fefe94 said:
Hello,
I've rooted my Kindle fire HD 7 and installe TWRP recovery and then installed PAC-man rom, but it has had some problems, and I'm going to recovery and wipped all, the system too, for reinstall all from zero, but now i'm unable to connect the usb storage at pc and tranfer the .zip of rom on the memory of my device.
I can only enter in the recovery but I'm unable to use the usb storage, maybe I think the trouble is the driver, how can I resolve?
Thanks you, and sorry for my bad english
Fefe94
Click to expand...
Click to collapse
Try this and see if it help,
In TWRP, go to 'advanced' -> 'ADB Sideload'.
Connect your Kindle to the computer.
Start CMD on your computer.
Type command 'adb kill-server' and than 'adb devices',
You should see a list with recovery listed.
You can do adb push and upload the zip files to the sdcard from there
for example, adb push <local file name> /sdcard/
Once you are done pushing the files over you should be able to flash them from the recovery.
Hope this helps,
Thanks you everyone!
With adb push i just putted and installed the zip on my kindle
Thanks a lot
But the problem to connect the device like a mass storage is again here ahah but is a driver problem... beacause in my device i can see connected as a media device... some help?
fefe94 said:
Thanks you everyone!
With adb push i just putted and installed the zip on my kindle
Thanks a lot
But the problem to connect the device like a mass storage is again here ahah but is a driver problem... beacause in my device i can see connected as a media device... some help?
Click to expand...
Click to collapse
I've now unistalled the driver and reconnected the device and now workd all propely!
Thanks a lot everyone
fefe94 said:
I've now unistalled the driver and reconnected the device and now workd all propely!
Thanks a lot everyone
Click to expand...
Click to collapse
You're welcome. Yep, sometimes just a quick uninstall and re-install of the drivers works like a charm.
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
Hi mates, please help.
I have just update my girlfriends HTC One M7.
It was a 4.2 Android version from ARHD. I didn't notice that I needed to update Recovery in order to run new ROMs and now is looping in HTC logos.
The problem is that Fastboot isn't working with Windows 8.1 (I've been hours trying different drivers).
ADB is working right, but I can not install RECOVERY.IMG throught recovery or sideload.
I was thinking in installing through sideload an old ROM that works with my Recovery but I can not find any.
¿Any other solution?
¿A factory reset will work?
Thanks,
I'm in a hurry, i'm leaving soon and i do not like to let her with a brick mobile.
SergiNS said:
Hi mates, please help.
I have just update my girlfriends HTC One M7.
It was a 4.2 Android version from ARHD. I didn't notice that I needed to update Recovery in order to run new ROMs and now is looping in HTC logos.
The problem is that Fastboot isn't working with Windows 8.1 (I've been hours trying different drivers).
ADB is working right, but I can not install RECOVERY.IMG throught recovery or sideload.
I was thinking in installing through sideload an old ROM that works with my Recovery but I can not find any.
¿Any other solution?
¿A factory reset will work?
Thanks,
I'm in a hurry, i'm leaving soon and i do not like to let her with a brick mobile.
Click to expand...
Click to collapse
Win 8.1 does not work with lower hboots. You should try a Win 7 computer or Linux on USB.
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
If you get "no permissions ?????????" when trying to use adb, type:
Code:
killall adb
Disconnect the phone for a few seconds, then reconnect and type:
Code:
sudo adb devices
adb should now work as normal without the sudo prefix.
Click to expand...
Click to collapse
majmoz said:
Win 8.1 does not work with lower hboots. You should try a Win 7 computer or Linux on USB.
Click to expand...
Click to collapse
¿Isn't just easier to flash an old ROM that doesn't need TWRP 2.6 or higher?
I'm not used into Linux
Thanks a lot, please give any alternative you know.
SergiNS said:
¿Isn't just easier to flash an old ROM that doesn't need TWRP 2.6 or higher?
I'm not used into Linux
Thanks a lot, please give any alternative you know.
Click to expand...
Click to collapse
Yes, if you can find an older ROM that doesn't require an updated custom recovery. However, you wanted to update your girlfriends ROM and in order to do that you will need the newer custom recovery!
The other option, if you can find a newer RUU you could flash that and possibly Win 8.1 will work with the higher hboot.
Personally, Linux is not that difficult and if you follow the instructions posted you will not have an issue.
majmoz said:
Yes, if you can find an older ROM that doesn't require an updated custom recovery. However, you wanted to update your girlfriends ROM and in order to do that you will need the newer custom recovery!
The other option, if you can find a newer RUU you could flash that and possibly Win 8.1 will work with the higher hboot.
Personally, Linux is not that difficult and if you follow the instructions posted you will not have an issue.
Click to expand...
Click to collapse
I'm installing it on a pendrive right now.
Hope is easy.
Is taking time "Creating a persistent File"
As it seems, I can get files from HDD from Ubuntu isn't it?
Thanks
SergiNS said:
I'm installing it on a pendrive right now.
Hope is easy.
Is taking time "Creating a persistent File"
As it seems, I can get files from HDD from Ubuntu isn't it?
Thanks
Click to expand...
Click to collapse
Yes you will be able to access files on your pc's harddrive from the Linux pendrive. But it's better to copy them to the Linux home folder as in my guide before flashing. This is why you need the persistent file. It's like a Virtual Hard drive on your usb stick
Otherwise it will complicate flashing with long file paths needed for the adb and fastboot commands.
Just follow my mini guide and you'll be fine
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Yes you will be able to access files on your pc's harddrive from the Linux pendrive. But it's better to copy them to the Linux home folder as in my guide before flashing. This is why you need the persistent file. It's like a Virtual Hard drive on your usb stick
Otherwise it will complicate flashing with long file paths needed for the adb and fastboot commands.
Just follow my mini guide and you'll be fine
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Thanks a lot mate.
Right now is all done.
I will keep Ubuntu in my pendrive, it can help me in many ways.
Thanks for the guide and for the quick answers.
Always a pleasure to be in this forum.
SergiNS said:
Thanks a lot mate.
Right now is all done.
I will keep Ubuntu in my pendrive, it can help me in many ways.
Thanks for the guide and for the quick answers.
Always a pleasure to be in this forum.
Click to expand...
Click to collapse
Your welcome. Glad it got you out of trouble, Linux ain't so scary eh! [emoji12]
P.s no need to say thanks, there's a button for that sure majmoz would appreciate one or two :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good: