I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Any help would be great to how I can undo this and install CWM.
Used the link for CWM from step 1 from this LINK
Thanks very much.
Tap UI Version : 1.2-5699
Kernal - 2.6.32.9-svn4979
Build - FRF91
Here is a link to a .zip I built for you. You will need to have root access for this.
fix-recovery.zip
Download this to your Gtablet and unzip it to /sdcard. Iif you can't make that work, download to your PC and unzip, then transfer the files over to /sdcard. Using a root file manager (I like ES File Explorer), move the file 'flash_image' into /system/bin, overwrite or rename the existing version if there is one, and change the permissions to make it executable (match the other executable files in the /system/bin folder). Then move the file 'cwm5502.img' into /system/etc/recovery (you might have to create the 'recovery' folder). Next, go back to /sdcard and change permissions on 'fixrecovery.sh' to make it executable as well.
Now open Terminal Emulator (install from the Play store or by other means if you don't already have it) and enter the following commands:
Code:
su
sh /mnt/sdcard/fixrecovery.sh
If the second command won't run, bypass the script by running this instead:
Code:
su
/system/bin/flash_image recovery /system/etc/recovery/cwm5502.img
That will install a version of CWM that is compatible with the 1.2 boot loader. Reboot and you should be able to enter the new recovery. Post back if you cannot get this to work for you, and we can try another way. This would be easier if you have ADB installed and working, but I assume most people do not.
Rochey21 said:
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Click to expand...
Click to collapse
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
DaggerDave said:
Here is a link to a .zip I built for you. You will need to have root access for this.
...
Click to expand...
Click to collapse
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
rajeevvp said:
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
Click to expand...
Click to collapse
Ok thanks, but I can not find the drivers for APX Mode, using Windows vista 32 bit?
Also just to make sure what Files would I need to use. Just want to make sure exactly what to do, and get it right.
Download the TeamDRH_350M_Prep.zip file from this post. It should have both the nVidia APX drivers and CWM-5.5.0.4 for a 1.2 bootloader (in part9.img).
Read the README file for the APX driver installation, but, don't run the NVFlash_gTablet.bat batch file. Instead, just write a new CWM using the commands in the link in my previous post.
EDIT: Note that you cannot install or upgrade the stock VS ROM using CWM. That can only be done using the stock recovery. For everything else, however, you can use CWM.
Feel like a total N00b :crying:
I have the drivers installed for AXB. I have downloads the zip folder with the img files and drivers etc. I renamed this folder to NVFlash for short.
Do I leave this folder on my laptop or put in on the tablet.
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Not sure how to do step 2
2. Run this command to determine the partition no. of the recovery (SOS) partition--usually, it is 9: Open a CMD.exe window, then change into the directory containing both the nvflash.exe and the bootloader.bin files. Then run:
You have been very helpful thanks again.
Rochey21 said:
Do I leave this folder on my laptop or put in on the tablet.
Click to expand...
Click to collapse
It's meant to be used on an x86 system (desktop, laptop, ...) running Windows or Linux. You can't run .dll and .exe files--Intel binaries--on an ARM tablet, right?
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Click to expand...
Click to collapse
Change to the directory containing the nvflash executable and bootloader.bin like this (only type in the stuff in bold):
Code:
[I]C:\SOME\PATH[/I]> [B]cd c:\NVFlash[/B] [I]Change to NVFlash directory[/I]
C:\NVFlash> [I] Note the changed prompt[/I] [I]now[/I]
After that, substitute C:\NVFlash\part9.img instead of C:\SOME\PATH\recovery.img in the given command line.
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
I have attached the command window. I typed cd c:\NVFlash and the directory changed to NVFlash.
Not sure how I substitute img 9 then?
EDIT* I got the p.txt file. How would I read this file?
Just looking to get CWM running so I can update to a new custom rom.
Rochey21 said:
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
Click to expand...
Click to collapse
No need to transfer anything.
EDIT* I got the p.txt file. How would I read this file?
Click to expand...
Click to collapse
Any editor will read that file. Just double-click on the filename.
Just looking to get CWM running so I can update to a new custom rom.
Click to expand...
Click to collapse
Which one?
rajeevvp said:
No need to transfer anything.
Any editor will read that file. Just double-click on the filename.
Which one?
Click to expand...
Click to collapse
JellyBean Smoother Seems to be good?
Sorry which editor would that be? I opened it in wordpad/notepad and it is all just symbols.
Would something like Hex editor read it?
Rochey21 said:
JellyBean Slim Seems to be good?
Click to expand...
Click to collapse
In that case, shut off the tablet; put it back into APX mode using Power and Vol [-]; then double-click the NVFlash_gTablet.bat batch file. It will do all the prep steps (including installing CWM) needed for a Jellybean ROM install. After the tablet boots into CWM, transfer the ROM install zip file onto the tablet and follow the instructions given in the ROM's first post to install the ROM.
Sorry which editor would that be? I hope it in wordpad/notepad and it is all just symbols.
Click to expand...
Click to collapse
Ah! You've got one of the screwey nvflash executables which produce a binary output. Ignore all this, then.
Ok So do I ignore everything or click the NVFlash_gTablet.bat file?
Rochey21 said:
click the NVFlash_gTablet.bat file?
Click to expand...
Click to collapse
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
rajeevvp said:
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
Click to expand...
Click to collapse
Finally :victory:
Thanks very much for all your help.
I have Smoother Bean installed, doesn't seem to be running correctly but il figure that out myself.
Thanks again.
Related
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
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
omni_angel7 said:
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
Click to expand...
Click to collapse
If your on linux it's "./moto-fastboot" not just fastboot.
Windows 7 64 bit. sorry, should have specified.
Nobody with win 7 knowledge/advice?
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Diviance said:
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Click to expand...
Click to collapse
Thanks SO much for the quick response and all the effort I'd actually updating OTA from 1.26 because I flashed back, thinking no one was gonna help! Well, when I feel up to it another night. I'll give this another shot. Thanks for the custom fastboot, too!
i get < waiting for device >
did i do something wrong?
Me too. ^^^^^^^
I figured it out, i forgot to put it into fastboot mode!
did not work for me
when I do what you told the other guy it says system cant find the path specified couls you please help I have spent a couple of days trying different things and also when I try to erase the recovery installer file it want let me
Ok, this is how to root the 2.2 OTA:
1. Download THIS file
2. Unzip "Root.zip" to your C:/SDK_Tools/Platform-Tools/ directory
3. Double click "Root.bat"
4. You should now have the # sign in Command Prompt
5. Download THIS File THIS file and THIS
7. Mount usb storage
8. copy ESPRIMG.zip and update.zip that you downloaded to the root of your sdcard
9. Unmount usb storage
10. Unzip "eng.zip" to yous platform-tools directory and click eng-prep.bat
11. Type:
cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img
exit
adb reboot bootloader
11. Press Power when you see the fastboot screen, then press volume up when prompted on the device
12. Reboot into recovery, click apply: update.zip from /sdcard
13. Flash the rom of your chioce!
Your welcome
Thank NBetcher for this method!
It's great that we can root the offcial OTA this way, which is my more quickly than the one that requires goldcard and bunches of other stuffs. However, I know it's a bit too much but is it possible that we can have the rooted official Froyo version that we can flash anytime? Sometimes, I need a stable ROM but flashing the official version and then root it takes too much time. Just show me the way and I will try to do it myself if you don't have time. Thanks in advance
bearshare said:
It's great that we can root the offcial OTA this way, which is my more quickly than the one that requires goldcard and bunches of other stuffs. However, I know it's a bit too much but is it possible that we can have the rooted official Froyo version that we can flash anytime? Sometimes, I need a stable ROM but flashing the official version and then root it takes too much time. Just show me the way and I will try to do it myself if you don't have time. Thanks in advance
Click to expand...
Click to collapse
Just install NB_Mod or CR_Mod, thats exactly what you are asking for
Whoareyou said:
Just install NB_Mod or CR_Mod, thats exactly what you are asking for
Click to expand...
Click to collapse
The OTA was released later and it's newer (update3 I think). I am just curious and want to play with is for a while. If there's no major difference among those, then I will use those Mod versions. Thanks.
bearshare said:
The OTA was released later and it's newer (update3 I think). I am just curious and want to play with is for a while. If there's no major difference among those, then I will use those Mod versions. Thanks.
Click to expand...
Click to collapse
Someone posted a rooted official OTA but the link no longer works. I managed to grab it while it was available and it works very well, I even flashed Dark Tremor's a2sd to gain way more memory. This is my daily ROM now. This was the post that contained the link: http://forum.xda-developers.com/showthread.php?t=1022518
Fuzi0719 said:
Someone posted a rooted official OTA but the link no longer works. I managed to grab it while it was available and it works very well, I even flashed Dark Tremor's a2sd to gain way more memory. This is my daily ROM now. This was the post that contained the link: http://forum.xda-developers.com/showthread.php?t=1022518
Click to expand...
Click to collapse
Thanks man, but the link is down. If no one cares about it anymore then I skip it.
11. Press Volume Up when prompted on the device... this is the step thats confusing me. I have done everything as said with no errors , root.bat and eng-prep but nowhere have i recieved a prompt to press volume up? and will the prompt be on my phone or on cmd?
Balem said:
11. Press Volume Up when prompted on the device... this is the step thats confusing me. I have done everything as said with no errors , root.bat and eng-prep but nowhere have i recieved a prompt to press volume up? and will the prompt be on my phone or on cmd?
Click to expand...
Click to collapse
I messed up the .bat file, ill look in to it, but the prompt will be on your phone....i will revise the thread
Ok so I have tried to move the appropriate file to the specified directory but it doesn't exist?
I dont have a "C:/SDK_Tools/Platform-Tools/" directory. And I just installed android sdk. Do I need a different one?
Am I missing something here?
EyeAndroid said:
Ok so I have tried to move the appropriate file to the specified directory but it doesn't exist?
I dont have a "C:/SDK_Tools/Platform-Tools/" directory. And I just installed android sdk. Do I need a different one?
Am I missing something here?
Click to expand...
Click to collapse
The files need to be unzipped to the Platform-Tools folder in the android sdk directory. Look in the folder that the android sdk is installed in and you will find the platform-tools forlder.
Has this actually worked for anyone? Not getting anything telling me to press volume up. also do you do all of these steps with the phone on and booted?
I'm working on fixing the .bat right now
Sent from my NookColor using XDA Premium App
Ok, try that
Does this flash a recovery?
Clock or amonRa?
Sent from my PG86100 using XDA Premium App
Bump?
Sent from my PG86100 using XDA Premium App
jshealton said:
The files need to be unzipped to the Platform-Tools folder in the android sdk directory. Look in the folder that the android sdk is installed in and you will find the platform-tools forlder.
Click to expand...
Click to collapse
Ok Ill try that. Also do I need to have 2.2 sdk installed?
mine keeps telling me SU not found /// help
alemanandrew said:
mine keeps telling me SU not found /// help
Click to expand...
Click to collapse
Just don't type sun if you already have the "#" prompt
Sent from my NookColor using XDA Premium App
this method does not work.
It does work, just 1 typo
This Method DOES Work!
there is just one little typo that stops it's functionality. You need a space between the [chmod 04755] and [*]. It should be:
chmod 04755 *
Thanks Whoareyou!
Whoareyou said:
Ok, this is how to root the 2.2 OTA:
1. Download THIS file
2. Unzip "Root.zip" to your C:/SDK_Tools/Platform-Tools/ directory
3. Double click "Root.bat"
4. You should now have the # sign in Command Prompt
5. Download THIS File THIS file and THIS
7. Mount usb storage
8. copy ESPRIMG.zip and update.zip that you downloaded to the root of your sdcard
9. Unmount usb storage
10. Unzip "eng.zip" to yous platform-tools directory and click eng-prep.bat
11. Type:
cd /data/local
chmod 04755*
/data/local/flash_image misc /data/local/mtd0.img
exit
adb reboot bootloader
11. Press Power when you see the fastboot screen, then press volume up when prompted on the device
12. Reboot into recovery, click apply: update.zip from /sdcard
13. Flash the rom of your chioce!
Your welcome
Thank NBetcher for this method!
Click to expand...
Click to collapse
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