Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
Related
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?
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
I am rooted but i have been reading on installing a recovery. I don't have a sd card at the moment so not sure if i can use ADB to install a recovery. Why cant i just install recovery through Rom Manager?
eastwood1 said:
I am rooted but i have been reading on installing a recovery. I don't have a sd card at the moment so not sure if i can use ADB to install a recovery. Why cant i just install recovery through Rom Manager?
Click to expand...
Click to collapse
Someone with more knowledge will need to chime in, but I I'd bet the build we are using isn't official, and probably can't be installed through Rom Manager. Give it some time, eventually things will work as normal
And you can use the internal storage to copy over the recovery. I used terminal emulator and the internal memory when I did mine.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
And you can use the internal storage to copy over the recovery. I used terminal emulator and the internal memory when I did mine.
Click to expand...
Click to collapse
Can you explain to me how you went about installing the recovery with only internal storage? I would like to give that a try but not sure the best way to go about it. What commands to use and such, thanks.
eastwood1 said:
Can you explain to me how you went about installing the recovery with only internal storage? I would like to give that a try but not sure the best way to go about it. What commands to use and such, thanks.
Click to expand...
Click to collapse
To all,
I couldn't be bothered with learning ADB, but wanted a custom recovery on my SIII ... maybe you can relate?
Here's the easiest way to do it -- and you don't even need a computer!!! You do, however, already need to be rooted before you can use this method ...
Download your recovery of choice (.. as of this writing, I think there are two: CWM and TWRP ..) and make sure you place a copy in the root drive of your sdcard. Rename it recovery.img, if you want to follow the terminal directions listed below ...
Then, download a terminal emulator onto your device (I use Better Terminal Emulator Pro, which is a paid app) and fire it up.
Once in the terminal emulator, type the following commands one line at a time, waiting after each line for the appropriate prompt:
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
# reboot recovery
Your device should then boot into the custom recovery, which serves as immediate confirmation that you did things correctly.
I just used this method to install birdman's twrp8.img to my SIII and it worked like a charm.
http://forum.xda-developers.com/showthread.php?t=1764398
I dont think that will work. Notice the command says sdcard.
The internal memory on the sgsiii is labeled sdcard for whatever reason. The external sdcard slot is under mnt/extsdcard in root explorer if that helps.
Sent from my SGH-T999 using xda premium
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
eastwood1 said:
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
Click to expand...
Click to collapse
You need to be rooted and have a "su" command. Typical "rooted" roms include supersu , or equivalent, and busybox (which provides the basic Linux commands). I would install super super and busybox from Google play and try again.
You need the SU command to switch to root user in the shell to have the rights to use dd to overwrite the recovery partition.
I can confirm that the dd command works as that is how I loaded cwm on my s3.
Sent from my SGH-I747M using xda app-developers app
eastwood1 said:
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
Click to expand...
Click to collapse
See if this helps.
http://forum.xda-developers.com/showthread.php?t=1739426
For what its worth the reason ROM manager doesn't work is because there is not an official CWM Recovery out for the Verizon S3. We are using the Sprint Recovery
Pompsy said:
For what its worth the reason ROM manager doesn't work is because there is not an official CWM Recovery out for the Verizon S3. We are using the Sprint Recovery
Click to expand...
Click to collapse
There's no official CWM Recovery for any US versions of the GS3, Sprint included. The only official GS3 recovery available is for the international version. The one we're all using right now (I believe) was built by Team Epic. They're historically Sprint devs and so they built it for the Sprint version; however, as you know it works on more than just the Sprint version. Eventually, I'm sure there will be official recoveries direct from Koush.
Personally, I prefer TWRP (bettery touch control layout and options such as compression to save space), but that too is a work in progress.
I follow the steps on this post: http://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819
but when I put the commands in the terminal , it appears: "No such file or directory". How i can fix it? Thanks.
You probably mistyped something.
Vagelis1608 said:
You probably mistyped something.
Click to expand...
Click to collapse
I try copying it directly from the post and still shows the same error
Acritura said:
I follow the steps on this post: http://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819
but when I put the commands in the terminal , it appears: "No such file or directory". How i can fix it? Thanks.
Click to expand...
Click to collapse
Copy it to internal storage and make sure, that you write commands correctly.
Don't forget the unpack and don't forget the "su" before you try the "dd".
Zaaap72 said:
Don't forget the unpack and don't forget the "su" before you try the "dd".
Click to expand...
Click to collapse
Yes, I'm sure I have not forgotten . It's safe to try putting the file on internal storage and see if it works well ? It would be the same command ?
Acritura said:
Yes, I'm sure I have not forgotten . It's safe to try putting the file on internal storage and see if it works well ? It would be the same command ?
Click to expand...
Click to collapse
You actually have to put it in internal storage with that command.
Cafi96 said:
You actually have to put it in internal storage with that command.
Click to expand...
Click to collapse
Installation:
1 - Unzip the file. E.g. using 7zip.
2 - Copy the extracted file to /sdcard on your phone.
3 - Start a shell using a terminal or ADB
4 - Get root rights: su
5 - Install the bootloader using dd
Says in the instructions must be copied to the SD , now I 'm confused.
----------------------------------------------------------------------------------
Ok , you were right and I was able to unlock the bootloader. But now I have another problem , I flash the CWM.img with flashify, and when reboot the phone i got a green screen "TZ Crash - DemiGod Crash Handler" how i can fix it? thanks.
Acritura said:
Installation:
1 - Unzip the file. E.g. using 7zip.
2 - Copy the extracted file to /sdcard on your phone.
3 - Start a shell using a terminal or ADB
4 - Get root rights: su
5 - Install the bootloader using dd
Says in the instructions must be copied to the SD , now I 'm confused.
----------------------------------------------------------------------------------
Ok , you were right and I was able to unlock the bootloader. But now I have another problem , I flash the CWM.img with flashify, and when reboot the phone i got a green screen "TZ Crash - DemiGod Crash Handler" how i can fix it? thanks.
Click to expand...
Click to collapse
Can you boot up the phone? If yes, flash TWRP instead.
Cafi96 said:
Can you boot up the phone? If yes, flash TWRP instead.
Click to expand...
Click to collapse
Yeah, by luck i can boot it. I will try flashing TWRP from: http://forum.xda-developers.com/g2-mini/development/recovery-lg-g2-mini-d618-v10c-t2854493 to see if it works.
------------------------------------------------------------------------------
It worked perfectly , millions of thanks! o/
prefered from here http://forum.xda-developers.com/g2-mini/development/recovery-twrp-2-8-7-0-t3147675 download 2.8.7.0 TWRP