Have posted this a number of places with no luck, including Rom Mgr thread:
If I flash a rom, set it up, then back up, Rom Mgr will not reboot to system. Goes to X and hangs. Sometimes after 3 tries or so it works or if I Restore the recent backup it works. Nothing consistent.
This started when I used amon 2.0 to increase ext to 1024mb for running eVil's desire rom. I had numerous issues where I could not even back up or restore. Seemed to always hang on android-secure part. Since then I reformatted sdcard with sdformatter, then used RM to create 1024 ext3. Flashed fresh eVil HD Gamma rom. All went well, but again after setting everything up and then tapping on reboot into system it hung again. It did not hang after initial flashing of rom and Circle Battery .zip. It booted into system fine.
When I got back to system and homescreens, I uninstalled RM and reinstalled. Although, I had done that before, but before I reformatted sdcard.
So, if this keeps up, only conclusion is RM even though I installed latest from Market, or this rom is messing things up. But, no mention of this issue anywhere else. I will try to boot into Clockwork thru Quick Boot (did that before also) to get to recovery and see how it goes.
Anyone have any idea for a solution to this nightmare, or had a similar experience. Running out of ideas. I am going to dl latest MIUI rom and see how it performs. And maybe load an earlier version of eVil's HD rom.
Thanks for any help, know this is weird,
Ken
Only thing I would suggest is to stop using ROM manager. There is really no need for it. Anything you can do in that, you can do either in recovery, or via a terminal.
efrant said:
Only thing I would suggest is to stop using ROM manager. There is really no need for it. Anything you can do in that, you can do either in recovery, or via a terminal.
Click to expand...
Click to collapse
+1
IMO, using an in-OS software to control the recovery is risky. I prefer having full control by manually flashing everything!
Thanks guys for replying,
I can try reboot recovery thru terminal and Quick Boot. Although, it did it right after repartitioning with Amon_Ra. So, thought it might not be Rom Mgr.
Really thought the reformat of sdcard would do it. May have two issues. Next step is to get the latest eVil rom off and go back to previous version and/or repartition back to 512mb sdext.
Just Frustrated and Confused
Ken
Just an update guys, since you were kind enough to reply to my post
I have kept the 1024 sdext made thru RM/CW removed both eVil's roms and relashed a fresh MIUI. No issues so far, time will tell. Will probably reflash a MicroMod rom too. Can't believe the larger HD rom was the cause. I loved the rom.
If I figure it out one way or the other I'll update. I can't even google my problem and find someone else with it.
Ken
id get rid of rom manager and clockwork. i flashed many many many things/times with amon ra recovery alone without issues, but all i hear are problems with rom manager/clockwork. i mean how easy is it to just go into recovery and flash? or just download something through the browser... my 2 cents
I've been doing this for 8 months and started with amon. Never had issues with either amon or rm/cw. Started using rm/cw just to try when doing a lot of nightlies with cyan.
But, I recently repartitioned to 1024 sdext3 with amon to run desire rom and amon hung too.
Still 1024 and no hanging with MIUI, using rm/cw. I don't have a preference one way or the other, as long as it works.
Don't think it is either amon or rm/cw, but the rom and my ext not working well together. Had no issues with the 512 ext and desire rom. But, I was getting windows warnings on errors on my sdcard and thought it time to reformat anyway.
Thanks for the advice all, I will run MIUI and Micro for awhile and maybe go back to 512 ext.
Did learn for anyone using Rom Mgr that it does now do 1024 ext3 partitioning. Many people thought, as I, it stopped at 512 and ext2. Maybe it use to. Verified the ext 3 thru Mini Partition Tool Wizard. Just FYI.
Ken
Well,
I appreciate all the advice and help, I need it sometimes. But, seems (I hope) that I forgot to reboot into recovery after repartitioning. This tip came from Amon_RA and seems to have fixed my "reboot into system from recovery" issue.
I am now back on eVil's great HD Desire rom and 1024 sdext3 working great.
Thanks,
Ken
Related
i have done quite a few searches on this and yet have found nothing so i hope i dont get reamed for posting this.
if someone has a link for this answer id be very thankful.
if not then PLEASE SOMEONE EXPLAIN!!!!!!!
at the moment i am running drizzy hero rom. to do the update i did use the one touch root. on a second phone i did it manually. on both i added the hard spl and am running the RA v 1.2.1 recovery. I liked this ROM and wanted to see what bugs it had. after a few days i wanted to switch and try a different ROM I have dl most of the ROMs available and already have them on my sdcard once i did this no ROM would load except for Drizzy(new Vision v2.8). after trying a few things and accomplishing nothing i decided to redo EVERYTHING. unrooted my phone rooted again applied recovery made sure radio was to date and spl. and still nothing i cant even run the original jf1.5 that i was using before deciding to port. this issue is occuring on both phones. 1st phone was again done with one step root and the 2nd phone was done completly manually. I REALLY REALLY REALLY want to try these other roms SO PLEASE SOMEONE HELP. if you need more information on what i did with these phones ill gladly tell you step by step on what i did.
sorry for that.
I was using my G1 and also had a friends. On my g1 i used the one step root. I used the Instructions from The Unlocker.com. It uses flashrec.apk and also Amon Ra's recovery image. After that i went over to the How to Load a Custom ROM. same site. It asks you to check the Radio and the Spl. The radio is 2.22.19.26I and the spl used was the HARDSPL 1.33.2005.
Once i finished that i went and formated the sdcard to Fat32+Ext2+LinuxSwap also converted Ext2 to Ext3.Then I did-Move Dalvik Cache to SD. last 3 steps to speed up hero. after all of that I loaded 4 ROMS CyanogenMod ROM, jACXHeroSkiv Hero ROM v1.8, Drizzy’s NewVision TouchFlo ROM, and JF v1.5 Cupcake ROM. I have only flashed Drizzy's until last night.
I was unable to flash any other one and when i flashed back to drizzy I had problems loading it back but eventually loaded fully the issue was running the startup wizard it kept crashing. after a reboot it was ok.
Give us step by step on what you did and USE PARAGRAPHS
that whole thing looked like mumbo jumbo to me
put new lines where they belong to help separate out the steps you took
FIXED! thanks!
hobbitton said:
FIXED! thanks!
Click to expand...
Click to collapse
did you do a data wipe? you need to wipe going from hero to cupcake/donut
When I first did all of that I did. Am I supposed to data wipe everytime I switch the Rom?
hobbitton said:
When I first did all of that I did. Am I supposed to data wipe everytime I switch the Rom?
Click to expand...
Click to collapse
when your using hero rom's, yes.
if your upgrading cupcake roms (ie cyan 4.0.4 to 4.1.9.2 ), no
If its not working, WIPE
you cant go from hero to cupcake without wiping and not expect a lot of problems. they cause too many issues.
hero roms use the data partition differently
also remember to wipe /system/sd/ to clear all of that out. pull your /system/sd/ to your computer first though
thanks you guys it helped alot
I've been on XDA today for atleast 3 hours and havent gotten anywhere, I have owned my G1 since dec. 08, rooted it, and kept the firmware at 1.1. I have jesus freak recovery 1.41.
Like I said, I've been on XDA forums for 3 hours already and haven't had any clarity what so ever and am just frustrated right now. Without being 100% I managed to upgrade to 1.6 withy cyanogen 4.2.15.1 I lost everything that was on my phone, it hurts but I'm just frustrated to the point right now that the phone is functioning slower than before and theres lag between the screens and functions. With the upgrade, all of the phones original fucntions "contacts, alarm clock, calculator, etc." force closed and nothing worked, i tried to factory reset and because of the stupid sync issue from the begining skrewed me and about half of my info saved to my google account. I'm so frustrated right now.
I need to know how to install the newest recovery to hopefully work with Nand because I had to Manually rename the DRC83_base_defanged to update.zip and then had to manually rename update-cm-4.2.15.1-signed to update.zip to install each one at a time without having the ability to freely choose what zip i wanted to install.
I haven't been able to find what issues there are with using another phones firmware on the G1, i've seen the Hero firmware, the home screen looks gorgeous and runs like a dream, but I haven't been able to find anything saying that it is okay or a BAD idea to attempt to install it, also I havent been able to find any info on finding the newest g1 firmware or any mods to be able to make the g1 firmware look like the hero, or any other android platforms. I have just found constant cooked firmware after firmware with a hard time decyphering why one may be better than the other. If someone could help me, I would GREATLY appreciate it.
I continute to run into threads "how to root" or "down load this, and download this, and assuming you have something with options you dont have, make it work like this"
Please someone help.
First you need to upgrade your recovery b/c the one you have is very very Ancient with a capital A....You have to wipe before you flash the defanged then flash cyan w/o rebooting.
I want to upgrade my recovery, but I haven't found anything that can help me upgrade the thing. any links to tell me how to do it? and is there no order that I have to install the firmware? instead of having to go from 1.1 to 1.5 to 1.6, can i just go from 1.1 to 1.6 in one hit?
step 1: search the development forum for amon ra's recovery. read the instructions to flash it.
step 2: go to cyanogenmod.com and read the instructions for upgrading from scratch.
once you've done those two things, you'll be much happier.
maniacallyhappy said:
I want to upgrade my recovery, but I haven't found anything that can help me upgrade the thing. any links to tell me how to do it? and is there no order that I have to install the firmware? instead of having to go from 1.1 to 1.5 to 1.6, can i just go from 1.1 to 1.6 in one hit?
Click to expand...
Click to collapse
You don't re-root when you need to change roms you just wipe in recovery mode
You need amon_ra
http://forum.xda-developers.com/showthread.php?p=4647751#post4647751
Like the other guys have said, upgrade to Amon_RA recovery. This allows you to flash updates from any filename, not just update.zip. The link is in my signature, or it's on the G1 Dev Forum in the sticky threads.
After that, boot into recovery and go to the Wipe section. Wipe all the things there, not just data. I never used to wipe everything either and I found that was the source of alot of my problems when changing ROMs. Obviously if you have your SD card partitioned and you choose to wipe your ext then you will lose what is on there.
Cyanogen has good instructions on his Wiki, but basically you want to flash DRC83_base_defanged, DO NOT reboot, and flash CM over the top straight away, then reboot your phone and you'll have a nice clean CM install.
This flashes the HTC Developer image which includes legal Google apps (Gmail, Maps, etc) and then flashes CM over the top which includes all his cool changes but does not delete the Google apps which we aren't supposed to distribute because it's illegal. Perhaps you are not aware, but Cyanogen got a Cease & Desist letter from Google, which is why we now do the defanged base method. More ROMs are moving to this method as time goes on, Pay's ROM and Super D are two which do this.
As an aside, I have found CM is not the fastest ROM. Some people have had better success with a ROM called Super D which is quite popular and includes many of the Eclair bits and pieces which CM does anyway. I personally use Dwang's ROM which is a much more plain Donut image however it absolutely flies. Both of these are linked in my sig, and are usually within the first few pages of the G1 Dev Forum anyway.
Thank you guys so much! I really appreciate how helpful the community has been. I've been having some issues with the the upgrading and maintaining because of my memory card slot dying out. A lot of the times the system will not register that I have my micro sd card in it or it'll say the sd card is blank. I just hope the phone lasts the extra 6 months till the end of my contract
Sent from my T-Mobile G1 using XDA App
maniacallyhappy said:
I've been having some issues with the the upgrading and maintaining because of my memory card slot dying out. A lot of the times the system will not register that I have my micro sd card in it or it'll say the sd card is blank.
Click to expand...
Click to collapse
I used to have this problem too, but it went away when I moved to 1.6 (coincidentally the same time I replaced the SD Card that came with my phone with a new Class 6 card). So either the upgrade of the OS or the SD Card fixed it.
In going to have to try the new men card cause the system is already at 1.6 but the phone is still trying to kill itself.
Sent from my T-Mobile G1 using XDA App
I have been trying for the past 3 days to return my N1 to the stock program. I have unlocked the phone and i was enjoying rooting for the past 8 months. I installed many different builds like Modaco, LeoGingerbread, Rodrigues MIUI, MicroMod Gingerbread and then Cyanogen Mod 7 (build 36), that is when it started to have tons of force close and the programs would stop running.
I always cleared the phone before i installed a new build.
I decided to return the phone back to the original factory settings and start fresh but it is giving me some problems.
I have used many different version of the PASSIMG files on XDA but i always get an issue with an Android program stopping unexpectedly.
At first it was the Settings that did not work, i fixed that.
Now it is the Calendar AND Market who keep force closing.
I have been trying for the past 3 days looking for a solution but i have come to the end of my patience.....
If ANYONE has a solution, i would love to hear from you.
Right now i am just thinking of getting a new phone but i love my Nexus 1
This is the first phone i ever rooted so my knowledge of rooting is limited to the 8 months of installing different builds. I never created a program or modified any.
Thanks
Phone status right now
Canada
Nexus 1
Bell Network
HBOOT: 0.33.0012
Radio: 4.04.00.03_2
Dec 17 2009,13:05:23
Firmware: 2.1 Update1
Baseband: 32.26.0024U_4.04.00.03_2
Kernel version: 2.6.29-01117-g4bc62c2
Build number: EPF30
I am going to take a stab in the dark here...are you by chance using ClockWorkMod recovery? If so did you upgrade to 3.0.0.5? Assuming this is correct you are in the same boat as I was...your not going to like it but if you are first go back to 2.5.1.4 or older. Next you will need to format your entire SD card and repartition it, then do a restore. That should work. Hopefully you have backups of your SD card contents... If a restore doesn't work still then you may need to format and partition again and do a fresh install. I lost a lot of sleep the other night trying to figure out WTF happened. It seems that something it 3.0.0.5 changes the SD-EXT and cannot be repaired without a format. I was mad enough about the whole situation that I have ditched CWM and am now running RA.
Galloway said:
I am going to take a stab in the dark here...are you by chance using ClockWorkMod recovery? If so did you upgrade to 3.0.0.5? Assuming this is correct you are in the same boat as I was...your not going to like it but if you are first go back to 2.5.1.4 or older. Next you will need to format your entire SD card and repartition it, then do a restore. That should work. Hopefully you have backups of your SD card contents... If a restore doesn't work still then you may need to format and partition again and do a fresh install. I lost a lot of sleep the other night trying to figure out WTF happened. It seems that something it 3.0.0.5 changes the SD-EXT and cannot be repaired without a format. I was mad enough about the whole situation that I have ditched CWM and am now running RA.
Click to expand...
Click to collapse
I sis upgrade to the ClockWorkMod 3.0.0.7 and that is when the problem all started.
I downgraded to the 2.5.4 version and i was able to install the CyanogenMod 36 and then it really went all bad.
I was so frustrated that it was not working that i formated (and i did back it up) my SD card. Then i did what i said and i am still having issues.....
Where did you get and how did you install RA? I was used to the CWM and i really liked it until they upgraded to version 3.
Thanks
Look in Developer section.
Take your SD card out, reformat it in Windows, then put it back and repartition for EXT, if you're using old Apps2SD (/A2SD/Apps2EXT).
Wipe everything.
Install any ROM.
Enjoy.
ROM Manager says there's an update to Clockwork Mod. 3.0.0.x, is it safe to apply? Running CM7 rc2 right now.
Sent from my Nexus One using XDA App
Why wouldn't it be? And yes it's ok I've been using it since release with no problems.
Yeah it is safe to apply. I've been using it for quite a while.
I've tried to run with clockwork 3.x twice now, and both times my SD card (ext partition) got screwed up to the point that it couldn't mount. The only way I could recover was to reformat the entire card.
I don't know if it was clockwork 3.x, or user error, or just coincidence, but I've never had this problem at other times...
The web is full of similar examples, so until I know for sure, I refuse to use 3.x (I'm a clockwork fan, and use 2.5.1.4).
Sent from my Nexus One using XDA Premium App
Ive had some annoying issues with version 3 also. Never a problem in 2.x
I use RA when I have issues. 3 seems to integrate the GUI but causes problems while actually in recovery mode... I was wondering if I was the only one. I'm definitely a Clockwork fan.
Clockworkmod 3 has problems with sd card, in particular if you are using DT apps2sd.
In my case, it didn't restore to the sd card properly.
I reverted to clockwork 2.5.1.1 and was able to replay my backup. For now, I am staying with 2.5.
yeah cwm 3 has given me nothing but grief. refuses to flash roms, wiping sd card completely, left me in a sticky situation the other day as i had nothing to read my sd card, and have been stuck in the same situation again right now, switching to RA recovery from now on. nothing but grief.
however, glad to see im not just losing my mind and im not the only one experiencing things like this
general consensus is that it is safe some people though like me had issues with it. It wouldnt restore my backups correctly and would freeze in the process. Bc of this i stuck with version 2.5x
I had the same issue with CWM3 totally screwing up my ext3 partition, to top it all off I couldn't access any of my previous backups and wound up having to totally format the SD card complete, repartition and start from scratch with a backup on my PC that was several months old. VERY ANNOYING! Needless to say i now use AmonRA with ZERO issues and I will be pretty hard pressed to go back after that little fiasco...
mrkrizzle said:
general consensus is that it is safe some people though like me had issues with it. It wouldnt restore my backups correctly and would freeze in the process. Bc of this i stuck with version 2.5x
Click to expand...
Click to collapse
I couldn't get CWM 3 to complete a backup...pretty essential, so I went back to 2. May try the update and see if it works.
Long ago I had issues where my backup would freeze. Temp fix was to restore each individual section which allowed me to at least restore that backup.
I have a question, I was wondering if this is possible. OK, I have been on CM7 for a while now and now I'm looking into going back to stock now there is a way to run CM7 from an SD card, I would like to go that route from now on if possible. OK, little back ground first. I was on GMPower's Auto-Nooter 3.0 running 1.1 software version with CWR 3.0.0.5. When I made the choose to move to CM7, I made a full nanodroid backup first before I made any changes, I also did a test and did a restore to make sure it worked fine. Then I installed CM 7 with 3.0.1.0 and have been running fine (of course with the known issues that CM7 has). Now with the question, If I boot with my Monster RootPack Clockwork Recovery 3.0.0.5 SD since it's CMR 3.0.05, can I restore my nanodroid backup and it restore fine since it should restore all my emmc partitions? I know I would first wipe the cache and then format the /system and /data partitions then do the restore. With all that being said, or would I have to completely return my Nook back to stock and redo everything? If this has been answer please don't shot me and sorry for the bad grammar (I'm no English manger)...LOL
Thanks,
DG
It's possible - I just did the exact same thing myself. So, it can be accomplished. that being said - it took me a while to get it back. I consider myself fairly well versed in most things android (have a 1st gen droid phone for a while now - been through many custom roms), and on my Nook went from stock to rooted stock to cm7. I got to a point where I just wanted to start over fresh, so looked into getting back to a rooted stock version. From what I have found, a lot of what you will go through depends on how deeply you've delved into cm7 (mainly do you have clockwordmod installed on the internal memory, etc. My situation was running cm7 from internal, but was still using clockwork from an SD.
Long story short - my method went something like this (after many trials and errors):
- used the SD I installed CM7 with since it would boot into clockwork.
- formatted system and data
- applied stock 101 zip I had copied to the SD
- had some issues booting correctly (not sure if you will) but ended up holding power and 'n' for about 10 seconds to get to the factory restore and after that completed, my nook booted as it should into a fresh install
-re-rooted using autonooter.
I had attempted the "interrupt power 8x" trick but got nowhere with it since it was a huge pain in the butt to time it correctly. There are lots of great guides around, you just have to find the correct one for your particular situation and may have to use one to get to point A, then another to get to point B.
Hope my ramblings help - bottom line is yes, it's possible