Related
Sorry guys, I have searched through, tried all possible things... but cannot get things working... here's my story (long, but gives the whole picture)
1. Was on CM 6.0 (stable) and Amon RA 1.7 recovery
2. Got a new SD card (8gb class 6)
3. Had Nand backups, so just removed the old card and inserted the new
4. Booted into recovery, partitioned SD card, copied CM 6.1.0 RC and gapps onto the SDCard
5. Performed Wipe Data/Factory reset, Wipe cache, Wipe Dalvik-cache and flashed CM 6.1.0 rc and gapps
6. Booted into the ROM, signed into my account, got all my apps from market
7. Everything was running fine
8. Booted into recovery, made a Nand backup and installed Steel my Elegance
9. Booted into the ROM and realized something was not correct, so decided to restore from the Nand backup
10. Booted into recovery and tried to restore - failure, asked me to run nand backup from adb
11. Did that but that did not resolve the situation
12. Performed step #5 (above) again and got it to the original state
13. Did not login into my account, as I wanted to get a backup of a fresh install
14. Booted into recovery made a Nand backup successfully
15. Just to be on the safer side, tried restoring... did not work. Same error - run SH from adb - tried that, but did not work
16. Read somewhere on the forums to wipe cache before backup and try, did that backed up and tried restoring - no go
17. Decided to flash ClockWork recovery - did that through terminal (ROM booting properly)
18. Booted into recovery - successfull
19. Tried creating Nand backup - failed at Cache - cannot image cache error message or something
20. Performed format SD card, cache, system and all other formats available from the recovery (ClockWork mod)
21. Tried performing nand backup - created some folders/files under the clockwork mod folder with junk characters
22. Performed a SD card format from computer (FAT32)
23. Booted into recovery and tried nand backup - no go
24. Decided to revert back to Amon RA 1.7 - flashed through terminal and rebooted into recovery - phone won't go to recovery
25. Though there might be some problem with the img file, so downloaded from multiple locations and tried it - still no go
26. Followed all sorts of instructions - mount/remount, flash_image - no go. When I do flash_image recovery <image name>, the command exits without any errors, but still can't boot into recovery
27. Installed ROM manager and flashed clockworkmod recovery from within, still no go.
28. Performed "Fix permissions" - ended with "Could not run some privileged commands"
29. I can still boot into the ROM and when I go to terminal can do SU - takes me to "#" from "$" - so I am guessing I still have root
It just doesn't add up... and I feel very lost, right now. I guess the only thing remaining to do is go back to 2.1 RUU, reroot and go from there. Is there any other way? Or did I do something wrong?
Can someone please help?
Edit: I had enough battery juice or wall power plugged into the phone while trying the backups and restores...
Do you still have the super user app? Check the permissions in the app, maybe one couldve gotten declined???
go to impalers cyanogen mod q&a, ask there, impaler is really knowlegable and helpful, you should get some concrete help.
I don't think this has anything to do with CM, else would have posted there.
Thanks anyways.
cordell12 said:
Do you still have the super user app? Check the permissions in the app, maybe one couldve gotten declined???
Click to expand...
Click to collapse
Checked that, everything that needs access seems to have it.
Any other ideas? I am so close to going RUU route......
Maybe this can help? I dont know never had this happen?
http://forum.xda-developers.com/showthread.php?t=845069
Thanks everyone... I ended up going the RUU way. Got my recovery back, backup/restore and CM6.1.0 RC up & running. Loooonnnnggg night .
andythegreenguy said:
Thanks everyone... I ended up going the RUU way. Got my recovery back, backup/restore and CM6.1.0 RC up & running. Loooonnnnggg night .
Click to expand...
Click to collapse
I hate that you had to go that route, but atleast all is well now. It couldve been worse and not even let you RUU Thats a Scary thought!
cordell12 said:
I hate that you had to go that route, but atleast all is well now. It couldve been worse and not even let you RUU Thats a Scary thought!
Click to expand...
Click to collapse
No kidding... . It was so frustrating, just going through it all.
Originally, I had rooted my phone that had 2.31.651.7 on it. So, I applied that RUU and went through the root. It seemed to have rooted fine, but then it won't allow me to flash recovery - did the same steps as I had performed during my first rooting process, but didn't work. Then went through all possible ideas suggested on the forums... still no luck. So, finally put the 2.27.651.5 RUU, followed regaw_leinad's rooting method and everything worked out.
All-in-all a good learning experience .
BTW, for anyone that is reading, I think the issue was a corrupted SD card. I might have pulled it while the phone was running and then applied a corrupted recovery image.
Slight issue here, not sure if anyone has had it before.
Just acquired a Captivate as an xmas gift to myself (sick of that iPhone), and began the whole process of getting a new ROM onto it. Rooted, installed ROM Manager, flashed a clockworkmod recovery (2.5.1.2), and hit "Backup Current ROM".
The device reboots into the standard recovery mode with the usual options (reboot system now, reinstall packages, delete all user data, delete cache data).
No backup is made, and I just have to continue the reboot. I've tried flashing to an older version, clearing the download cache, and using the option to go to ROM Manager's recovery mode (just takes me to the default recovery boot).
Am I doing something wrong here? I followed all of the instructions step by step.
Velshtein said:
Slight issue here, not sure if anyone has had it before.
Just acquired a Captivate as an xmas gift to myself (sick of that iPhone), and began the whole process of getting a new ROM onto it. Rooted, installed ROM Manager, flashed a clockworkmod recovery (2.5.1.2), and hit "Backup Current ROM".
The device reboots into the standard recovery mode with the usual options (reboot system now, reinstall packages, delete all user data, delete cache data).
No backup is made, and I just have to continue the reboot. I've tried flashing to an older version, clearing the download cache, and using the option to go to ROM Manager's recovery mode (just takes me to the default recovery boot).
Am I doing something wrong here? I followed all of the instructions step by step.
Click to expand...
Click to collapse
Try doing "reinstall packages".
Steps:
1. Copy the clockwork recovery "update.zip" attached to this post to ur sdcard root.
2. Reboot to recovery.
3. Select "reinstall packages".
4. It would say something like replacing recovery with clockwork recovery, and reboot into recovery. This happens only the first time u use this.
5. Select "reinstall packages" again.
6. You should be in clockwork recovery.
diablo009 said:
Try doing "reinstall packages".
Steps:
1. Copy the clockwork recovery "update.zip" attached to this post to ur sdcard root.
2. Reboot to recovery.
3. Select "reinstall packages".
4. It would say something like replacing recovery with clockwork recovery, and reboot into recovery. This happens only the first time u use this.
5. Select "reinstall packages" again.
6. You should be in clockwork recovery.
Click to expand...
Click to collapse
Good deal. Worked perfectly. Out of curiosity, do we know why the phone was doing this?
Velshtein said:
Good deal. Worked perfectly. Out of curiosity, do we know why the phone was doing this?
Click to expand...
Click to collapse
Ok. I'll explain to the best of my knowledge.
The zip I gave u is the most non-intrusive way of CWM. No ROM manager installer is needed on phone apart from placing this zip on sdcard root.
When the phone boots up, it loads the default recovery console. When we select "reinstall packages", it loads "update.zip" on the sdcard root by default. Since the update.zip we have there is the CWM zip, it loads it therby loading CWM console.
If u don't want CWM, just delete this update.zip.
Hope this helps.
I have this exact same issue ROM Manager is doing nothing but rebooting into recovery. So if I use your workaround, I need to keep this update.zip file on my device at all times?
NISMOFO said:
I have this exact same issue ROM Manager is doing nothing but rebooting into recovery. So if I use your workaround, I need to keep this update.zip file on my device at all times?
Click to expand...
Click to collapse
Yes best to do so
All ROM Manager does is download the update.zip that was posted and put it on your SD Card. The other steps need to be done regardless.
MikeyMike01 said:
All ROM Manager does is download the update.zip that was posted and put it on your SD Card. The other steps need to be done regardless.
Click to expand...
Click to collapse
I got the ROM backup working. I guess I was too impatient the first time. I cleared/moved a lot of stuff off my internal SD card too....doubt that it mattered.
But it works quite well.
Hi All
I looked around and didnt see anyone with my problem, I installed Rom Manager on my NC and when i went into recovery my NC just started boot looping. Does anyone have any suggestions on how i can fix this?
Same Problem....
Sorry I can't help I'm having the same problem I installed ROM Manager, tapped Backup Current Rom, clicked Ok and now it just keeps booting until it displays "Touch the Future of Reading" then turns off and does it all over again, I have tried interrupting the boot 8 times unfortunately I don't really think there is anything I'm interrupting as not only did that not work if I let it just sit it does the exact same thing without reverting to its non-rooted state. Please anyone help!!!
When in the loop...wait Dorothy to turn off... then just as it starts up hold power and n button for 4-5 seconds and release...should boot you into CWM. Then either try clearing cache and dalvik cache then reboot. What where you doing when it happened? Installing kernel? Making backup? Do you have the newest version of cwm?
Sent from my LogicPD Zoom2 using XDA App
If you look in the nook color development subforum right now there is a thread called how to boot into recovery and it explains and shows exactly what I mean... check it.out.
Sent from my LogicPD Zoom2 using XDA App
I already looked at a couple including one with a video showing you exactly how to do it (power/n buttons) it just keeps restarting like I'm not doing anything. I was trying to make a backup and ya i downloaded it yesterday
help plz. samsung galaxy s - after install ROM MANAGER click backup after - you have to install clockworkmod - i clicked YES - and problem - all the time my phone is restart in clockworkmod and and cant choose any option - apply sd card e.t.c. please help me what can i do for get my phone alive. step by step please my mates. thank you in advance. [email protected]
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
Worked PERFECTLY!!! Thank you!!! I thought i was screwed! CWR screwed this thing into a loop! YOU ARE A SAVIOR!
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
STICKY PLEASE!!!!! This is amazing and it freakin buried!
I found that if you install cwr from rom manager that if you reboot before rebooting into cwr, you will avoid the cwr boot loop.
I think this is a problem with any nook waswith 1.1 and rooted with AN3.0
Sent from my LogicPD Zoom2 using XDA App
I don't see the need of removing CWR. Setting BootCnt to 0 should be enough..
Use:
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
And you can also make a flashable zip of it if people are adb-phobic..
Sam
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
You, sir, saved me from tossing my NC in a fit of frustration. CWR had me in Nook purgatory for 6 hours... Thank you kindly!
samuelhalff said:
I don't see the need of removing CWR. Setting BootCnt to 0 should be enough..
Use:
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
And you can also make a flashable zip of it if people are adb-phobic..
Sam
Click to expand...
Click to collapse
Sam, what you have will actually keep it in recovery - you're setting it to a count of 8.
However, this should *really* fix it (from adb shell):
mount /dev/block/mmcblk0p2 /rom
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
dd if=/dev/zero of=/rom/bcb bs=1 count=1088
umount /rom
The above fix is apparently in an upcoming CWR release (in git now). The /rom/bcb bit is apparently what causes the "Installation Failed" message, too.
As I mentioned, the zip I posted above will uninstall CWR. The bit above will fix the boot loop, but it will most likely reappear the next time you boot into recovery.
This worked perfect. Saved my CM7 install.
You're right sorry. Read the thread a bit quickly. Thaught it was standard bootlooping..
Sent from my NookColor using Tapatalk
damned that i didnt see that thread.. i passed 3 hours before testing this solution..
I don't know if its related but from now i can't install from market, it just download app and say "download successfull" . No installation..
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
I am having exactly the same problem. But this solution isn't working for me. When I install the attachemnt I get an error:
--Installing: /sdcard/uninstall-CWR.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/uninstall-CWR.zip
(Status 0)
Installation aborted.
I didn't know if that was the error referred to above, but I reboot multiple times after this and it continues to boot into recovery mode. I've downloaded and transferred the file to the g tablet twice.
Please help.
Thanks
A clear flag on CWR would sure be nice. Here I am at work and have no way of removing it.
To give some background, I was booted, and in ROM manager, I clicked reboot to recovery - didn't work, so I figure "what the hell, let's kill it and try again." Wrong... So then I manage to get it rebooted into recovery, I do a factory reset (thinking everything's hosed at this point), then try to reboot, and what do you know? Yep, recovery again.
My guess is all this started after I updated SuperUser ... things started going weird after that.
Ah yes, and after a restore, I click on reboot system now - and it turns the device off??? Wonky...
edit: OMG... now the damn thing won't turn on at all... This is beautiful crap here...
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
Thanks, Edison. This solution worked perfectly.
I'd like to use this rom http://forum.xda-developers.com/showthread.php?t=929678 but after the each flash I got reboot and boot loop.
SPL: 1.33.0013d
Radio: 2.22.27.08
Recovery: ra-dream-v1.7.0
EXT4
I made superwipe, than powered off and back to recovery and flash rom.
When the rom is flashed and I login to google everything is ok, but when I tap on the "android market" and this one is loading, suddenly I got reboot and loop, like i said, but when I flash ROM and reboot this after login to google (without taping on android market) I get boot loop too.
Here is a logcat from the first boot, through login to google, run the "android market", reboot and a few boot loop
Code:
http://wklej.org/hash/a809611d593/
Edit://
I've changed the SD with no result
It was said that Froyo ROMs do not support SD EXT4. Re-partition your SD-Card with EXT2 and re-flash ROM. This should work.
uvt_novice said:
It was said that Froyo ROMs do not support SD EXT4. Re-partition your SD-Card with EXT2 and re-flash ROM. This should work.
Click to expand...
Click to collapse
I'm currently running on this FroyoByLaszlo rom and it is recommended to use EXT4 partition.
In regards to your problem, start from the beginning by using Ohsaka Wipe script and remember to wipe your sd-ext partition too ( just wipe everything )
After flashing rom, skip first the google login, now try start the google talk application and fill in your google account information, let google talk signed in
Now try go to the market. Hopefully it will help.
No results.
When I signed in to GTalk it looked promising, but when I left GTalk I got gapps FC. First running of MARKET was almost good, I accepted rules and it was loading and loading and rebooted and boot loop again.
I was using ext2 and the same result.
I'll check FroyoByLaszlo-5.2.zip 'cause I was trying to run polish version.
Edit:// The same.
Edit2:// v4: market was working but after reboot the rom didn't wake up.
meatman91 said:
No results.
When I signed in to GTalk it looked promising, but when I left GTalk I got gapps FC. First running of MARKET was almost good, I accepted rules and it was loading and loading and rebooted and boot loop again.
I was using ext2 and the same result.
I'll check FroyoByLaszlo-5.2.zip 'cause I was trying to run polish version.
Edit:// The same.
Edit2:// v4: market was working but after reboot the rom didn't wake up.
Click to expand...
Click to collapse
Follow these steps, if it still does not work check in on my Irc channel..
This is if you have fastboot....
In fastboot USB mode type the following in a command prompt on your PC pressing enter after each line -
fastboot erase system -w
fastboot erase boot
Now boot to recovery and do the following in order -
1) Delete the rom you have on your SD-Card and redownload it. (This is to cut out a bad transfer/copy)
2) Flash Superwipe v2 making sure to READ the printout when it's finished and powering off the phone and NOT rebooting it.
3) Boot back to recovery.
4) Flash Superwipe v2 again and again power off.
5) Boot to recovery.
6) Flash the rom.
7) Boot phone and let it sit at the Welcome screen for TEN minutes (I don't mean six or eight minutes... I mean TEN!) go and watch some youtube videos or something
8) Skip through the wizard.
9) Give phone a few minutes to setup and sort itself out and reboot phone.
10) Open market and proceed with sign in.
All should be good but if not as I said hit me up in my Irc channel, link is in my sig below.
No result. I left the phone for 10m and 5minutes, after reboot the phone had the boot animation loops, than I removed the battery and the phone is staying on splash screen.
Logcat form splash screen
Code:
wklej.org/id/488590/
Hi everybody I had a question, I tried installing TWRP from goomanager for the touchpad the other day. When it installed I went in to moboot and tried opening it it gave me the error invalid size. Also, after installing TWRP to option for clockwork mod disappeared on my moboot. So through intrernalz pro on web os I was able to remove the uimage of twrp from the boot folder, but that left me with only the option to boot into cyanogenmod and no type of recovery option available. I tried using acmeinstaller2, to just install CWM but after restarting there was nothing added to my moboot. I am sort of at a stand still since with out a recovery i cant update, nor can i recover from a back up. Any help would be appreciated. Thanks guys.
- Zero
zeroman9121 said:
Hi everybody I had a question, I tried installing TWRP from goomanager for the touchpad the other day. When it installed I went in to moboot and tried opening it it gave me the error invalid size. Also, after installing TWRP to option for clockwork mod disappeared on my moboot. So through intrernalz pro on web os I was able to remove the uimage of twrp from the boot folder, but that left me with only the option to boot into cyanogenmod and no type of recovery option available. I tried using acmeinstaller2, to just install CWM but after restarting there was nothing added to my moboot. I am sort of at a stand still since with out a recovery i cant update, nor can i recover from a back up. Any help would be appreciated. Thanks guys.
- Zero
Click to expand...
Click to collapse
Do you still have "ulmage.ClockworkMod" in the boot folder, it sounds like it must be gone or it should show up as an option in moboot? With mine when I installed TWRP it didn't change the options in moboot, moboot still says ClockworkMod but when that is selected it goes into TWRP and there is no "ulmage.TWRP" in my boot folder. I thought that was how TWRP was meant to install on the TP. I'm not sure if there is another way to install CWM other than with the ACME2installer, might be worth a search.
Did you make sure "update-cwm_tenderloin-1012" was in the "cminstall" folder when you ran ACME2?
You could move your backup to comp, run ACMEuninstaller and webos doctor and start from scratch and install CM9. Then just restore from your backup. I've done that a few times for other reasons.
Good Luck
Thanks for the help man, the CWM i was using was called recovery_cwm and i just had to change the name to update_cwm and let acmeinstaller do the rest. Saved me alot of time by avoiding uninstalling everything and restoring.
- Zero
CWM gone while installing TWRP through gooMan
Hi Zero,
Sorry but I am totally new to android and on how to install it in my TP. But, I was successfully running Cyanogenmod for sometime now until I thought of installing TWRP in my TP instead of CWM as installing nightly updates was becoming difficult for me.
I tried to install twrp through gooManager so that I would have both the option of Clockworkmod and twrp. SInce twrp is a better ui, I thought of using it instead of ClockworkMod.
So, I went to their site: teamw.in/project/twrp2/75
and followed the following:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
By doing so, it did not reboot but while I tried to reboot myself, I saw that the ClockWorkMod menu is gone from moboot and I have no recovery option left. The menu has 'Boot TWRP' but when selecting that, it says corrupt data and my TP hangs.
Please guide me in getting CWM back or get the TWRP.
Please help!!! Thanks in anticipation.
avisekhg said:
Hi Zero,
Sorry but I am totally new to android and on how to install it in my TP. But, I was successfully running Cyanogenmod for sometime now until I thought of installing TWRP in my TP instead of CWM as installing nightly updates was becoming difficult for me.
I tried to install twrp through gooManager so that I would have both the option of Clockworkmod and twrp. SInce twrp is a better ui, I thought of using it instead of ClockworkMod.
So, I went to their site: teamw.in/project/twrp2/75
and followed the following:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
By doing so, it did not reboot but while I tried to reboot myself, I saw that the ClockWorkMod menu is gone from moboot and I have no recovery option left. The menu has 'Boot TWRP' but when selecting that, it says corrupt data and my TP hangs.
Please guide me in getting CWM back or get the TWRP.
Please help!!! Thanks in anticipation.
Click to expand...
Click to collapse
If you have the install zip from sd card option, then flash jcsullins' recovery. Use the 12/15 version.
You can also install the same recovery using acmeinstaller 3.
There's a moboot cleaning utility, on the classic nerds' site (use it if you need to get rid of 'ghost' uimages).
Edit : here's the link to jcsullins' recovery : http://goo.im/devs/jcsullins/cmtouchpad/recovery
Edit 2 : here's another link that would be useful : http://forum.xda-developers.com/showthread.php?t=2030675&page=4