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.
Related
Hello!
I followed this guide and read the comments of everyone, and it's a reliable guide to rooting and installing a new ROM. The rooting went perfect, so I decided to go further and load cyanogen's latest ROM.
Power off your phone.
Boot into recovery mode. (Press and hold the Home key, then hit the power button).
Before you flash a rom file, perform a wipe. Press Alt+W to wipe the data and cache folders. You must wipe when going form different builds of Android.
Wait for the wipe to finish and the recovery image to display again, then select “apply any zip from sd”. Flash the zip file of your choice.
After flashing any zip you should be able to reboot your system and watch it load to the home screen.
After changing Android builds, it came take several minutes for the first boot. If you phone hangs on the animated Android logo, this is because you did not perform a wipe. If you are stuck in a boot loop, return to the recovery image and make sure you wipe.
Click to expand...
Click to collapse
-Taken from the guide
At the first time I rebooted it took me back to recovery, so using logic I rebooted again and now it is stuck at the T-Mobile G1 screen (the one before it normally shows the android)...
I know it's supposed to take several minutes.. but 30minutes is ridiculous -.-"
Can somebody please help me out before I do something stupid and remove the battery? Thanks so much..
You need to read a bit more then, because you would have learned that you have to install the 1.6ADP fro Htc before installing a cyanogen rom, that is one of the things you would know if you followed the guide in his thread...
-Best Regards
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
Don't think so It didn't say anything in this guide about that and several comments below recently show that they succeeded with the process..
tk112190 said:
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
Don't think so It didn't say anything in this guide about that and several comments below recently show that they succeeded with the process..
Click to expand...
Click to collapse
You have to listen to cyanogen plus that might be a different rom like enom or something.Cyanogen has a different maybe tricky install method.
You need to goto his thread.
-Go to http://developer.htc.com/adp.html
-DL the 1.6 "recovery image" the file name is - signed-dream_devphone_userdebug-ota-14721.zip
-Then DL CyanogenMod-XXXX
-put them both on your SD card
-Boot up into Amon_RA recovery by rebooting and holding the home button, do a wipe.
-update using any zip to that "recovery image" (signed-dream_devphone_userdebug-ota-14721.zip)
(it should auto reboot install radio then reboot again and load back up to the CMrecovery img screen)
-Then update any zip usig CyanogenMod (update-cm-xxxx-signed.zip)
-Then reboot the phone
Thanks a lot man.
I found the 1.6 ADP file and I have it downloaded onto my computer. Is there anyway I can put this on my SD card? It won't let me.. :/ If I could somehow get this on there, run it.. and THEN run the cyanogenrom.zip I think it could work again?
You need to delete the partitions with console while in recovery mode.
1.console
3.parted dev/block/mmcblk0
4.print
rm 1
rm 2
rm 3
quit
reboot recovery
Dont rename any of the files just leave them.
Now try it on your pc.
You need to delete the partitions with console while in recovery mode.
1.console
3.parted dev/block/mmcblk0
4.print
rm 1
rm 2
rm 3
quit
reboot recovery
Dont rename any of the files just leave them.
Now try it on your pc.
Thanks a lot for the help, I really appreciate it.
I took your advice and did those steps and it rebooted me into recovery like you commanded. I plugged it via USB into my computer hoping that the computer would recognize it and let me put the file on the SD card - but to no avail.
What is the next step I can take?
http://code.google.com/p/sapphire-port-dream/
I loaded the radio first...
and then I loaded the SPL...
and then I loaded the ROM...
I didn't go out of order. Was the problem that I didn't have the 1.6 ADP on my SD?
@Ace42: If I get a card reader and add the 1.6 ADP (signed-dream_devphone_userdebug-ota-14721.zip) to my sd card.... and load it. Can you tell me what to do from there?
Do I load that zip and then reload the ROM?
You may want to try Dwang1.13 rom. I don't think his rom requires the extra step to get the google apps.
Long story short: When restoring via Nandroid it hangs, when using advanced restore the data portion says
E:Can't mount /dev/block/mmcblk0p2
(file exists)
Error mounting DATA:!
Click to expand...
Click to collapse
This afternoon I tried running the Voodoo zip, but the one I downloaded from their site isn't for the Captivate. I ended up with a phone that was constantly displaying 90 degrees off from what it should have been (holding it straight up had the phone thinking I had it on its side).
I decided to uninstall voodoo by creating the "disable lagfix" folder on my card. I rebooted and the phone hung and remained hung at the spinning progress wheel for an hour. I pulled the battery since I couldn't get out of that screen. Rebooting after that had me in what appeared to be the stock version and showed a few of my non-stock apps as "com.etc..." apps.
More reading on here and I found the Captivate-specific version of Voodoo. I figured I'd try to install that before restoring from the Nandroid backup I ran before installing the Voodoo. However, when in recovery mode I couldn't "click" anything with the power button. I tried using adb reboot recovery which didn't fix the problem and instead put me into a non-stop cycle of non-functioning recovery modes after boots.
So I used Odin to get back to stock. Now I'm trying to restore back to where I was before Voodoo. I tried to just run a simple Restore but it hung and after 90 minutes it hadn't completed. So I tried to run an advanced restore and all sections restored except for Data. When I try to restore Data i get the error at the top of this post. I've googled for an answer and everything I've read so far is Cyanogen specific and appears to require Cyanogen to fully fix it. Anyone know how to fix this on a Captivate? Anyone have a link that I'm missing?
Thanks!
If you can boot the phone, then go into android terminal emulator (you may have to download it from the market first) and type mount in the terminal. See what type of partition /data is. If it's ext 4, the disable lagfix was not finished before you pulled the battery. Your best bet then is to download the Captivate voodoo beta 4 kernel version 1.6, which is sticky post in the Captivate development forum here, remove the disable lagfix folder/file from /sdcard/Voodoo/ and let it boot. It will then get you to the point where you should have been at first without having rotation issues and with a kernel that understand ext4. After that, restore your phone to the way it needs to be with Titanium, or by manually downloading and reinstalling any apps that got deleted by your premature battery pull. When ready to do a nandroid backup, do a disable lagfix and let it fully reboot to convert the ext4 to RFS. Then you can do a nandroid backup of restore, as clockwork recovery does not understand ext4 (yet).
Thanks Rajendra! I'll try that and follow up with the results.
I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.
Duplicate post (no way to delete I guess?)
RobertDeBord said:
I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.
Click to expand...
Click to collapse
Try this - once the phone boots - then go to internal sd card and see if there is a Voodoo folder (which there still should be) inside the Voodoo folder make a folder called disable-lagfix - reboot and it should go through the reverse process of creating the lagfix (robot voice). After it finishes reboot go to rom manager and restore.
Hope This Helps....
I can tell you, I've never had a successful restore from rom manager/clockwork recovery. Not once! The only thing that program is good for is as a replacement recovery reboot, it lets you select which zip you want to install from, rather than having to manually name everything to "update.zip". I can't honestly think of anything else its good for. I've tried literally dozens of restores on my captivate and everyone of them has crashed or frozen at some point during the restore. Worthless!!
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.
SO i was running nook color version 1.1.0 and i used the autonooter to get clockwork installed. I then tried to use the monster rootpack to install phiremod but after it says install is complete i rebooted but now every time i reboot it goes directly to clockwork and i cant get it to boot up normally. is there anything i can do besides a restore to stock to install phiremod/cm7 or exit recovery? BTW i did remove the monster sd card so thats not the reason its booting that way....
When booted to CWR, use adb:
adb shell
Check that rom is mounted with:
mount
You should see /rom somewhere in the returned result.
If it's mounted, do:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
If not:
mkdir /rom
mount /dev/block/mmcblk0p2 /rom
Then use previous command.
If that doesn't help, you can always flash my cwr remover .zip, found on my nook color restore to stock thread.
Sent from my HTC Desire using XDA App
thanks im going to try that right now.
So i am trying to run adb but it says device not found and i cant figure out how to get the device to mount
I had the same thing happen. In recovery, install the zip file in this post to remove recovery and keep it rooted. You will then be able to reboot normally.
http://forum.xda-developers.com/showthread.php?t=914690
I read that it does that with autonooter 3.0. What you need to do is reboot normally after flashing recovery (don't reboot into recovery immediately after flashing). Afterwards you can reboot into recovery.
Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.
krisslake said:
Hello guys,
I had the same problem, but with Team Win Recovery
I tried to remove TWR folder in sdcard, wipe Cache, Dalvik cache and even factory reset.
I installed a new rom, and as last attempt i tried to wipe all system tree, but nothing happen.
I tried to fix following the list showed in this post, but I'm not able to mount "mmcblk0p2".
Any ideas? There is a TWR remover ?
Advance thank for helps.
Click to expand...
Click to collapse
Not really sure what you are saying was your problem. But I have a lot of solutions to booting problems in my nook color tips thread linked in my signature. See items A8 and A12. And there is my partition repair thread.
Sent from my BNTV400 using Tapatalk
Hope someone can help me here...I already rooted my CDMA HTC Hero and was in process of installing the CM6 zip file from my sd card through ClockworkMod Recovery...After rebooting, It just shows the HTC screen and it just sits there. I took the battery out and reset back to the original...I am running 2.15 update and a build of 2.32.651.2...This is my first time rooting/modifying a phone...Thanks
douglaspott said:
Hope someone can help me here...I already rooted my CDMA HTC Hero and was in process of installing the CM6 zip file from my sd card through ClockworkMod Recovery...After rebooting, It just shows the HTC screen and it just sits there. I took the battery out and reset back to the original...I am running 2.15 update and a build of 2.32.651.2...This is my first time rooting/modifying a phone...Thanks
Click to expand...
Click to collapse
How long did it just sit there? Starting up a new ROM the first time sometimes takes a few minutes or more. It it's not rebooting itself, let it sit and load.
maybe
douglaspott said:
Hope someone can help me here...I already rooted my CDMA HTC Hero and was in process of installing the CM6 zip file from my sd card through ClockworkMod Recovery...After rebooting, It just shows the HTC screen and it just sits there. I took the battery out and reset back to the original...I am running 2.15 update and a build of 2.32.651.2...This is my first time rooting/modifying a phone...Thanks
Click to expand...
Click to collapse
more info is needed to help you. What steps did you take EXACTLY? get long winded. Like what root method, what recovery, what wipe process, what flash process, etc.
Okay...I used Z4Mod and went with a permanent root (seemed to be successful)...I grabbed the free version of ROM manager from the mkt place...I then flashed Clockwork Recovery in ROM Mgr...Finally, I selected "Install ROM from SD Card." A prompt showed up and I selected "Backup Existing ROM" and "Wipe Data and Cache." After checking OK, it rebooted and froze on the HTC screen for 15+ minutes two times. I have two zip files on my sd card: "update-cm-6.1.0-RC1-Heroc-signed.zip" and "gapps-mdpi-20101213-signed.zip" This is as far as I could get...thanks!
Well when you chose to backup existing rom that was good. When you chose to wipe data that was bad. Now your phone can't boot into anything because you wiped all of your data. But you were smart and made a backup. A general rule of thumb at least IMO
Is only wipe data if your flashing a new rom or having trouble with an exiting one. With that being said. Just boot into recovery by
Holding home and power until you see your recovery
Then look for an option that says install update zip from sd or update from sd. I don't use clockwork mod but I'm sure its something to that effect. Then choose install from sd or what ever the option was. Then you should see your two rom zips on your sd choose which one to install,let it finish and reboot. Being a fresh install it might take a minute. Or if you want to go back to your factory rom just look for an option that says restore and choose your backup you made when you used rom manger. Hope this helps good luck.
Yea its me Again With the
Modified Hero-
douglaspott said:
Okay...I used Z4Mod and went with a permanent root (seemed to be successful)...I grabbed the free version of ROM manager from the mkt place...I then flashed Clockwork Recovery in ROM Mgr...Finally, I selected "Install ROM from SD Card." A prompt showed up and I selected "Backup Existing ROM" and "Wipe Data and Cache." After checking OK, it rebooted and froze on the HTC screen for 15+ minutes two times. I have two zip files on my sd card: "update-cm-6.1.0-RC1-Heroc-signed.zip" and "gapps-mdpi-20101213-signed.zip" This is as far as I could get...thanks!
Click to expand...
Click to collapse
Instead of installing from ROM Manager, select the option to Reboot Into Recovery.
From there, select Wipe Data/Factory Reset, then select Wipe Cache Partition, then go into Advanced and select Wipe Dalvich Cache.
Once those steps are complete, go back to the main menu and select Install zip from SD Card, then select Choose zip from SD Card. Find the CM zip and select it.
Once it completes, select Install zip from SD card again, find the gapps zip and select it.
Go back to the main menu again, and select Reboot now.
That's an old build of 6.1 anyway, grab the "stable" release instead.
Thanks for all of your assistance. Where can I find a current, stable 6.1 download file? I will replace it on my sd card before going forward.
Also, how do I get to the boot/recovery screen? When I choose recovery, it freezes with the HTC screen...I have success getting the phone back to original when I select fastUSBboot, or something similar to that...
Trying powering off, then press and hold the Home button while you press and release (don't hold) the Power button.
If that doesn't work, try pressing the volume up button while pressing the Power button.
Turn off the phone and hold volume down and power. A white screen will appear from there press the home button. It will take a good 15 to 20 seconds to get into recovery. Are you waiting long enough???
Or power off phone and hold power and home untill it boots into your recovery remember it takes a few seconds 10 to 15 seconds
Yea its me Again With the
Modified Hero-
I selected the home key to get into recovery...after 10+ minutes of showing the HTC screen, I think there is something wrong. This goes back to the same issue when I originally attempted to install the CM ROM - it was supposed to reboot into recovery but instead restarted into a frozen HTC screen. What ele can I do? Can I just go back to original and try all over again? I had to take the battery out and reset the device...
After Fastbooting, I lost network access and can't get into the marketplace...When I go into ROM manager to restore the backup, it just sits and looks like it is working on it...How long should this take? Is 10 min too long?
So your able to boot into your rom right.??? So just go to rom manger and choose flash alternate recovery. Place a different recovery on your sd and flash it. Or just flash the clockwork recovery. Basically I think you need to get into recovery first.
Yea its me Again With the
Modified Hero-
I think you're right as far as getting into recovery being the key...Since my network is down, I had to try "Flash Alternative Recovery," but it showed "An error occurred while flashing your recovery" ...Is there another alternative to getting a new recovery installed?
My network connection just started working...I had to uncheck and recheck the connect to network...Clockwork recovery finally worked and I was able to install 6.0 and the Google apps...Thanks for all of your help! I do have one additional question - How do I set up my apps to store on the sd card instead of the internal memory? Thanks again
I'm having a similar issue as OP.
This is my first time trying to load CM7 on my Hero CDMA. I rooted my phone successfully and then installed Amon_Ra's Recovery (v1.6.2) and wiped the data/Dalvik-cache and then flashed CM7 and Google Apps. Everything seemed to install without problem.
However, when I reboot the device it doesn't get past the initial "HTC" screen.
I then attempted to use adb to look at the logs but when I boot into recovery mode and enable USB mode, the computer doesn't recognize an HTC device/serial:
c:\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
000000000000 recovery
and trying to access the logs or run shell commands through adb fails.
It's been stuck on the "HTC" logo for 10 minutes; I'm not sure if I just need to wait it out or if something has gone awry. Did I just brick my phone or can this be salvaged?
I managed to flash whatever I had backed up from nandroid, but it's incredibly unstable. Took several resets and almost an hour stuck on the "HTC" splash screen before booting. I have missed calls and can make them, which is a good sign, but I'm repeatedly hit with an error "The application Setup Wizard (process com.android.setupwizard) has stopped unexpectedly. Please try again.".
I can't post pastebin links since I'm new, but I have dumps of logcat and /proc/last_kmsg.
At this point I'd be happy to either get CM working OR revert back to a stable stock ROM.
How did you root ???
Also what's your baseband/ radio ??
Also what hboot are you currently on ??
Root-Hack_Mod*Always\
I needed to have a phone so I took it back to Sprint and they were able to do a factory reset. So while I'm glad it's not bricked, I'd prefer to have a better ROM on here.
I rooted using the following set of commands:
adb push asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
Firmware version 1.5
Baseband version: 1.04.01.09.21
Kernel version: 2.6.27-533ce29d [email protected]
Build number: 1.56.651.2 CL85027 release-keys
Software version: 1.56.651.2
Hardware version: 0002
I'm not sure how to find out the hboot version.
When you first rooted or before did you make a backup/nandroid ?? Also after you rooted did you flash a recovery ??
Root-Hack_Mod*Always\