My device:
Vpad7 w/ Android 2.2.1
Baseband version PR3.7_125
Kernel version Apps_2.6.32.9
Build number 1008_3_240
SWVer=3.240
Model: FM6-0001
HWVer=107
Desired ROM: EUViewpad7v1.7b-ITE
I tried to follow the [READ FIRST] Vpad7 Dev's thread.
1- Root was ok, su successful (SOC 1.7 and antivirus off);
2- Copied all partitions to sdcard was ok;
3- Error copying flash_image to /system/bin (read-only file system)
solved with:
mount -o remount,rw /dev/block/mtdblock4 /system
cp /sdcard/flash_image /system/bin
chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/cwrecovery.img
4- EUViewpad7v1.7b-ITE.zip copied into sdcard and renamed to update.zip;
5- Backup stock ROM on dev's recovery mode ok;
6- Select 'apply sdcard: update.zip' on dev's recovery mode, with success;
After reboot, the VP7 shows the 3 birds logo, and after that shows an endless animation, on which is a kind of telephone's cabin flying through a cloud tunnel. (no, i'dont use drugs!). The android's graphic interface isn't loaded.
I restored rom bkp from sdcard by dev's recovery mode with success.
Could I use the EUVpad7v1.7b without a previous EUVpad7v1.7 ?
What's going wrong?
It takes a while to load first time. For me it did. I also had a problem like that and had to mount system with latest CMW
What's your CWM's version?
Sent from my ViewPad7 using xda premium
My version is 5.0.2.6
indyend said:
What's your CWM's version?
Sent from my ViewPad7 using xda premium
Click to expand...
Click to collapse
almartin said:
My version is 5.0.2.6
Click to expand...
Click to collapse
Mine is 2.5.1.2
could this be causing that problem?
thks u
indyend said:
What's your CWM's version?
Sent from my ViewPad7 using xda premium
Click to expand...
Click to collapse
almartin said:
My version is 5.0.2.6
Click to expand...
Click to collapse
My CWM's version is 2.5.1.2
I'll try a newer one.
I tried w/ the CWM 5.0.2.6, but after "flash_image recovery /sdcard/cwrecovery i've got an error (No space left on device).
When i use the CWM 2.5.1.2 (from XDA dev's tutorial), flash_image recovery is completed with success.
Is there an intermediate version that solve this issue?
thanks!
Weird. Did you factory reset and wipe?
almartin said:
Weird. Did you factory reset and wipe?
Click to expand...
Click to collapse
That's it!
We get, but when i start the recovery mode on VP7, the CWM version shown is 2.5.1.2 yet! As a newbie i thought to install a new CWM only the "flash_image recovery /sdcard/cwrecovery.img" command was necessary to.
I didn't forget to copy new cwm (downloaded here: http://forum.xda-developers.com/showthread.php?t=1288223 - is it the rigth version?) to sdcard.
Do you have an idea to apply that change?
lucadiq said:
That's it!
We get, but when i start the recovery mode on VP7, the CWM version shown is 2.5.1.2 yet! As a newbie i thought to install a new CWM only the "flash_image recovery /sdcard/cwrecovery.img" command was necessary to.
I didn't forget to copy new cwm (downloaded here: http://forum.xda-developers.com/showthread.php?t=1288223 - is it the rigth version?) to sdcard.
Do you have an idea to apply that change?
Click to expand...
Click to collapse
Yeah!
I gave up to change CWM version. After searching here, i found a very good step by step for newbies (http://forum.xda-developers.com/showthread.php?t=1224825). My 2.5.1.2 CWM has worked fine!
The problem is that i was forgetting to create the ext partition to App2SD, probably.
Thread closed.
CWM Newer than 2.5 maybe cause of some error.
Sent from my ViewPad7 using xda premium
Related
CWM has been updated officialy to 3.2.0.1! See the Changelog and FAQ below for more information!
Changelog:
3.0.0.5 - Initial official release for the nook. Only supported ext3. Had bootloop errors with the 1.1.0 update. (Note: Unofficial builds supported ext4 but not both at the same time)
3.0.0.6 - No significant changes to 3.0.0.5 officially. (Note: Unofficial builds supported ext3 or ext4 but not both at the same time)
3.0.0.8 - Broken build. Blame the samsung phones for messed up additions.
3.0.0.9 - Adds official support for ext4 as well as compatability for ext3. (i.e. No need to swap recovery for different ROMs). Fixes "Always boots into recovery" with 1.1.0 updated u-boot.bin
3.0.1.0 - Adds support to for /sd-ext to recovery.
3.0.2.8 - Sets /system to ext2. You can now backup and restore your stock roms! Delete/Update all 3.0.0.5 threads to point to 3.0.2.8 for all rom types. Rom Manager now pushes a recovery kernel as well as the ramdisk!! No need to manually install recovery kernel. Just flash the lastest from RomManager and you are done!
3.2.0.0 - Support for newer nooks with the 5G /data parition! New .32 kernel is included which fixes the freezing after formatting /data! (/data format issues. Don't Use)
3.2.0.1 - Fixes a bug with 3.2.0.0 (actually a build issue) where ext3 (/data and /cache) wouldn't be formatted properly (they were but CWM was bombing out)
*Recommended *
RomManager can now push the recovery kernel. No need to manually install via CWM or ADB! Flash from RomManager and rock and roll.
Q: Why should I upgrade?
As of the official version 3.0.0.9 there CWM supports both ext3 and ext4 ROMs with a single recovery image. This means no more of this swapping back and forth between different versions of CWM! 3.0.2.8 sets /system to ext2 to allow for proper backing up and restoring of stock roms!
This version also fixes issues with the 1.1.0 version of u-boot.bin. Some with this version may experience that your NookColor will always boot back into RomManager. This is now fixed (as of 3.0.0.9)
Click to expand...
Click to collapse
Q: But I have CWM <insert older version> I am good right?
Always use the latest found on this post or on RomManager. Older version are not supported
Click to expand...
Click to collapse
Q: I used RomManager to install CWM but now i can't use backup or restore
This should be fixed. Report any issues to me either on this thread or via PM
Click to expand...
Click to collapse
Q: I upgraded CWM and now my market doesn't work.
Installing CWM doesn't alter any rom or data files which shouldn't have any affect on recovery. There is something else that may have affected your market.
No worries though you can try the following to try and fix it:
If you are using CM7. Upgrade to the latest nightly (which will be after tonight: 3/3)
Try clearing the following: For "My Apps," go to manage apps, market, uninstall updates, clear market cache. Then delete data for Google Framework Services.
Click to expand...
Click to collapse
Q: I have upgraded but now I am having issues?
So some of you are still having issues with this new CWM version. PLEASE PLEASE PLEASE give me the following information:
What you are trying to do/accomplish. Be as detailed as possible
What rom you are running and what rom you are upgrading to (if applicable)
IMPORTANT! Grab a recovery.log from your nookcolor. You can do this either through adb or through the advanced menu. If I don't have this then there is little I can help with.
Click to expand...
Click to collapse
Q: How do i grab the recovery.log?
Method 1: ADB
After setting up adb type:
Code:
adb pull /tmp/recovery.log
You are done. (This is why everyone should learn and setup ADB. It really is stupid simple)
Method 2: Save from the menu
From the ClockworkMod Recovery main screen do the following
Select 'Advanced'
Select 'Report Error'
There is now a copy of recovery.log on your sdcard. Transfer the sdcard to a computer or boot into your rom and mount your sdcard on your computer.
Click to expand...
Click to collapse
Thank you Nemith
i flashed this earlier today, at first it kept bootlooping so i used the remove CW zip and got rid of it. The 2nd install went fine (both times i rebooted before booting into CW)
however CW says it cannot mount system so i'm unable to make a full backup
davidukfl said:
i flashed this earlier today, at first it kept bootlooping so i used the remove CW zip and got rid of it. The 2nd install went fine (both times i rebooted before booting into CW)
however CW says it cannot mount system so i'm unable to make a full backup
Click to expand...
Click to collapse
What rom are you running?
Nice! Thanks!
Sent from my DROIDX using Tapatalk
nemith said:
TL;DR: If you use RomManager go upgrade it in RomManager NOW!
Click to expand...
Click to collapse
My RomManager still sees 3.0.0.5 as the latest version.
Chahk said:
My RomManager still sees 3.0.0.5 as the latest version.
Click to expand...
Click to collapse
I provided a link/instructions to manual flash cwm. This may help.
Stock 2.1 rom
Sent from my DROIDX using Tapatalk
davidukfl said:
Stock 2.1 rom
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Grab /tmp/recovery.log from your device after you try to do a nandroid backup.
Thanks!
Excellent! I 'll have a new installclockwork.zip and universal bootable sd out here as soon as I get back from skiing
Thanks!
Thanks for the info. I have been waiting for this.
So I'm stuck in the CM boot loop. Can I install from the boot-looping CM or do I flash it from the SD loaded CM?
No problem either way, just curious what the best approach is?
Moar gees with gginggerbread and tapatalk!
John Kotches said:
So I'm stuck in the CM boot loop. Can I install from the boot-looping CM or do I flash it from the SD loaded CM?
Click to expand...
Click to collapse
Either should work since both are ran from RAM.
Can the img file be written to an SDcard? Also, can Nandroids made with 3.0.0.5 be restored using the update?
Homer
nemith said:
Grab /tmp/recovery.log from your device after you try to do a nandroid backup.
Thanks!
Click to expand...
Click to collapse
the tmp folder is empty. In the clockwork folder on the SD card the boot.img file is in there though.
When i create a backup it says cannot mount system, and when i got to advanced and hit mount system it says the same thing
Homer_S_xda said:
Can the img file be written to an SDcard? Also, can Nandroids made with 3.0.0.5 be restored using the update?
Homer
Click to expand...
Click to collapse
Yes. There is nothing special about the images written to an sdcard. You can even rename the files to uImage and uRamdisk to have it boot without the two-finger salute on the sdcard.
davidukfl said:
the tmp folder is empty. In the clockwork folder on the SD card the boot.img file is in there though.
When i create a backup it says cannot mount system, and when i got to advanced and hit mount system it says the same thing
Click to expand...
Click to collapse
There should always be a /tmp/recovery.log. You need to grab this while in recovery via adb
Code:
adb pull /tmp/recovery.log
nemith said:
Either should work since both are ran from RAM.
Click to expand...
Click to collapse
I'll probably shove remove cw onto the bootable sd card and then push cw again from rom manager.
Moar gees with gginggerbread and tapatalk!
I can't mount /system either. Using CM7. I also have a dual-boot partition, but I doubt that matters.
from log:
mounting /system!
W:failed to mount /dev/block/mmcblk0p5 (No such device)
Error mounting /system!
Also:
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p7 (No such device)
edit: Here's the full pastebin
Updated rom manager with cm7 nightly 7. Worked flawlessly.
Okay, I've seen a few people and various threads with this problem:
1. They have a rooted Optimus V
2. they may or may not have flashed a recovery
3. they download ROM Manager and select ROM Manager's Clockwork Recovery
4. they flash a rom and reboot
5. they get stuck in a recovery loop and run around screaming.
This was me yesterday!!
What did I do, then? I downloaded the Fastbootroot tool. That got rid of the ROM Manager's CW Recovery and put in thunderc-v-1.1.0 version recovery... that looped. I tried the 1.2.0 version, which also looped, but I could flash a different recovery, finally. So I downloaded Xionia's Clockwork Recovery and THAT worked. (this next excerpt is from my androidcentral forum post)
here's exactly what I did starting from the thunderc-v-1.2.0 recovery (i'm gonna go into too much detail for other eeijits like me):
download xionia's clockwork recovery and the flash image, unzip both onto your sdcard
put your desired rom on your sdcard (zipped, omg)
get out of usb storage mode
Get ADK Tools if you don't have it (search the forum, this is the easy stuff)
Make sure you're all mounted in mounts and settings in your current recovery.
open cmd, and get into adb shell
(this next part is from zefie's post)
enter the following commands:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /sdcard/xionia_cwma_12518.6.img
# reboot recovery
it should reboot into xionia's clockwork recovery mod
clean dalvik cache and mount everything
choose 'fix recovery loop' under ... advanced IIRC, I can't check right now as I'm reloading my stuff onto the fixed phone
after the loop's fixed, get back into recovery and load whatever ROM you fancy.
WIN!
Recovery loop from ROM mgr backup restore...tried Kiona, tried mmarz, what next?
Newb here...BUT, in my defense...I DID NOT DO AN ANDROID SYSTEM RESTORE ON MY ROOTED PHONE!! which seems to be most people's problems with boot/recovery looping. My phone is stuck in a recovery loop after restoring a Clockworkmod backup.
History: I rooted my LG Optimus V running 2.2.2 with gingerbreak a couple of months ago. Per all instructions I could find, I installed SuperUser, Rom Manager, Titanium Backup, I also have another backup by Rerware, but I can't remember the name of it. I kept the stock ROM. Everything has been working fine.
I got a 32 gig micro card for Christmas. So, as per instructions found elsewhere, I made a backup to my sd card with ROM Manager, Titanium and Rerware. I copied my sd card to my hard drive, partitioned my new sd card, and loaded the new sd card with the old sd card data. At that point everything looked fine. But the instructions said to restore from my backup which I did with clockworkmod and now I am stuck in a recovery loop.
I completed Kionia CWMA install 1..4 and performed "Fix Recovery Boot Loop" but it did not fix the issue.
I completed Kionia CWMA install 1..6 and performed "Fix Recovery Boot Loop" but it did not fix the issue.
I completed the abd shell instructions "strings/dev/mtd/mtd8" and "flash_eraseall /dev/mtd/mtd8" per mmarz but it did not fix the issue.
I have recovery access. I have ADB running.
What should I do next? Everyone else seems to be fixed with mmarz's suggestion...
Thanks to whoever is out there for any help...
rom manager is mostly no good on V and the new V screen {after sept.} gets ruined alot by rom manager, so i wouldn't use it
get a compatible recovery at the iho wiki and install
then flash the rom of your choice
if that doesn't work there is lots of help for this in the optimus v "development" section
Thanks for your reply. I just wasn't sure what I should do next and your suggestion worked perfectly. And I guess I had to get over the fact that I was going to have to restore from scratch and get over my fear of installing a custom ROM. Luckily, of all the backups I had, Titanium worked BEAUTIFULLY! I was chicken to flash a custom ROM, but I flashed IHO Harmonia and it is beautiful and has been working flawlessly ever since. I shouldn't say flawlessly, I kept getting some gapps error but I was able to look it up easily and fix it.
Live and Learn.
the latest version of rom manager in market has bug... so we can use older version search on google. And it works again
Sent from my LG-P500 using xda premium
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
hi friends
excuse me for my bad english!
i have rooted my 2.3.3 stock rom and installed xrecovery by copying Xrecovery files from root explorer to System>bin
i have recovery menu i can backup my rom but when i want install another programme from recovery:
E:Can't mount /dev/block/mmcblk0p1 Cant mount Sdcard
help me please
davut1362 said:
hi friends
excuse me for my bad english!
i have rooted my 2.3.3 stock rom and installed xrecovery by copying Xrecovery files from root explorer to System>bin
i have recovery menu i can backup my rom but when i want install another programme from recovery:
E:Can't mount /dev/block/mmcblk0p1 Cant mount Sdcard
help me please
Click to expand...
Click to collapse
- boot your phone into xrecovery
- @xrecovery connect with adb shell
- enter this script
rm -r /sdcard
mkdir sdcard
chmod 777 sdcard
-go install what you want to installed
it worked for me, but what I did wrong to get to this?
thanks for the tip
saint23liquori said:
- boot your phone into xrecovery
- @xrecovery connect with adb shell
- enter this script
rm -r /sdcard
mkdir sdcard
chmod 777 sdcard
-go install what you want to installed
Click to expand...
Click to collapse
have a simmilar problem but it says device or resourse busy tried the above script it says rm is not recognized as an internal or external command same for chmod any help would be great
I had the same problem and i fixed it by updating the Xrecovery to v0.3 .
Found here ;
http://forum.xda-developers.com/showthread.php?t=859571
Put the xRecovery v0.3 zip on your sdcard and rename it to update.zip
Then install the update.zip in your current xRecovery. Somehow my old xRecovery could read the update.zip and it worked.
I had tha same problem. My was resolved with a stock firmware downgrade. I've flashed my X10 with stock 2.1 ROM and after that i did rooting, kernel upgrade, xrecovery instalation..step by step. Everything is working fine for me rightnow.
Who can not succed with other methods, can try mine.
Sorry for my bad english
Chears
Elaba said:
I had the same problem and i fixed it by updating the Xrecovery to v0.3 .
Found here ;
http://forum.xda-developers.com/showthread.php?t=859571
Put the xRecovery v0.3 zip on your sdcard and rename it to update.zip
Then install the update.zip in your current xRecovery. Somehow my old xRecovery could read the update.zip and it worked.
Click to expand...
Click to collapse
Tks you
Elaba said:
I had the same problem and i fixed it by updating the Xrecovery to v0.3 .
Found here ;
http://forum.xda-developers.com/showthread.php?t=859571
Put the xRecovery v0.3 zip on your sdcard and rename it to update.zip
Then install the update.zip in your current xRecovery. Somehow my old xRecovery could read the update.zip and it worked.
Click to expand...
Click to collapse
And yes this is my fix.
I first install xRecovery v0. 3 then i boot in recovery menu and i install xrecovery .zip from link above with that script, then i could install feralab v.03 rom.
Sent from my GT-P5110 using xda app-developers app
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