My prime is stuck in the splash screen and I can't get it to go further than that. I've been reading and been told I can push the ROMs zip file with the adb push command. The zip I downloaded on my computer is in my downloads folder. What would I exactly need to put in the command window to push the zip to the internal memory of my prime?
Sent from my Galaxy Nexus using xda premium
Nilsonf said:
My prime is stuck in the splash screen and I can't get it to go further than that. I've been reading and been told I can push the ROMs zip file with the adb push command. The zip I downloaded on my computer is in my downloads folder. What would I exactly need to put in the command window to push the zip to the internal memory of my prime?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Number 1, stick your ROM into the same folder that adb is in.
Number 2, read up about command line and terminal. (Trust me, you should do this)
Number 3, with your new found knowledge, push that file onto your internal storage. Example "adb push /ROM.zip /sdcard" !!!!!!
It's as simple as that sometimes.
The thing I don't get is what am I supposed to put on the adb push /ROM.zip /sdcard part
Sent from my Galaxy Nexus using xda premium
adb
Run adb devices, this will let you know if your drivers are working correctly, you should get
Recovery and your devices serial number, then if your zip is named virtuous.zip the command line is,
adb push virtuous.zip /sdcard/
You put the name of the zip file in there to push, /sdcard/ puts it on your root directory.
dklue said:
Run adb devices, this will let you know if your drivers are working correctly, you should get
Recovery and your devices serial number, then if your from zip is named virtuous.zip the command line is,
ad push virtuous.zip /sdcard/
You put the name of the zip file in there to push, /sdcard/ puts it on your root directory.
Click to expand...
Click to collapse
I've been doing that but it doesn't work
Sent from my Galaxy Nexus using xda premium
adb
Can you put it into cwm recovery ? When off hold volume down and the power button,
When little white letters come up, hit volume up, it should be in cwm when your adb pushing files, you can also try continuing to hold down on volume and then you get the three choices,
Android, USB, wipe data, it may push in the USB choice, read in the development section how
to unbrick your transformer prime, hopefully its a soft brick.
dklue said:
Can you put it into cwm recovery ? When off hold volume down and the power button,
When little white letters come up, hit volume up, it should be in cwm when your adb pushing files, you can also try continuing to hold down on volume and then you get the three choices,
Android, USB, wipe data, it may push in the USB choice, read in the development section how
to unbrick your transformer prime, hopefully its a soft brick.
Click to expand...
Click to collapse
Yeah when I try to push the file its in CWM and I type adb devices it recognizes it in recovery and the serial. I put adb push Primalicious_9.4.2.21._Final.zip /sdcard/ enter and it says no such file. Is it supposed to be in a specific folder or am I doing something wrong? I already unbricked it I just need to load the ROM
Sent from my Galaxy Nexus using xda premium
adb
The rom zip file should be in the directory where your adb.exe is. So if its in say
Program files/android/tools that's where you need to put the zip, otherwise it won't know
Where it is.
dklue said:
The rom zip file should be in the directory where your adb.exe is. So if its in say
Program files/android/tools that's where you need to put the zip, otherwise it won't know
Where it is.
Click to expand...
Click to collapse
Is this right?
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
adb
Yes that's right, you may want to rename it prime.zip, cause it may be .zip.zip or something,
or it may be a zip inside a zip.
dklue said:
Yes that's right, you may want to rename it prime.zip, cause it may be .zip.zip or something,
or it may be a zip inside a zip.
Click to expand...
Click to collapse
So rename the ROM prime.zip? And try that?
Sent from my Galaxy Nexus using xda premium
adb
You need to put the full file name,
adb push primalicious.zip /sdcard/
That's just the example, put the correct name in and include .zip.
I changed the name to prime.zip so I tried adb push prime.zip /sdcard/ and adb push prime.zip.zip /sdcard/ and it says no files found
Sent from my Galaxy Nexus using xda premium
adb
Do you have a backup to restore in cwm ? Or try to unmount /staging and mount /Data
In cwm and try
adb push prime.zip /data/local/
Otherwise I'm not sure why its not recognizing that file, I bricked my prime and someone in irc channel sent me a blob file, and he told me to push it to /data/local/
And it worked, I had to use win xp cause I couldn't get it to work on win 7, but your getting the correct response from adb devices, so I'm not sure,
---------- Post added at 09:22 PM ---------- Previous post was at 09:11 PM ----------
http://android.dkszone.net/copy-transfer-files-android-sd-card-adb-windows
dklue said:
Do you have a backup to restore in cwm ? Or try to unmount /staging and mount /Data
In cwm and try
adb push prime.zip /data/local/
Otherwise I'm not sure why its not recognizing that file, I bricked my prime and someone in irc channel sent me a blob file, and he told me to push it to /data/local/
And it worked, I had to use win xp cause I couldn't get it to work on win 7, but your getting the correct response from adb devices, so I'm not sure,
Click to expand...
Click to collapse
Ok thank you for your help. I will try to do that tomorrow cause I'm tired of messing with it for tonight lol. Hopefully I can get it to work
Sent from my Galaxy Nexus using xda premium
FIX!! - How to adb a zip ROM through CWM!!!
Hello there, for the last few nights I was having the same issue as you. I bricked my tablet, fixed it, and then just got stocked on the recovery with no data on my SDCARD. After searching and searching for hours online I found your post last night. And after reading the comments from "dklue", i googled some more information about something very important that me and you were missing!: "Blob files".
The "Primalicious_9.4.2.21._Final.zip" file or the "AOKP.zip" file will not work just like that because they are not in the format to be "Pushed" using the push command (At least thats what i kinda realized lol) anyhow, so i went online and searched for a ROM on Blob format and luckily i found the following!:
[ROM][WW][US][9.4.2.21] Primeval: The STOCK stock rom
So here is what worked for me thanks God! lol (Keep in mind that for some reason this process did not work for me on the new "CWM Touch Recovery 5.8.1.8" I actually had to downgrade my CWM to the 5.5.0.4 Version, you can download it from here:
androidroot . mobi / 2012 / 02/22/introducing-cwm-for-asus-transformer-prime/ --> WITH NO SPACE in between!
Here is how to Install the CWM file on your prime:
1. Get fastboot from that website, and extract it.
2. Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
3. Power off your prime.
4. Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot” -> USB ICON.
5. Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
6. Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
7. Reboot
-----------------------------------------------------------------------------------------
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "dklue" gave me the BLOB concept idea! heheheh i guess i learned something new now..
djedoortega said:
Hello there, for the last few nights I was having the same issue as you. I bricked my tablet, fixed it, and then just got stocked on the recovery with no data on my SDCARD. After searching and searching for hours online I found your post last night. And after reading the comments from Nilsonf, i googled some more information about something very important that me and you were missing!: "Blob files".
The "Primalicious_9.4.2.21._Final.zip" file or the "AOKP.zip" file will not work just like that because they are not in the format to be "Pushed" using the push command (At least thats what i kinda realized lol) anyhow, so i went online and searched for a ROM on Blob format and luckily i found the following!:
[ROM][WW][US][9.4.2.21] Primeval: The STOCK stock rom
So here is what worked for me thanks God! lol (Keep in mind that for some reason this process did not work for me on the new "CWM Touch Recovery 5.8.1.8" I actually had to downgrade my CWM to the 5.5.0.4 Version, you can download it from here:
androidroot . mobi / 2012 / 02/22/introducing-cwm-for-asus-transformer-prime/ --> WITH NO SPACE in between!
Here is how to Install the CWM file on your prime:
1. Get fastboot from that website, and extract it.
2. Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
3. Power off your prime.
4. Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot” -> USB ICON.
5. Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
6. Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
7. Reboot
-----------------------------------------------------------------------------------------
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "Nilsonf" gave me the BLOB concept idea! heheheh i guess i learned something new now..
Click to expand...
Click to collapse
Thanks man. I'll have to try that sometime later on today. I will report back with the end results
Sent from my Galaxy Nexus using xda premium
I'm stuck on number 3 of part 2. It's been doing nothing for about 20 minutes now. Should I keep waiting?
Related
I bought my own nook color on saturday, there doesn't appear to be a factory image that can be restored. My new nook color came with version 1.01 preinstalled. Before turning it on the first time I put in nookie froyo and did a dd of all 8 of the stock partitions. Below is the zipped up .img files of mmcblk0p1/mmcblk0p5 (boot/system) from a stock untouched 1.01 nook color. I am also including the factory.zip. This should be enough to restore a bricked nook color with a corrupted boot or system partition. Many people have been able to restore to stock by just using the boot.img because after 8 failed boots it will do a factory reset.
To make this work you must have ADB working first. You may be able to get this to work on ADB Wireless, but I don't recommend it. For instructions on getting adb to work with the nook color go here:
http://nookdevs.com/NookColor_USB_ADB
To use these files unzip them to the sdcard portion of a nookie froyo sdcard, or just about any other rom that runs from the sdcard and run the following commands in an adb shell:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Boot
System
factory.zip
Thanks, you're a life saver!
samuelhalff said:
Thanks, you're a life saver!
Click to expand...
Click to collapse
Did it fix you samuelhalff?
Yes. But I only used boot.img. Then restored to stock with 8 failed boots. Dd'ing system will also work.
If it dosen't boot, do a factory reset with power+n.
Sent from my HTC Desire using XDA App
So if I put the factory.zip on /dev/mmcblk0p3 and replace the current one, when we do the 8 bad boot trigger we would get 1.0.1 flashed instead of 1.0.0 right?
Yes. And I would also do a power+n reset at the end, to avoid any problems.
Sent from my HTC Desire using XDA App
shad0wf0x,
I am having the same problem with my NC not booting after a failed attempt at
re-rooting. I will tell you in advance that I am VERY tech-phobic and don't comprehend all this command-line stuff well at all.
Given your original post above, could you please explain in layman's terms EXACTLY what steps to take to restore my NC to like-new? And hopefully it can be done with just simply putting some files on a micro SD and that's it. Please let me know from start to finish how I do this. Appreciate your help in advance.
vigeh4
P.S. I know I had no business doing this, but I screwed my unit up anyway. I already tried the 8-step interrupt thing before re-rooting but with no success.
vigeh4,
First download the first 2 files, system and boot, and then unzip them. Then you need to copy those 2 files (system.img and boot.img) to the sdcard, either while booted up in nookie froyo or by putting the sdcard in your computer. Then you must have adb working on your computer. open a command prompt or terminal(windows or mac/linux) and go to the location where your working adb is and copy and paste those commands into the window to run them.
Code:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
shad0wf0x said:
vigeh4,
First download the first 2 files, system and boot, and then unzip them. Then you need to copy those 2 files (system.img and boot.img) to the sdcard, either while booted up in nookie froyo or by putting the sdcard in your computer. Then you must have adb working on your computer. open a command prompt or terminal(windows or mac/linux) and go to the location where your working adb is and copy and paste those commands into the window to run them.
Code:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
Sorry, I am WAY confused about how to do this. This adb crap is over my head.
Maybe I just have a $250 paperweight at this point. If I mail you my NC, would you reset to "factory" for a small fee?
Thanks.
OMFG, thank you very much for these files and instructions.
I really thought I bricked it to the point of no return. I initially screwed it up when I installed Clockwork and wouldn't boot past "N", then after tinkering around some more, it wouldn't even turn on ... lol.
@vigeh
First you need to unzip those files you just downloaded. Second, you need to copy the "boot.img" and "system.img" (not the *.zip) to the "/SDCARD" folder on your SDCARD. I had to use WIFI FILE Explorer in Nookie Froyo cuz I messed up my nook so bad, i couldn't copy these files by turning on the USB Storage through the regular method. It took me days to figure this out cuz i'm kinda slow.
I hope you installed the Android-SDK on your computer already. If so, then go to the folder named "\platform-tools" on your PC - this is where ADB.EXE is located. Connect your nook and type "ADB DEVICES" just to make sure your nook is connected to the computer. It'll show up and tell you it is or not. If it is connected then do the following:
1. Type "ADB SHELL" then you'll see a "#" symbol after you hit enter.
2. Type "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1" just the way it is written by the original poster (minus the "" marks)
at this point, it usually wont say anything. Just wait a few minutes and something will pop up. In my case, it says:
"477033984 bytes <454.9MB> copied, 138.757660 seconds, 3.3MB/s"
"#"
3. Type the second command next to the "#" sign "dd if=/sdcard/system.img of=/dev/block/mmcblk0p5"
wait another few minutes til the next confirmation pops up.
4. turn off nook, remove SD card
5. Hold the N button and the Power button at the same time and it'll ask you to reset the nook to factory settings.
I hope this helps you ....
well im a tard... i did this without reading that YOU CANNOT HAVE GOOGLE APPS!!!! so anyway Im trying to get back to a stock image, but i cant figure out how to copy 700 med +/- of images to 134 meg f free space. someone un-tard me plz . thanks
I have ClockworkMod Recovery installed, and if I put the factory.zip you provided on my sd card and use the option 'install zip from sdcard' will that in fact install factory settings on the nook?
I tried to do the 8 failed boots, but cannot get it to work with this installed.
shad0wf0x said:
vigeh4,
First download the first 2 files, system and boot, and then unzip them. Then you need to copy those 2 files (system.img and boot.img) to the sdcard, either while booted up in nookie froyo or by putting the sdcard in your computer. Then you must have adb working on your computer. open a command prompt or terminal(windows or mac/linux) and go to the location where your working adb is and copy and paste those commands into the window to run them.
Code:
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
How do you get to your "working adb?" I'm probably even more ignorant on this SDK stuff that vigeh4. I have SDK installed though.
How to get adb working is found here:
http://nookdevs.com/NookColor_USB_ADB
gconol said:
@vigeh
First you need to unzip those files you just downloaded. Second, you need to copy the "boot.img" and "system.img" (not the *.zip) to the "/SDCARD" folder on your SDCARD. I had to use WIFI FILE Explorer in Nookie Froyo cuz I messed up my nook so bad, i couldn't copy these files by turning on the USB Storage through the regular method. It took me days to figure this out cuz i'm kinda slow.
I hope you installed the Android-SDK on your computer already. If so, then go to the folder named "\platform-tools" on your PC - this is where ADB.EXE is located. Connect your nook and type "ADB DEVICES" just to make sure your nook is connected to the computer. It'll show up and tell you it is or not. If it is connected then do the following:
1. Type "ADB SHELL" then you'll see a "#" symbol after you hit enter.
2. Type "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1" just the way it is written by the original poster (minus the "" marks)
at this point, it usually wont say anything. Just wait a few minutes and something will pop up. In my case, it says:
"477033984 bytes <454.9MB> copied, 138.757660 seconds, 3.3MB/s"
"#"
3. Type the second command next to the "#" sign "dd if=/sdcard/system.img of=/dev/block/mmcblk0p5"
wait another few minutes til the next confirmation pops up.
4. turn off nook, remove SD card
5. Hold the N button and the Power button at the same time and it'll ask you to reset the nook to factory settings.
I hope this helps you ....
Click to expand...
Click to collapse
Thanks to Shadowf0x for getting ABD to work
I have a question though, if I dont have the file "SDCARD" in my SD card then can I just make a new file and name it SDCARD, and put both of the .img's into it?
Sir a teema said:
I have ClockworkMod Recovery installed, and if I put the factory.zip you provided on my sd card and use the option 'install zip from sdcard' will that in fact install factory settings on the nook?
I tried to do the 8 failed boots, but cannot get it to work with this installed.
Click to expand...
Click to collapse
I'm not sure if that will work, I guess it's worth a try, however if you replace the existing factory.zip and do a factory reset you will restore back to 1.01 instead of 1.0 if you don't already have a nc that has 1.01 on it. I saw another thread about trying to use the factory.zip with cwm, but I didn't see anyone coming back and say it worked. How to flash back to stock is found here:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
mmaner said:
well im a tard... i did this without reading that YOU CANNOT HAVE GOOGLE APPS!!!! so anyway Im trying to get back to a stock image, but i cant figure out how to copy 700 med +/- of images to 134 meg f free space. someone un-tard me plz . thanks
Click to expand...
Click to collapse
The nookie froyo sdcard partition for me was 900+m, and I've heard that all you need to do for this to work is to flash the boot.img.
Ign3nt said:
Thanks to Shadowf0x for getting ABD to work
I have a question though, if I dont have the file "SDCARD" in my SD card then can I just make a new file and name it SDCARD, and put both of the .img's into it?
Click to expand...
Click to collapse
You could try to mount the media partition in nookie froyo and put them there.
The partition is /dev/block/mmcblk0p8 and type is vfat.
shad0wf0x said:
The nookie froyo sdcard partition for me was 900+m, and I've heard that all you need to do for this to work is to flash the boot.img.
Click to expand...
Click to collapse
Ill try it tonight. thanks
Facts:
Laptop connected to my phone uses Ubuntu linux
Unlocked my Amaze successfully
I have the RecoveryInstallerForNoobs2.0
I have chmod'ed all the pertient files to be executable
With phone in fastboot mode, doing 'sudo ./fastboot devices' returns the serial number
Problem:
'sudo ./Flash.sh' returns the following output:
./Flash.sh: 1: adb: not found
: not found 2:
Additional facts:
I am a n00b and I am aware my life's output at age 32 is dismal
I have read the "read first for linux..." thread, "how to root" thread and the "faq before posting" thread
I have searched the site but possibly not hard enough, ergo my own impudent thread
What to do??
Is debug on in your phones settings?
Sent by accident from my Amaze using Tapatalk
Double0EK said:
Is debug on in your phones settings?
Sent by accident from my Amaze using Tapatalk
Click to expand...
Click to collapse
what he said turn on debugging on your phone. also make sure the zip file is unzipped into a folder
Debugging is on in the settings and the recovery for noobs zip is unzipped.
I flashed mine manually using the fastboot command...
But I only know how to do it with a windows machine.
Put the recovery.img in your AndroidSDK/tools folder , open cmd , cd to the tools folder and type "fastboot flash recovery recovery.img" being if you renamed it to recovery.img..(if it wasn't renamed then you need to type the name of the recovery img.)
Sent by accident from my Amaze using Tapatalk
ryurage said:
Debugging is on in the settings and the recovery for noobs zip is unzipped.
Click to expand...
Click to collapse
don't go to fastboot, the script should automatically kill and restart the adb shell...just turn on your phone and run flash.sh... if that doesn't work Rename the shellscript from flash.sh to flash.command, then associate it with Terminal.app
let me know if those work, if not, I've got some other tricks but it's a little bit more complicated.
@seansk, I renamed the file and tried it with the same resulted output:
./flash.command: 1: adb: not found
: not foundmand: 2:
Btw, I run the flash script one of two ways, 1. sudo ./flash.command or 2. bash flash.command
I could be wrong but I think the issue possibly lies in the script:
adb kill-serveradb reboot bootloaderfastboot flash recovery recovery-cwm-ruby-5.0.2.7.imgfastboot rebootexit
Perhaps adb has to be in my PATH? I'm open to other suggestions too.
One more thought, assuming the adb daemon is shut down, maybe this command would do it: 'sudo ./fastboot flash recovery recovery-cwm-ruby-5.0.2.7.img'?
hmm that thing has been up for months...I've only had two people having trouble and havn't heard back from the other guy...so I hope there's nothing wrong with the scrip...I will look into it again...unfortuantely my vitual machine for mac is down right now, don't know when I'll get it back up and running...
try these
1)To start the shell-script 'file.sh':
sh file.sh
bash file.sh
2)Another option is set executable permission using chmod command:
chmod +x file.sh
Now run .sh file as follows:
./file.sh
ultimately if you have a windows computer it would be much easier...or if you can also here's the new recovery from xboarder I havn't updated this zip file yet... you can edit the recovery script to change the name to this file name: recovery-cwm-ruby-5.5.0.4.img
if all else fails follow the second method here from xboarder (you need an sd card): http://forum.xda-developers.com/showthread.php?t=1316855
Download file to your computer
2. make sure its named PH85IMG.zip
3. Copy to sdcard (external one) then restart your phone in fastboot, by holding down the volume down and power.
4. Wait for it to say do you want to update (press volume up)
5. Press power button to reboot
6. Reboot Phone into recovery as normal and enjoy clockworkmod recovery with fixed charging and sdcard
I downloaded it from here ww w.clockworkmod.co m/rommanager/
I got the 5.8.4.3 image for my att note
(sorry I need to post more)
I have put it on my internal sd card and renamed it to recovery then I used my terminal emulator to use the command
su
flash_image recovery /sdcard/recovery.img
then it says it cant find it.
What am I missing?
rogsoccerman said:
I downloaded it from here ww w.clockworkmod.co m/rommanager/
I got the 5.8.4.3 image for my att note
(sorry I need to post more)
I have put it on my internal sd card and renamed it to recovery then I used my terminal emulator to use the command
su
flash_image recovery /sdcard/recovery.img
then it says it cant find it.
What am I missing?
Click to expand...
Click to collapse
Use odin.... thats what i done worked perfect!
Sent from my SAMSUNG-SGH-I717 using xda premium
How do I Odin a recovery image? I thought you need a tar file.
rogsoccerman said:
How do I Odin a recovery image? I thought you need a tar file.
Click to expand...
Click to collapse
Scroll on down this thread and u will find the tar file for odin and it will fix ur problems
Sent from my SAMSUNG-SGH-I717 using xda premium
rogsoccerman said:
How do I Odin a recovery image? I thought you need a tar file.
Click to expand...
Click to collapse
Its a little bit farther down someone already made the same thread ur file is there hope it helps let me know
Sent from my SAMSUNG-SGH-I717 using xda premium
Link please I can't find what you are talking about, all I can find is the old version by braway.
Thank you
rogsoccerman said:
I downloaded it from here ww w.clockworkmod.co m/rommanager/
I got the 5.8.4.3 image for my att note
(sorry I need to post more)
I have put it on my internal sd card and renamed it to recovery then I used my terminal emulator to use the command
su
flash_image recovery /sdcard/recovery.img
then it says it cant find it.
What am I missing?
Click to expand...
Click to collapse
I get the same problem as root in terminal:
flash_image recovery /mnt/sdcard/recovery.img
error scanning partitions: no such file or directory
- ROM Manager won't work; the "flash touch recovery" says "not supported" on this phone. The recovery download also doesn't work; the Galaxy Note is not listed, despite it being on the clockworkmod website!
- ODIN won't work as it needs a tar file or md5, or similar.
- There is no tar file in this thread or anywhere else I can find. If anyone knows exactly where this can be found, that would be helpful!
Basically, if I could find an easy way to "tar" up the recovery.img, it might work with ODIN. This might work, as past tars had only the one file within, but I need a UNIX OS to use the tar command. Drat!
UPDATE: I tarred it in the terminal and will now try ODIN. I hope it works....
UPDATE #2 - yep, it works!
How to install
Odin (this will increase the flash counter)
- put your phone into download mode
- in odin choose pda, and select the .tar.md5 file and flash
http://forum.xda-developers.com/showthread.php?t=1584576
[Recovery] ClockworkMod Based Touch Recovery - 04/14/12
works without any issue.....
Here's how I installed/upgraded CWM to 5.8.4.3 this is an A in Q&A
I was on the April version of CWM and was fat and happy, then I thought I'd try ICS, and didn't much care for what I was finding, then I read about another one I thought I'd try, but it (apparently) required a newer version of CWM, 5.8.4.3 i think.
So ROM Manager from the play store wouldn't do the upgrade for me, kept giving errors.
I'd used odin to install the april .tar, but this new version comes in an .img file.
I downloaded the .img file and placed it on my phone in sdcard (/mnt/sdcard)
searched high and low for a few hours, found a semi-cogent post about how to install it using adb from your PC, i guess.
adb is in the SDK which you can get from here:
http://developer.android.com/sdk/index.html
I installed this and I located adb here: C:\androidsdk\android-sdk-windows\platform-tools
on my PC from the command line (start, run, cmd, ENTER) I changed directories to that directory.
I executed, still on the command line: adb shell
:
This presented me the the octothorpe (hashtag if you must) prompt:#
at the # prompt I entered WITHOUT the double quote, ditto marks (")
"dd if=/sdcard/recovery-clockwork-touch-5.8.4.3-quincyatt.img of=/dev/block/mmcblk0p22"
so it looked like this:
#dd if=/sdcard/recovery-clockwork-touch-5.8.4.3-quincyatt.img of=/dev/block/mmcblk0p22
I pressed enter and it ran pretty quickly and returned to the (apparent) adb prompt # then I typed exit and it dumped me to the C: prompt and I exited that too (so there!), Then I rebooted the phone into recovery mode using one of many nifty reboot apps in the play store, so I don't have to have my fingers holding this slick and slippery buttons.
I verified I was in the new version of CWM, and rebooted to make sure my phone was still breathing... it was so I bailed back into recovery and am now running a backup... then I'll try to install the new ICS ROM, although it looks way too small to me.
I've gathered that the # prompt is the root prompt in adb, so either I'm very lucky and it does this by default, or adb detected my rooted phone... if you've read this far your guess is as good as mine.
I hope this helped someone from having to google for hours and hours into the night, and then not oversleep, not be late to work, not get fired, not go on unemployment, etc.
or not.
if you are running an unsecured kernel, adb should start with root rights of I'm not mistaken...also when you were done moving the recovery file instead of exiting the adb session and the c prompt altogether
You could have simply used the command:
Adb reboot recovery
And in fact..That's all those apps do.
Also of you copy the files in your android sdk platform-tools folder:
Aapt.exe
Adb.exe
Adbwinapi.dll
Adbwinusbapi.dll
Into your main Windows folder, you no longer have to cd to the platform-tools folder, you can use adb as a global command.
bigjoe2675 said:
How to install
Odin (this will increase the flash counter)
- put your phone into download mode
- in odin choose pda, and select the .tar.md5 file and flash
http://forum.xda-developers.com/showthread.php?t=1584576
[Recovery] ClockworkMod Based Touch Recovery - 04/14/12
works without any issue.....
Click to expand...
Click to collapse
That's an older version of cwm touch which is not compatible with some newer rooms.
VoluntaryMan said:
That's an older version of cwm touch which is not compatible with some newer rooms.
Click to expand...
Click to collapse
Really...cus i have been using it since i got the note and have flashed just about every ROM, lol works great for me sir, maybe my phone likes me idk, and yes just about every ROM....k
But hey i could be wrong..., so which ever works...use it, thanks
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I had the same problems... Ended up flashing twrp 2.2.1. But this link will work for you.
http://forum.xda-developers.com/showthread.php?p=28932726
Sent from my SAMSUNG-SGH-I717 using xda premium
CWM Touch [Solved, again]
I got it working very easily...
Heres how.
Got my .img file from http://www.clockworkmod.com/rommanager. Scroll to find Samsung Galaxy Note(ATT)
Changed the name of the file from "recovery.whatever.whatever.quincyatt.img" to "recovery.img"(minus quotes) using es file explorer(root needed)
Moved the file to root of /sdcard = /sdcard/recovery.img
Opened terminal emulator
typed
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
quit
then backed out to home screen and rebooted into my newest CWM Touch recovery.
Hope this helps anyone who needs it
EDIT: Just performed backup and succeeded. saved backup to /sdcard/clockworkmod/backup/
Moving prior braway recovery backups there to see if they are manageable within ROMmanager
This worked for me, thanks!
tyler79durdan said:
I got it working very easily...
Click to expand...
Click to collapse
I know this is old but better late than never...
ClockworkMod Touch Recovery 5.8.4.3 for SGH-I717 .tar file
http://forum.xda-developers.com/showthread.php?p=39037837
your welcome, enjoy
tyler79durdan said:
typed
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
quit
Click to expand...
Click to collapse
I did this, but instead of quit, I wrote "reboot recovery". I'm not sure if that did it, or if it was something else I did wrong, but the phone won't come back up. I checksummed the img I downloaded with another copy of "recovery-clockwork-touch-6.0.4.3-quincyatt.img" that I downloaded, and they matched:
e70ee18c0d63ee18d325c94e2af7a683
Shrug.
Edit: I just flashed it through odin and it worked. To build the tar.md5 I did the following in cygwin:
Code:
mv recovery-clockwork-touch-6.0.4.3-quincyatt.img recovery.img
tar -H gnu -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
Hello i have a transformer prime and i did some work on it and at this moment, it has not any files in it but i can access cwm recovery and fastboot mode. Plz help me. I think that somehow i need to put rom inside so i can flash it with cwm but how.
Put rom on sd card?
Sent from my Galaxy Nexus using XDA Premium HD app
Although you may get flamed from posting in Dev instead of QA,iIf you have fastboot access from your PC, then you can run the following command:
fastboot -i 0x0b05 flash staging YourChoiceOfRom.blob
Afterwards, reboot your TFP and your new rom should install.
If not, you can also try using ADB to push the file from your PC to the tablet's internal storage, then install through CWM.
kokopuphz said:
Although you may get flamed from posting in Dev instead of QA,iIf you have fastboot access from your PC, then you can run the following command:
fastboot -i 0x0b05 flash staging YourChoiceOfRom.blob
Afterwards, reboot your TFP and your new rom should install.
If not, you can also try using ADB to push the file from your PC to the tablet's internal storage, then install through CWM.
Click to expand...
Click to collapse
ADB push a rom onto /sdcard from your pc through Recovery
SFG said:
ADB push a rom onto /sdcard from your pc through Recovery
Click to expand...
Click to collapse
Download nvflash from the dev thread, extract it to C: it has adb in it. Download universal naked driver from dev thread, install the drivers as per the opening page (the prime is connected to the pc by cable at this point and booted into cwm). Download a rom, put it in the nvflash folder where the adb.exe is. Open the folder so you can see adb.exe, press and hold the shift key, right click the mouse, from the menu select open command window here. In the window, type adb push (enter name of the rom) don't forget the .zip at the end, press enter. This will take about 5 minutes to transfer. Reboot to cwm, install the zip (rom). You should be good to go.