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.

[Q] CWM - Failed to mount /recovery

I just rooted and got everything up and running again. I have ClockworkMod installed and I am trying to do a backup now, but I get an error. Here is what it says during/after the backup:
SD Card Space free: 7568MB
.
Backing up Boot.....
.
Backing up Recovery.....
.
E:FAILED to mount /recovery ( Block device required )
.
Can't mount /recovery!
.
END
What could this mean and what can I do to fix it ? I dont even see a /recovery mount point.
Please advise !

Did you do it using IOMonster's root pack and install CWM using his zip? If so, you can try flashing CWM through ROM Manager. I'm having the exact same issue and nothing is working for me, but most seem to be able to flash CWM through RM and it's fixed.

eyecrispy said:
Did you do it using IOMonster's root pack and install CWM using his zip? If so, you can try flashing CWM through ROM Manager. I'm having the exact same issue and nothing is working for me, but most seem to be able to flash CWM through RM and it's fixed.
Click to expand...
Click to collapse
Yes I used his CWM zip. I have tried via Rom Manager and get the same result's. The only thing that is different is that IOMonster's recovery is using 3.0.0.5 and When I installed Rom Manager it downloaded 3.0.0.7 but then when I tried a backup via CWM the recovery changed back from 3.0.0.7 to 3.0.0.5 Not sure what thats about, but I dont see any reason why it cant find or mount the restore dir.
Im lost :O( I need to make a ROM backup !

I am in the exact same place you are. IOMonster says he's uploading a new version of his root pack tonight that will include a new flashable CWM. I'm hoping it'll work for me. If not, i'm going back to stock and rooting with autonooter to see if that fixes it. Did you root with IOMonster's root.zip? Or just his CWM?

eyecrispy said:
I am in the exact same place you are. IOMonster says he's uploading a new version of his root pack tonight that will include a new flashable CWM. I'm hoping it'll work for me. If not, i'm going back to stock and rooting with autonooter to see if that fixes it. Did you root with IOMonster's root.zip? Or just his CWM?
Click to expand...
Click to collapse
I rooted with IOMonster's root.zip I also used his gapps and block1.1 script's ... then I installed his CWM.
I wish someone can help us ! please let me know if you find a solution.

HELP! I bricked my captivate! :confused:

Hi,
I was trying the Gingerbread CynogenMod 7 and I think i have bricked my captivate. It does not start .. Any help is appreciated..
This is what i did:
I followed these steps :
Download the initial package: cm7-captivate-initial-package-XXXXXXXX-XX.zip (link below)
Extract it
Copy following files to your internal sdcard
- captivate-efsbackup.zip
- cm7-captivate-initial-XXXXXXXX-XX.zip
- cm7-captivate-radio-XXX.zip (pick the one you want, I use JK4)
Flash a Kernel that contains Clockworkmod recovery 2.X or 3.X using odin (e.g. I had http://forum.xda-developers.com/showthread.php?t=914284 )
!! Don't use "reboot recovery" command or other shiny things to do the step below !!
Reboot into recovery using 3-button-combo and apply captivate-efsbackup.zip.
Flash cm7-captivate-initial-kernel.tar as pda using odin without auto-reboot
Reboot into recovery using 3-button-combo
Choose "mounts & storage" and format system, data, cache
Apply zip from sdcard: cm7-captivate-initial-XXXXXXXX-XX.zip
Do a wipe!
Apply zip from sdcard: cm7-captivate-radio-XXX.zip
----------------------------------------------------------------------------------------
All this while it gave me an error : E: no misc partition found..
Then next step was to Copy Gapps to your internal sdcard and apply zip (link below)
Then i realised i forgot to copy this zip .. I was stuck.. So decided to revert back .. Restored the Nandroid partition which i had done earlier.. This was a Froyo Nandroid! Obviously it failed and now the phone is bricked!!!!!!!!!!
This is the first time i hve bricked my phone and I am freaking out! PLease help!

You could start by reading one of the 5000000 other threads just like this one.
I'm not trying to get on your case specifically, but there's only a few answers to this problem and I don't understand the need for a new thread every time.
Good luck
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Not sure why you extracted the zip file you can just flash that through clockwork. Try getting into download mode with the 3 button method to flash back to stock with odin
Ya never restore a nandroid backup if you are not on the exact same rom and version as the backup
Sent from my SGH-I897 using XDA App

[Q] HELP! :( Semi Bricked. Tried EVERYTHING

Ok
Please forgive me I have spent up to 7 hours today searching and trying but to no luck.
So I didnt realise what i was doing and Semi Bricked my Phone. I edited build.prop and saved it in MyExplorer(name?) to try and turn off the camera sounds and when I rebooted, it just gets stuck on the galaxy S 2 screen, boot loop.
I'm on SGSII (Australia) Stock Vodafone's ICS 4.0.3 Rooted.
I have CWM installed but tried a few things:
- I can get into Download MOde (no idea what to do here)
- I can get into CWM mode 5.0.2.7 Recovery mode but cant do anything still.
- I tried various Edify script builders to try and put the original build.prop back in but get multiple Status 0 errors whenever I try update.zip from the SD card.
- I tried rebuilding the backup on there and changing the build.prop file on there and trying to restore but MD5 check fails. Even tried rebuilding the MD5 file with the modified files and still no luck. MD5 files fails.
Would anyone have any suggestions and how to resolve this without a flash or wipe? I didnt back recent backup and will lose everything.
I am coming to a point where I really am wanting to back to Apple
There are 2 build.props attached. One is the bad one that stopped me from booting up and I found another one that was named .bak (extension taken off) I found in the same directory (/SYSTEM)
If anyone can help me build an update.zip to push in via CVM I would greatly be in your debt (I tried for 4 hours with no luck)

If you have recovery and download mode yet nothing is lost.
In first, do saved your apps ?
If you had saved them or if it doesn't matter to you, reflash a rom via recovery
LINK HERE:
http://download.cyanogenmod.com/get/jenkins/2773/cm-9-20120615-NIGHTLY-galaxys2.zip
Flash it GoogleApps folder
http://goo.im/gapps/gapps-ics-20120317-signed.zip
The rom that I attached to the reply is a CM9 ICS version, it's quitly stable and we can have some settings on it.
If it doesn't work reflash with Odin (it's with software who use the Download Mode)
http://hotfile.com/dl/149514867/aea2f22/I9100XXLPQ_I9100OXALPQ_XEO.zip.html
Instructions
-Unzip the Rom Folder ( I9100XXLPQ..........)
-Open the included Odin
-Put your phone on Download Mode
-Click PDA and select I9100_CODE_I9100XXKP*_CL*_REV02_user_low_ship.tar.md5
-Click PHONE and select MODEM_I9100XX*_REV_02_CL*.tar.md5
-Click CSC and GT-I9100-MULTI-CSC-OXA*.tar.md5
-Click Start and don't touch anything still the colored case become green
-And now your phone resurrects
Reply me of results

thanks for your reply
unfortunately i didnt save my apps and havent got backups of my data either
i cant reach the file via ADB either, when i run ADB (have KIES installed and worked before) - adb devices.
nothing shows up when the phone is stuck on "Samsung GS2" screen.
do you have any recommendations around keeping my data there?

If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium

understood thanks
what if i just want to flash build.prop via update.zip?
i tried so many methods but it always fails. is anyone able to create a update.zip for me?

i used a GUI script creator to try and update it via CWM recovery mode but it doesnt seem to like it.
If i turn off signature verification, it gives me a (status 0) error saying : E: Error in /sdcard/update.zip
and if i turn on verification toggle, it says E: signature verification failed
can anyone help?

calum96 said:
If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
i know there are 2 types of ROMS right? the nonwipes and wipes. i really dont want the wipe versions.
the one i downloaded is 1G which i'd imagine is the wipe version if i were to upgrade via odin?
http://www.androidaddicted.com/firm...-vodafone-australia-firmware-update-1267.html

Can you mount any sd on your pc, because you can the recovery mount trick to access to your data.
When you are in the recovery menu, go to mount and storage and click on "mount usb storage" and the internal and external sd will appear on your pc.

you are posting in galaxy s thread....repost in galaxy s2 thread

I don't think so but then again I don't own a s2 but you can select advanced restore: restore data then flash a compatible ROM, then restore the data if you worried but as I said before flashing the same ROM shouldn't remove user data
Sent from my GT-I9000 using xda premium

How to install OTA files?

On sammobile these days a few OTA files are available, one like this. Can anybody help how to use this .zip file. The contents of the file are,
1. debug_info (1KB)
2. delta.hidden (856KB)
3. delta.modem (1KB)
4. delta.platform (78396KB)
5. delta.Sbl (1280KB
6. delta.ua (241KB)
7. delta.zImage (4855KB)
FYI these files are not Recovery or CWM flashables.
Above file is an update of firmware to N7000DDLR8 from the previous firmware DDLR6 for indian GalaxyNote. As one can see it includes the firmware files, so be assured that it can be installed. But How???

yogeshmishra23 said:
On sammobile these days a few OTA files are available, one like this. Can anybody help how to use this .zip file. The contents of the file are,
1. debug_info (1KB)
2. delta.hidden (856KB)
3. delta.modem (1KB)
4. delta.platform (78396KB)
5. delta.Sbl (1280KB
6. delta.ua (241KB)
7. delta.zImage (4855KB)
FYI these files are not Recovery or CWM flashables.
Above file is an update of firmware to N7000DDLR8 from the previous firmware DDLR6 for indian GalaxyNote. As one can see it includes the firmware files, so be assured that it can be installed. But How???
Click to expand...
Click to collapse
normal recovery --> install update.zip?

DMax99 said:
normal recovery --> install update.zip?
Click to expand...
Click to collapse
As mentioned in OP, this file is not updated by Recovery. It returns error with both the Recovery and CWM.

yogeshmishra23 said:
As mentioned in OP, this file is not updated by Recovery. It returns error with both the Recovery and CWM.
Click to expand...
Click to collapse
you can try to rename the file to update.zip and then choose update from recovery. Dont know if this will help but its worth a try.

It gives a signature verification error not sure just renaming it to update.zip would fix it!

jaskiratsingh said:
you can try to rename the file to update.zip and then choose update from recovery. Dont know if this will help but its worth a try.
Click to expand...
Click to collapse
Tried all these before posting. No luck
!
tommy_vercetti said:
It gives a signature verification error not sure just renaming it to update.zip would fix it!
Click to expand...
Click to collapse
That is true for Recovery and CWM shows Installation Aborted message.
Sent from my GT-N7000 using xda premium

Instruction available at this link on sammobile.
http://www.sammobile.com/2012/08/25...999-android-4-1-1-jelly-bean-test-ota-update/
But already tried, stock recovery gives signature verification error.
Sent from my GT-N7000 using xda premium

You should be on complete stock ROM
non rooted and on unsafe kernel then may it work, and thats is the point to be concern. This work with unsafe kernel as well update also contains unsafe kernel, so anything lead to messing your device, that will be risky to wipe anything. and in this situation you have to first flash safe kernel.
Mobile odin pro added support for flashing OTA files, but unfortunately didn't recognise OTA files which available for india. (this fuction in mobile odin is still on experiments)

struggling to get the same working , but in vain ...

Please tell me i download the bin file from the following site. how i install this
http://www.sammobile.com/firmware/?page=3&model=GT-P7510&pcode=0&os=1&type=3#firmware

i dont think any has been able to get the OTA downloaded from sammobile to work.
what r u trying to download.. which firmware?

yasirshafiq said:
Please tell me i download the bin file from the following site. how i install this
http://www.sammobile.com/firmware/?page=3&model=GT-P7510&pcode=0&os=1&type=3#firmware
Click to expand...
Click to collapse
using this method:
All Credits to tracid
1. Copy all files from the archive to /cache/fota/ or /data/fota if you have bigger ota
/cache folder is only 192 MB
use root explorer
2. from adb shell:
su
chmod -R 0777 /cache (optional)
echo -n "--install_fota" > /cache/recovery/command
exit
adb reboot recovery

doc.. i tried that last time with the DDLR9 update and i was stuck in boot loop.

Really I didn't tried yet, it was said by tracid somewhere.
Sent from my GT-N7100 using xda premium

Isn't mobile odin able to flash ota updates?
Sent from my Galaxy Note running ICS

no.. it doesnot recognize it as a valid update.zip

Hey doc where have you been lately sir??? Busy with note 2??? Plz dnt leave our note1 and haven't seen you in the jelly been thread as well which has been so active for the last few days sir...
Sent from my GT-N7000 using xda app-developers app

Yeah busy with note2 forum but still keeping eyes here too.
Sent from my GT-N7100 using xda premium