Database Develop

[Q] Boot loop after going into recovery using clockwork mod

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.

After installing aroma guestekrnL phone only boots to CWM

Hello
I've tried installing guestekrnL on WIUI. When installing guestekrnL, the only thing I've ticked extra that was other than defaults was:
"Activate init.d functionality and convert file system to EXT4?
- yes
select if init.d is not working yet or if you don't know"
Well, after reboot WIUI was screaming that my sd card is broken and format may help. It formatted it, but it still didn't work. So I've rebooted to recovery via option in power dialog in order to restore old firmware. However there's a problem now: CWM Touch says that it can't write logs to /cache. Mounting /cache, /data or /emmc from recovery doesn't work, only /system and /sdcard are mounting correctly. I've tried BackToExt3 with no luck. I've tried wiping it many times, with no luck. My phone only boots now to CWM. I can't flash stock via APX mode, because I have broken USB port in my phone. What can I do?

Does restoring a backup, flashing a zip file or wiping work?

Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558

exinepl said:
Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558
Click to expand...
Click to collapse
the Touch CWM might be the issue......most of the times it is found as the source of some unknown issues for some or intermittent issues.
I use the non-touch one always
Hope it helps

Well, how do I flash new recovery from CWM using zip then?

exinepl said:
Well, how do I flash new recovery from CWM using zip then?
Click to expand...
Click to collapse
check for the CWM thread by Rusty....you have the instructions and process in it.
THERE YOU GO>>>SEE HERE
Hope it helps

Unfortunately, it needs USB. I need to flash it via existing recovery.

Mounting problems occur on some zips using touch recovery . Change cwm to non touch 5.0.2.8. But hey, did you flash a stock kernel on wiui ? you need another kernel, like etana, symbiosis.....or just use the one shipped with rom

Please help unbrick a Telus HTC One

Hi everyone.
I unlocked the bootloader and rooted a Telus HTC One. But the latest flash went wrong and I went into bootloop. Somehow, I seem to have gotten myself into a situation where there's no ROM installed. I can still get into Bootloader and Recovery. When I try to start the phone, it's stuck at "HTC Quietly Brilliant" screen.
I've tried factory resetting, wiping everything, relocking the bootloader and loading the Factory RUU Zip using the All-In-One tool kit by Hasoon, and sideloading a ROM. Nothing seems to work. I also managed to push a ROM to the phone using the adb push command. When I try to install it using TWRP, I get an error msg "Unable to open zip file." It failed using CWM recovery as well.
When I plug the phone into a computer, it recognizes something is plugged in. But I can't open the drive at all. I get error msgs when I try to mount sdcard, system, data, anything. Things don't seem to be mounting/recognized at all. HTC sync and drivers are installed.
Experts, what else can I try?

Try downloading a Telus clean nandroid backup. Then go back into recovery (depends of what nandroid you get, make sure you have the right recovery, so if you download a CWM nandroid use CWM).

G-Bus said:
Try downloading a Telus clean nandroid backup. Then go back into recovery (depends of what nandroid you get, make sure you have the right recovery, so if you download a CWM nandroid use CWM).
Click to expand...
Click to collapse
Thanks for the suggestion. Not having any luck finding a Telus nandroid. Would it make matters worse if I try to restore from a non-Telus nandroid? My phone can't mount the /sdcard right now. Suppose I'll have to adb push it to the phone again?

runlsd said:
Thanks for the suggestion. Not having any luck finding a Telus nandroid. Would it make matters worse if I try to restore from a non-Telus nandroid? My phone can't mount the /sdcard right now. Suppose I'll have to adb push it to the phone again?
Click to expand...
Click to collapse
You don't mount the sdcard in HTC One you mount the data partition.
Also what happens if you sideload a ROM?
PHP:
adb sideload <ROM>
Have you tried erasing cache after installing a ROM if successful?

Riyal said:
You don't mount the sdcard in HTC One you mount the data partition.
Also what happens if you sideload a ROM?
PHP:
adb sideload <ROM>
Have you tried erasing cache after installing a ROM if successful?
Click to expand...
Click to collapse
When I sideloaded, It said
Can't Open /sdcard/rom.zip" (bad).
Installation aborted
Sideloading now gives me this error
failed to open driver control: No such file or directory
Restarting adbd
hmm, okay. I thought since recovery says "Install zip from sdcard" i thought /sdcard needed to be mounted. /data is mounted at the moment. No connectivity between computer and the phone unless through the All-in-one kit.

Riyal said:
Have you tried erasing cache after installing a ROM if successful?
Click to expand...
Click to collapse
And I haven't had successfully installed a ROM since I bricked the phone.

Install a custom ROM and kernel on your USB from the computer, mount the USB in Twrp using the otg cable. Flash ROM, if it doesnt boot, flash the kernel.
Flashing the kernel fixed it for me.
Another way is to use an adb pusher app and transfer thevfiles to your SD card.
Sent from my Nexus 10 using XDA Premium HD app

Thanks everyone. Somehow it sideloaded when I tried for the twentieth time.

[Q] HTC One - Stuck and need help please.

Hi,
My new HTC One's vibrate isn't very strong, so the vendor is sending me a new one. I'm rooted though, so thought I'd better start looking at ways to "undo" the root. When looking at options on the HTC One Toolkit, I "somehow" did something to my phone. All I "Thought" I was doing was getting the version information off it, so I could find the correct RUU, but when trying to reboot after that, it just kept going back to the bootloader with some error like "re-locked" and "security warning".
After extensive searches, I learnt I could flash the unlock.bin file again to unlock it. Done...but then it just sat at the "Slim" logo [ROM I was running]. I could still boot into Recovery (CWM) and tried clearing cache and dalvik - but still sat at the "Slim" logo. So I started digging in. I tried to mount the SDcard in CWM, but wouldn't mount. So flashed TWRP, but same thing there. When I try to mount anything, the only folder it will let me select is "System" - nothing else mounts and my "Storage" reads "0 bytes".
So I thought maybe I'd lost root, everything was Read Only and that's why I couldn't write to anything. So using the HTC One toolkit, flashed SuperSu. Still same thing.
I did manage to adb the slim ROM and the gapps to /sdcard, but when I tried to install, nothing would "mount" in order to install it...so all I got was errors saying install failed, and a bunch of directories that couldn't be "mounted". In summary I've done the following with Fastboot:
Flashed Unlock file
Flashed boot.img (from Slim Rom)
flashed Recovery (CWM first, but now TWRP)
Fastboot Clear cache
But after all that, when I boot into Recovery, nothing mounts and I can't get past this. Any help you could provide would be MOST welcome!
Thanks in advance.
-- Edit --
Disregard - got it finally. Using TWRP, I formatted the data directory, and it was writeable again. Not sure if it helped, but I then resubmitted everything I did in the list above, booted to Recovery, and was then able to adb the ROM and Gapps over and it installed fine. Phew.... Still need to figure out how to get it all back to stock though. That's my next task.

Samsung galaxy note gt-n7000 stuck on boot

PLEASE HELP ME
I changed the battery of my Samsung and my phone got stuck on boot Modus. it shows the Samsung logo and then again the blue Rotation Samsung (whatever that is, i think every Samsung Shows it)
So it just keeps switching from one Samsung logo to another. I have installed SuperBean ROM Version from zai89 and havent done a backup lately. do you know what i could do now without losing all my data? I don't know my kernal Version and am desperate as hell..
I have been reading threw some Threads and read that I should Mount internal storage in recovery and copy all my files off. How exactly do I do that?
After that someone said full wipe and flash new ROM with Odin. But is that even possible if I don't know my Kernal Version?
As you can read I'm a noob, please explain step by step. I'm thankful for every answer!

First, try to boot into recovery. Then wipe cache and wipe dalvik cache. If the phone boots up again, everything is fine, if not tell us and we will give you further instructions.

G4liant said:
First, try to boot into recovery. Then wipe cache and wipe dalvik cache. If the phone boots up again, everything is fine, if not tell us and we will give you further instructions.
Click to expand...
Click to collapse
It's still stuck

Install adb drivers if you don't already.
Boot into recovery and and connect phone to pc.
Go to mounts and storage menu and unmount cache and data.
Open command prompt on pc a type adb shell. You should see a # symbol.
Then type
e2fsck -f -c -y /dev/block/mmcblk0p10
Once this is done, Wipe cache and dalvik and reboot. It. Might do a lot of things, wait till you get the # prompt back.