I used Team win Recovery Project to wipe my phone Galaxy Nexus, and now when I plug the phone in to the lappy it doesn't show the sd card. Freaking out here cause I can't copy over a zip file to flash a ROM... please help...
The GNEX doesn't have an actual sdcard, so when you wiped the phone i'm guessing you wiped the virtual sd card.
You will have to adb push a rom to your phone.
One the top of the first Q&A page jubakuba has a guide that has a panic section in it.
The guide also shows how to install adb/fastboot and gives you the commands.
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
xskordeal said:
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
Click to expand...
Click to collapse
sorry, complete DOLT here. Where would I input the command?
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
How to get to a MS-DOS prompt or Windows command line
TheDodgey said:
sorry, complete DOLT here. Where would I input the command?
Click to expand...
Click to collapse
Click Start.
Click Run.
Type cmd or command and press enter.
gpfnzl said:
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
Click to expand...
Click to collapse
ok, following your instructions, and the instructions of the link, I have install ADB and can use cmd, however when I type adb shell, I get an error returning "device not found"
I see a lot of threads stating to make sure usb debugging is on, it was before I wiped the phone, but obviously I cant get to any settings at the moment.
on the verge of crying now, and noone likes to see a grown man cry
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
LOL
Normally if you can't see your device listed you haven't installed the drivers correctly.(or the correct drivers)
Also you have to open a command prompt window in the same folder as fastboot.exe and adb.exe
To do this in Windows 7:
Click the windows start button (bottom left hand corner)
In the search bar at the bottom type: cmd
At the top of the search list you will see the program cmd.exe right click and copy it.
Paste it into the same folder that has fastboot.exe and adb.exe
Now you can open the cmd window and type the command:
adb devices
Hit ENTER and if you have installed drivers correctly, the serial number of your phone will be listed.
If not, uninstall the drivers, download a new set of drivers from jubakuba or efrants guide and reinstall.
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
TheDodgey said:
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
Click to expand...
Click to collapse
didn't need to change the name of the rom zip. Just needed to type the full name of the .zip file.
Good to see it worked, and the tears have stopped
Related
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
neccoguy21 said:
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Know-Fear said:
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Click to expand...
Click to collapse
This is a very helpful way of doing things, but a little too long winded for CWM. But I'm thankful for you taking your time to respond and I'm happy to have this guide handy.
gpfnzl said:
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
Click to expand...
Click to collapse
A similar strategy to know-fear's, but different. Again, thank you very much for your help, but it's not the way I'll handle this one.
ÜBER™ said:
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
Click to expand...
Click to collapse
This was what I was looking for. Thank you so much for your time and help!
Sent from my Galaxy Nexus using xda app-developers app
Long winded perhaps. But it's the same thing for most phones running android. So in essence, once you learn it, you know it for good. I've been using the same method since back in the G-1 days. And honestly, those steps I listed take about 15 seconds to complete. It's just good to be thorough.
I wrote this guide a while back after fixing a friends phone, it has worked on others too so i decided id post it here for anyone that ran into this issue later down the road and did not want to run a ruu. This also works great if you want to start fresh before flashing roms.
Basically all this does it swap out recovery's and clean the SD, give it a fresh start.
You can find the full guide & Video here http://forums.team-nocturnal.com/showthread.php/1050
This involves unnecessarily deleting the contents of the internal sdcard.
The following method works 99% of the time, albeit in linux only:
1: reboot into recovery & do a mount usb storage (no mount sdcard)
this will just present your internal storage as a mass storage device to the system
2: do a
fsck.vfat /dev/sdX or /dev/ubX (whatever it gets detected as) - you can find out via (dmesg|tail)
Analogically, you can fix your data partition if it got corrupted.
You need to do it from recovery since not all roms have the fsck binaries available:
from recovery (copy - paste, unless you know what you're doing):
umount /cache
for x in {2,3,5}, do fsck.ext4 -fyD /dev/block/mmcblk0p1$x;sync;done;clear;echo done
XsMagical said:
I wrote this guide a while back after fixing a friends phone, it has worked on others too so i decided id post it here for anyone that ran into this issue later down the road and did not want to run a ruu. This also works great if you want to start fresh before flashing roms.
Basically all this does it swap out recovery's and clean the SD, give it a fresh start.
You can find the full guide & Video here http://forums.team-nocturnal.com/showthread.php/1050
Click to expand...
Click to collapse
Hi XsMagical this link no longer works. Can you provide me with the guide I'm having the issue with the corrupted SD card and my htc one x is bricked.
movadoevo8 said:
Hi XsMagical this link no longer works. Can you provide me with the guide I'm having the issue with the corrupted SD card and my htc one x is bricked.
Click to expand...
Click to collapse
what is your base number and hboot ?normally the sdcard thing is fixed long time ago
One-X-master said:
what is your base number and hboot ?normally the sdcard thing is fixed long time ago
Click to expand...
Click to collapse
How do i locate the Hboot number is that the serial# if so here it is HT265W300361
movadoevo8 said:
How do i locate the Hboot number is that the serial# if so here it is HT265W300361
Click to expand...
Click to collapse
no reboot into fastboot and you will see it there.... and base number you can see in settings/about then somewhere there
One-X-master said:
no reboot into fastboot and you will see it there.... and base number you can see in settings/about then somewhere there
Click to expand...
Click to collapse
hboot = 1.14.0002
movadoevo8 said:
hboot = 1.14.0002
Click to expand...
Click to collapse
do you have the one xl? try to update it to latest base
One-X-master said:
do you have the one xl? try to update it to latest base
Click to expand...
Click to collapse
Yes it's an XL, however i can't update, because any zip or file i throw in the SDCARD via twrp recovery after mounting as per my original post it disappears for some reason so i don't know how i would flash anything.
movadoevo8 said:
Yes it's an XL, however i can't update, because any zip or file i throw in the SDCARD via twrp recovery after mounting as per my original post it disappears for some reason so i don't know how i would flash anything.
Click to expand...
Click to collapse
can you not mount adb sideload and flash through that ?
I had yesterday night the problem that I wiped phone because I had some issues...then wanted to put Rom.zip through recovery on sdcard...problem was my pc didn't accepted it...so I tried to find a solution then I found the adb sideload function installed then again the adb and HTC one x driver and then I was able to put the zip on my sdcard...flashed then Rom and yes all is working now
Gesendet von meinem HTC One X mit Tapatalk 2
markb63 said:
can you not mount adb sideload and flash through that ?
Click to expand...
Click to collapse
I'm not sure how to do that and what that means. I know how to flash via TWRP recovery which is not working and flash boot images etc using "FASTBOOT".
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
One-X-master said:
I had yesterday night the problem that I wiped phone because I had some issues...then wanted to put Rom.zip through recovery on sdcard...problem was my pc didn't accepted it...so I tried to find a solution then I found the adb sideload function installed then again the adb and HTC one x driver and then I was able to put the zip on my sdcard...flashed then Rom and yes all is working now
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I can put the zip in there even if i remove the USB cable without unmounting and then plug the USB cable again i see the file inside the phone just fine, the problem is when I unmount to get back into TWRP recovery to install a zip then it doesn't show up. Very weird not sure what is going on, but from what i hear it's a corrupted SD CARD. I found a thread, that teaches you how to fix this, but the link is now broken. I have PM the original poster hope he will contact me back.
movadoevo8 said:
I'm not sure how to do that and what that means. I know how to flash via TWRP recovery which is not working and flash boot images etc using "FASTBOOT".
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
I can put the zip in there even if i remove the USB cable without unmounting and then plug the USB cable again i see the file inside the phone just fine, the problem is when I unmount to get back into TWRP recovery to install a zip then it doesn't show up. Very weird not sure what is going on, but from what i hear it's a corrupted SD CARD. I found a thread, that teaches you how to fix this, but the link is now broken. I have PM the original poster hope he will contact me back.
Click to expand...
Click to collapse
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
markb63 said:
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
Click to expand...
Click to collapse
Thank you so much! I will definitely toy with this later to see if it works.
---------- Post added at 10:07 AM ---------- Previous post was at 09:45 AM ----------
markb63 said:
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
Click to expand...
Click to collapse
adb sideload /path/to/rom.zip
this is not working for me instead of just displays all the commands that adb can do.
I have gone and go to advanced>adb sideload in twrp supported version
on my computer i have a folder called c:\fastboot with the adb software and it's the version that supports adb side load according to the instructions so i have met all the requirements. However when i run the command
adb sideload cm.zip
as i am already in the c:\fastboot folder via command prompt all i get is a display of all the commands i can use with adb as if i just typed "adb" and it displays all the commands.
I also tried typing
adb sideload c:\fastboot\cm.zip
this did not work either same result. FYI cm.zip is the name of the rom file.
I also tried typing
adb sideload /fastboot/cm.zip
Any thoughts?
movadoevo8 said:
Thank you so much! I will definitely toy with this later to see if it works.
---------- Post added at 10:07 AM ---------- Previous post was at 09:45 AM ----------
adb sideload /path/to/rom.zip
this is not working for me instead of just displays all the commands that adb can do.
I have gone and go to advanced>adb sideload in twrp supported version
on my computer i have a folder called c:\fastboot with the adb software and it's the version that supports adb side load according to the instructions so i have met all the requirements. However when i run the command
adb sideload cm.zip
as i am already in the c:\fastboot folder via command prompt all i get is a display of all the commands i can use with adb as if i just typed "adb" and it displays all the commands.
I also tried typing
adb sideload c:\fastboot\cm.zip
this did not work either same result. FYI cm.zip is the name of the rom file.
I also tried typing
adb sideload /fastboot/cm.zip
Any thoughts?
Click to expand...
Click to collapse
do you have sdk on your desktop ? ... if so reboot your phone into recovery and connect to your pc via usb-open up sdk\platform tools-enter into adb sideload in recovery,then put your curser in the platform tools folder-press and hold the shift key and right click mouse,you should see open command window here-click.then enter adb devices-your device should show as ********* sideload in the command adb window.your device should now be asking for you to flash ?
markb63 said:
do you have sdk on your desktop ? ... if so reboot your phone into recovery and connect to your pc via usb-open up sdk\platform tools-enter into adb sideload in recovery,then put your curser in the platform tools folder-press and hold the shift key and right click mouse,you should see open command window here-click.then enter adb devices-your device should show as ********* sideload in the command adb window.your device should now be asking for you to flash ?
Click to expand...
Click to collapse
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
movadoevo8 said:
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
Click to expand...
Click to collapse
I think your in fastbboot folder ? you need to be in platform tools .my platform tools has a lot more inside than yours
movadoevo8 said:
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
Click to expand...
Click to collapse
You don't need whole sdk ...if you activate adb sideload in recovery go to device manager on pc there should be something with android device or so ...then right click on it then update drivers or so then something with from computer and download at first the adb drivers for windows 8 extract to a folder a then in the driver update thing select this folder and update it or so...sorry am atm to stupid to write in English but you can sideload because adb drivers aren't working properly...you should also install HTC sync manager etc so it should be fixed then ...if not Google HTC one x adb driver windows 8 many instructions to get all working properlY
Gesendet von meinem HTC One X mit Tapatalk 2
One-X-master said:
You don't need whole sdk ...if you activate adb sideload in recovery go to device manager on pc there should be something with android device or so ...then right click on it then update drivers or so then something with from computer and download at first the adb drivers for windows 8 extract to a folder a then in the driver update thing select this folder and update it or so...sorry am atm to stupid to write in English but you can sideload because adb drivers aren't working properly...you should also install HTC sync manager etc so it should be fixed then ...if not Google HTC one x adb driver windows 8 many instructions to get all working properlY
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I'm setting this up on my windows 7 machine, now I think i had an issue once on win 8. Updates to follow, thanks.
markb63 said:
I think your in fastbboot folder ? you need to be in platform tools .my platform tools has a lot more inside than yours
Click to expand...
Click to collapse
EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways
lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app
when i tried to push error device not found lol
lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app
lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.
lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*
xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1
Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again
Ok i rooted my kindle fire and then decided i did not want it rooted any more so i went in to my TWRP setting thing on boot up and stupid me never made a back up and i erased every thing i hit wipe and now theres no firmware on it no ROM thing installed im not a techy person soooo plz give me detailed fixes i really want it fixed its stuck in boot loop but i can still accsess the TWRP settings i just dont know how to use it iv looked up a billion videos but no body has a back up file on the internet so i can just download it and install it on my kindle i used KFU the latest version and it can detect my kindle soooo wat do i do and plz dont just say im screwd cus i do not want to hear that i want ANSWERS pls its been like this for months and i want it fixed i dont want a $200 paper weight
vampire4383 said:
Ok i rooted my kindle fire and then decided i did not want it rooted any more so i went in to my TWRP setting thing on boot up and stupid me never made a back up and i erased every thing i hit wipe and now theres no firmware on it no ROM thing installed im not a techy person soooo plz give me detailed fixes i really want it fixed its stuck in boot loop but i can still accsess the TWRP settings i just dont know how to use it iv looked up a billion videos but no body has a back up file on the internet so i can just download it and install it on my kindle i used KFU the latest version and it can detect my kindle soooo wat do i do and plz dont just say im screwd cus i do not want to hear that i want ANSWERS pls its been like this for months and i want it fixed i dont want a $200 paper weight
Click to expand...
Click to collapse
Relax and take a deep breath. Panic is your enemy. Your situation is not as bad as it may seem.
Having said that, with the "billion" videos you claimed to have watched, surely you must have seen ADB mentioned...once or twice? Have you attempted to use ADB for part of what it is intended...to transfer (push) a ROM to your sdcard?
Same issue with me
soupmagnet said:
Relax and take a deep breath. Panic is your enemy. Your situation is not as bad as it may seem.
Having said that, with the "billion" videos you claimed to have watched, surely you must have seen ADB mentioned...once or twice? Have you attempted to use ADB for part of what it is intended...to transfer (push) a ROM to your sdcard?
Click to expand...
Click to collapse
I have tried kfu utility, i have downloaded stock from amazon site only to get an error with update.zip, and now I am trying to use my mac. I don't know what else to do!!!!
I can tell you how to get a ROM installed from a PC...
Download a ROM zip file. I use the CM10.2 nightly build with 3.0.72 kernel (see that thread under development). Copy the downloaded zip file to the same folder on your PC that your adb.exe is in. Boot the Kindle into TWRP. Press Advanced and ADB Sideload. Slide the slider. Plug the Kindle into the PC. In a command prompt on your PC go into the folder where you ADB.exe is. Type adb sideload filename.zip (use the filename of the ROM zip file you downloaded). That should get a ROM on your kindle that you can boot into at least. If you use a Cyanogenmod ROM, don't forget to download the compatible GAPPS zip for it and copy it to internal storage on the Kindle and use TWRP to install that zip file.
You can also look here for zip files. I don't know if the amazon-OS zip file would work to restore you to original or not, though.
http://goo.im/devs/Hashcode/otter2
I'm with you until adb file is that a part of the kfu
Sent from my SGH-I747 using xda app-developers app
imblessed68 said:
I'm with you until adb file is that a part of the kfu
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It should be. You want to look for adb.exe . I use KFFirstAide so my adb.exe file is in C:\KFFirstAide. There might also be a sub folder called "stuff" that I think some of the utilities have adb.exe in.
imblessed68 said:
I'm with you until adb file is that a part of the kfu
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
can you please tell me what to type in cmd box I downloaded 10.2 from link you gave I may almost be there lol
imblessed68 said:
can you please tell me what to type in cmd box I downloaded 10.2 from link you gave I may almost be there lol
Click to expand...
Click to collapse
So you should have downloaded the file: cm-10.2-20130731-UNOFFICIAL-otter2.zip and that file should be in the same folder on your PC as the adb.exe file is.
You will boot your Kindle into TWRP. Press Advanced and then ADB Sideload. Plug your Kindle into a USB port on your PC.
From the cmd box, you will type CD C:\folder In place of folder you put in the path to the adb.exe file, for me it is C:\KFFirstAide, buy yours will probably be different.
Once you are in the same folder with the adb.exe file and the zip file that you downloaded, you will type "adb sideload cm-10.2-20130731-UNOFFICIAL-otter2.zip" without the quotes. The zip file should be copied to a temporary location on the Kindle and then TWRP should flash it.
You should then be able to boot the Kindle into CyanogenMod. Next you will have to find the gapps zip file that goes with the version of CM10.2 that you installed, copy the gapps zip file to the "sdcard" on the Kindle. Reboot into TWRP and install the gapps zip file. Also, don't forget to turn on ADB (or USB Debugging) under the Developer Options in the system settings.
After you install the gapps file, you will have a complete ROM and ADB access again.
Sorry I can't help more with going back to stock ROM, I am out at sea at the moment on USS Nimitz and don't have a very good internet connection.
---------- Post added at 09:01 PM ---------- Previous post was at 08:12 PM ----------
This should be the GAPPS you need to go with CM10.2:
http://goo.im/gapps/gapps-jb-20130813-signed.zip
When I type adb sideload it says windows can't find adb I followed ur instructions carefully. I have the kffirstaide, I put the cm2 zip in that folder where a lot of other stuff is in and still no luck
Sent from my SGH-I747 using xda app-developers app
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
So I've followed ur instructions even put the kffirstaide and I keep getting windows can't find adb side load I am so frustrated becuz I know I'm so close now can the kffirstaide help me without doing adb sideload
Sent from my SGH-I747 using xda app-developers app
imblessed68 said:
When I type adb sideload it says windows can't find adb I followed ur instructions carefully. I have the kffirstaide, I put the cm2 zip in that folder where a lot of other stuff is in and still no luck
Sent from my SGH-I747 using xda app-developers app
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
So I've followed ur instructions even put the kffirstaide and I keep getting windows can't find adb side load I am so frustrated becuz I know I'm so close now can the kffirstaide help me without doing adb sideload
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Assuming that you extracted the KFFirstaide to your C:\ drive....
This is for Windows 7, but it should be close for Windows XP too:
Click on your Start button, then All Programs, then Accessories. Right click on Command Prompt and select Run As Administrator. (I don't know if that is necessary, but I do it). Click OK or Yes to the windows prompt asking if you want to run it as Administrator. When the command prompt window opens, enter CD C:\KFFirstaide (again, assuming that is where you extracted the KFFirstaide zip file to). You did extract it after you downloaded it, right? and not just copy the zip file?
Now type DIR *.EXE one of the files listed in the listing should be adb.exe.
Now type DIR *.ZIP one of the files listed in the listing should be the CM10.2 zip file that you downloaded.
If you see those two files, it means you extracted the KFFirstaide correctly and you have the CM10.2 zip file in the right place and your command prompt is pointed to the right folder. Now if you type adb by itself, you should see all the options for adb listed. If that works, then you should be able to boot into TWRP, start ADB Sideload on the Kindle, plug it into the computer and then do adb sideload cm-10.2-20130731-UNOFFICIAL-otter2.zip on your computer and it should work. Note that sideload is only one word.
If you don't see adb.exe listed in the directory above, then search for it on C:\ using the Windows search function to figure out where it is.
NavyLCDR said:
Assuming that you extracted the KFFirstaide to your C:\ drive....
This is for Windows 7, but it should be close for Windows XP too:
Click on your Start button, then All Programs, then Accessories. Right click on Command Prompt and select Run As Administrator. (I don't know if that is necessary, but I do it). Click OK or Yes to the windows prompt asking if you want to run it as Administrator. When the command prompt window opens, enter CD C:\KFFirstaide (again, assuming that is where you extracted the KFFirstaide zip file to). You did extract it after you downloaded it, right? and not just copy the zip file?
Now type DIR *.EXE one of the files listed in the listing should be adb.exe.
Now type DIR *.ZIP one of the files listed in the listing should be the CM10.2 zip file that you downloaded.
If you see those two files, it means you extracted the KFFirstaide correctly and you have the CM10.2 zip file in the right place and your command prompt is pointed to the right folder. Now if you type adb by itself, you should see all the options for adb listed. If that works, then you should be able to boot into TWRP, start ADB Sideload on the Kindle, plug it into the computer and then do adb sideload cm-10.2-20130731-UNOFFICIAL-otter2.zip on your computer and it should work. Note that sideload is only one word.
If you don't see adb.exe listed in the directory above, then search for it on C:\ using the Windows search function to figure out where it is.
Click to expand...
Click to collapse
Its nice to be thanked for all the effort you put in.....
I'll thank you instead for not losing it.
Sent from my LG-D801 using Tapatalk
Dear Exprts
Kindly check this how to fix this problem
when i give a command in CMD (c:\fastboot is not recognized as an internal or external command, oparebale program or batch file)
please give me the procedure as soon as possible ...
i cant unlock the boothloader
Thnks
Deep
I dont get your question. What command u typed? Check if your cmd console working directory is the same as fastboot localization.
Just ctrl rght click in folder where fastboot is and click open command window.
Sent from my One V using xda app-developers app
dipusmart said:
Dear Exprts
Kindly check this how to fix this problem
when i give a command in CMD (c:\fastboot is not recognized as an internal or external command, oparebale program or batch file)
please give me the procedure as soon as possible ...
i cant unlock the boothloader
Thnks
Deep
Click to expand...
Click to collapse
You must have fastboot.exe and the 2 dlls at the same directori, where you are at the moment at console (e.g. you wrote c:\fatsboot, so you need to have fastboot.exe and the 2 dlls at c:\ root to run them.)
I recommend to run fastboot and/or adb from a subdirectory from root, e.g. c:\htc\
I havehave fastboot.exe and the 2 dlls at the same directori (I rote c:\fastboot....but the same result ...
I don't have any root file in c drive
i am attaching the file ...
Ken-Shi_Kun said:
You must have fastboot.exe and the 2 dlls at the same directori, where you are at the moment at console (e.g. you wrote c:\fatsboot, so you need to have fastboot.exe and the 2 dlls at c:\ root to run them.)
I recommend to run fastboot and/or adb from a subdirectory from root, e.g. c:\htc\
Click to expand...
Click to collapse
Check this command in attach file
& told me , whats the problem in command
dipusmart said:
Check this command in attach file
& told me , whats the problem in command
Click to expand...
Click to collapse
don't know what the problem here, but I had errors like this on windows 8.1 and win8, which based on the poor command-line support...
try to move to the folder itself first with cd command, then fastboot as command.
dipusmart said:
Check this command in attach file
& told me , whats the problem in command
Click to expand...
Click to collapse
First, do not place files in the root (system could have some restrictions to run files from here). Place them in any folder and run from there (e.g. c:\fb\fastboot.exe)
Second, usualy you must be in the folder where the running file is. So do this:
cd c:\fb
fastboot ...
---------- Post added at 03:07 PM ---------- Previous post was at 02:59 PM ----------
Btw, are you really sure you want to take the risk with unlocking/rooting/flashing? If you are not quite familiar with a simple computer tasks there is a big chance you will go wrong and the phone will become unuseful. Unless you have many of them and just playing around. =)
Have you tried using the windows AIO tool?
http://forum.xda-developers.com/showthread.php?t=1676686
you may find it easier, but please do read all the instructions carefully especially about making a backup.
thnks guys....
now i don't have warranty ...so i want to upgrade my phone
urgents.....!!!!!
i am already done unlocking/rooting
but i have to install titanium kiss kernal i just stuck in command prompt ..its just waiting for device
what can i do ,,,
dipusmart said:
urgents.....!!!!!
i am already done unlocking/rooting
but i have to install titanium kiss kernal i just stuck in command prompt ..its just waiting for device
what can i do ,,,
Click to expand...
Click to collapse
What exactly the command prompt says?
You have to start your phone in the fastboot mode to accept external commands. So I guess the command prompt is waiting until the phone will get to that mode.
kvestas said:
What exactly the command prompt says?
You have to start your phone in the fastboot mode to accept external commands. So I guess the command prompt is waiting until the phone will get to that mode.
Click to expand...
Click to collapse
In command prompt with your phone connected, and USB debugging turned on in your developer options, and in the folder with your boot.img (you'll need to rename the hellboy kernel file to just boot.img)
type
<adb devices>
you should see a reply showing your phones ID if you get this go for
<adb reboot bootloader>
wait for the phone to reboot to your white bootloader screen then go for
<fastboot flash boot boot.img>
then once the kernel is in
<fastboot reboot>
Again I strongly recommend using an AIO program to make sure you haven't missed a step. Its great to learn all the ways to work with your phone, but its primary use is a phone, if it breaks it won't be able to do that.