Related
Ok, I'm guessing I misunderstood something. I'm a "noob" so bear with me...
here's what I did.
I was running cm v 4.2.9.1 and decided to try and upgrade to the latest version. I wiped and reflashed and got 4.2.14.1 running, but I felt it was slow (the reason I didnt use any other new version), so I came here looking to see any new roms.
I decided KiNgxKxlicK AOSP 2.1 rom looked cool, so I downloaded it and flashed it (yes I wiped first). I'm guessing this is where it went wrong. The rom took 30 mins to finally boot to home (longest ever) but the sweet nexus screen made it easier to bear. I DID NOT do anything with an spl or any radio (that part still kinda confuses me to be honest). I'm guessing this is why I am in the predicament that I am.
The KiNgxKxlicK AOSP 2.1 rom loads fine, but was VERY slow. I decided I'd just go back to cm v 4.2.9.1. I went to wipe and reflash, but the G1 screen never disappeared. I let it load for about 30 minutes and decided that was a bit ridiculous before removing the battery (mind you, it never got past the T Mobile G1 screen). I was, however, able to reflash KiNgxKxlicK AOSP 2.1 rom and run it. This is all I am able to do. When trying to reflash cyonagen it just hangs on the G1 screen.
I'm a noob so I don't know what went wrong or what I missed.
Can someone PLEASE help me out here and tell me what I need to do to fix this. Thanks
Additional Notes:
Can't get to settings running KiNgxKxlicK AOSP 2.1 AT ALL, and a lot of programs Force Close on the rom.
Thanks for any help/input you guys can provide.
Thanks
Do you have Amon Ra recovery?
No I do not believe so, as I am not exactly sure what that is?
UPDATE: I should also note I checked my SPL and Radio, both were very old (as I realized I followed an OLD guide when I rooted my phone)
I upgraded to the latest radio and SPL and still have the same problem...except King's rom doesn't force close when I go to "settings".....thats about the only difference (still slow/laggy, lots of programs still FC)
When you boot into recovery (holding home+power) it should tell you what recovery image you are using. (i.e. mine says v1.5.2 down at the bottom of the screen) I ran into a similar issue when I attempted to jump between roms without taking all the appropriate steps; all I did was reformat my sd card, wipe the phone, and reflashed my rom and it worked great after that.
I tried reformatting my sd card, even re-partitioned it and I'm still having the same problems:
CM wont get past g1 screen after flash, King's rom still pretty slow....
What do you gys recommend I do next? This is getting really frustrating
1st: Check if youre Formatting is correct
2nd: Wipe EVERYTHING
3rd: Re-Format
4th: Try downloading the ROM again. It could be an issue with the ROM's
5th: Check you have proper radio and SPL (1.33.2005 and 26I)
6th: Pray
Try them all hope one of them works for you dude.
why is it that that 99% of newbs are on cyanogen
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Here's what i suggest you do:
1> Download Amon_RA's recovery from here
here is a link to his thread
2> Transfer the file you just downloaded to the root of your sd
use this code to mount your sdcard from recovery console itself if needed
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
3>Disconnect usb and reboot to recovery (keep home pressed while powering on) or just type
reboot recovery if you are already in recovery console
4> Flash Amon's recovery:
Code:
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
when complete, reboot to recovery again
5>Partion your sd using amon's recovery (All data on SD will be lost so backup if needed)
[Alt+P] then [Alt+0] or scroll down using the trackball or the volume keys
follow the prompts, set your swap-size to 96 MB (use the vol keys) and 512 MB ext2. when done use the back button to go back and reboot
The above step will give you the partitions required to run any rom. Please make sure you meet the radio and SPL requirements before flashing a rom.
6>Transfer the latest CyanogenMod rom to your SD and flash it.
I would suggest that you try bbuchacher's SuperD rom (it requires Haykuro's Danger SPL)
make sure you flash the radio first and then the SPL if you dont already have it
P.S. When anyone says full wipe, they mean doing a factory reset, wiping your ext partition and wiping the dalvik-cache. These are the first 3 options in Amon_RA's recovery's wipe menu
what i would do....
make sure you flash the HTC recovery files first before you flash the CM rom
go for the defanged version of HTC
so...(once u have amon ra's latest recovery installed)
wipe everything
flash htc / defanged (DO NOT REBOOT!!!)
flash cm latest rom
ALLOW IT TO LOAD FULLY
reboot (personal preference)
create a nandroid backup for future **** ups
enjoy ur rom!!
j.
airmcnair06 said:
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Click to expand...
Click to collapse
1: Go to recovery console and type parted. A list will show up with your fat32,ext2/3/4,linux-swap settings.
2: Yes it does but you can never be too sure.
4: ok
thanx guys I followed the instructions MrBurrito and cqms13 gave and am now running the Super D rom just fine.
Thanks again!
very quick question..
did you wipe dalvik-cache?
Firerat said:
very quick question..
did you wipe dalvik-cache?
Click to expand...
Click to collapse
After installing the RA recovery, yes. I was running CM Recovery though when I began this thread, which is why I was not able to wipe dalvik
ok i flash roms everytime a new one comes out that i like
but i flashed htcclay fastest rom which is great. but now i try to flash other roms but it reverts back the the htcclay fastest rom.i do the standard things to flash a rom in recovery but it doesnt work. i just to flash super D lastest but it stated up with the super d start up.but the setup up screen said fastest?????? whats going wrong here?
are you making sure to do a complete wipe of the phone before flashing a new ROM?
pfkis2010 said:
ok i flash roms everytime a new one comes out that i like
but i flashed htcclay fastest rom which is great. but now i try to flash other roms but it reverts back the the htcclay fastest rom.i do the standard things to flash a rom in recovery but it doesnt work. i just to flash super D lastest but it stated up with the super d start up.but the setup up screen said fastest?????? whats going wrong here?
Click to expand...
Click to collapse
Be sure to do the following when flashing different ROMS:
Code:
Backup (not required but nice if you mess something up)
Wipe Data
Wipe EXT partitions
Repair EXT (I do this because I had problems with the EXT in the past, but most will say this isn't needed)
Then flash the rom. You shouldn't have any problems
WIPE
Yeah make sure to wipe the data, cache, and the ext. also make sure to repair the ext partition. After you've done that then you flash the rom that you desire.
Hi,
I'm researching flashing via CWR, ROM over ROM without flashing to Stock via ODIN. Specifically, I'm at Cog 3.02 with "base" Cognition Kernel/Modem thinking about going to Andromeda...both employ Voodoo/EXT4, so shouldn't need to disable lagfix (I think?)...
I read at this link (apologies for spaces, but I'm new so can't post actual links): h t t p : / / forum.xda-developers.com/showthread.php?t=900463
a spirited debate starting about page 4 that flashing to ODIN is effectively doubling your chances for a bad flash, and that recovering a bad flash via CWM is far easier (just try re-flash again...and again(?) until fail back to trying ODIN) than recovering a bad ODIN flash.
If that's true, what prep should I do first via CWR?
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Another question I had was regarding nandroid. I made a nandroid backup right after flashing to Cog. Do I really even need this? Since I haven't changed kernel/modem, wouldn't I be better off just flashing my initial Cog zip file?
Finally thanks to all who make this site kick_ss. Connexion2005's videos are indispensable for a newbie like me. People actually answer questions here, and the Devs suceed in delivering onto us a wolf in (out of the box) sheep's clothing...something AT&T and Samsung have failed to do.
Cognition 3.02 is my first and only custom ROM and DG, you have literally saved me from making my phone a brick the old fashioned way: throwing it against a wall. Running flawlessly since Jan 17th...at the same time, I am eager to see what else is out there, ***safely*** as possible.
Thanks in advance.
Since they are both ext 4 you should be ok.
The rom wipes, I clear davlik cache before flash and after, but there our no good reason as to why
Efs files, do you use kies? If so you may want to back them up, if not don't worry, I have never backed then up
Odin flash is not needed but my opinion is you should know how to use odin prior to flashing. Why panic to figure it out if something goes wrong,?
NANDROID only needed if youare going back to cog and after you have flushed the rom you want to restore settings
I think I got everything you asked
Thank you.
So really just the Dalvik cache wipe in CWR prior to.
Kies...soooo failed ever getting that working, and don't seem to need it.
Yeah I actually flashed ODIN1 unnecessarily prior to my flash to Cog. I was at stock and somehow thought ADW would mess it up...rook. I have build 1006 so good to know ODIN's there if I need it.
Re: Nandroid, but if I kept the initial zip for my flash to Cog wouldn't I just use that? Or does Nandroid do better job of ensuring good flash back to what I have right now?
Not familiar with flushing...Would I be able to restore Nandroid directly on top of ROM I'm switching off of?
Thanks again.
OP,
You'd double the chance of failure if all else were equal. I don't have statistics, but I have no doubt that failures happen far more often with odin flashes, though.
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Click to expand...
Click to collapse
The ROM install script does the wipe. This simply means all your apps and data will be erased (your pictures and anything on the internal and any external sdcard will not be deleted).
I never wipe the dalvik cache or cache partition before flashing. I only do that if I'm having issues like FCs (sometimes happens after a bad theme install, for example).
You probably should have backed up /efs before flashing anything, but that's not to say a backup now isn't a good idea. You only need to do this once.
If I recall, you do need to flash 2.1 to get the ID back. I'm not 100% sure there isn't another way.
WRT the nadroid backup, you don't really need it. What I do is keep 2 or 3 good CWM flashable ROMs and the CWM update.zip on my sdcard in case of problems. I also keep TiBU backup of my stuff there (which I also occasionally backup to my PC just in case my sdcard gets wiped for some reason).
One thing I would suggest is to be sure you have working button combos in case you ever need download mode (hopefully you never will, but it's always possible). If you don't have that, there is a clockwork flashable fix or you could just flash cognition or perception once and then flash whatever you want over them (you can do both flashes all without ever leaving recovery). That should fix the button combos since DG's ROMs include a good sbl.bin (I'm not a fan of that inclusion, but it is useful in this case). Since you are running Cog, I assume your download mode is already working.
Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...
Madtowndave said:
Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...
Click to expand...
Click to collapse
If the ROM you were running when you backed up is compatible with the new kernel then I don't see why there would be a problem. I don't do it, myself, but I'm not sure why. Maybe it's because I have the paid TiBU and I just use that.
Thanks again...
Yeah I bought full TiBu, so obviously that should work for the apps/data.
Did some more digging tonight and apparently Nandroid backup is ROM only, not Kernel...So seemingly would need to be on same Kernel at least to do proper Nandroid restore.
...that being the case, I guess I don't understand why people stress importance of running a Nandroid prior to and/or post ROM flash...am I missing something?
If you like a rom and set everything up but want to try another doing a nandroid allows you to restore once you flash the rom again.
Also good to run nandroid on new flash, so if you play with themes and something goes wrong you can restore
That makes sense.
Showing me newbie-ness since I haven't played around with themes yet...
...Figured I'd at least get 2nd ROM flash out the shoot before playing with kernels, modems or themes...
This thread is helpful for me. I appreciate your time.
This is along the lines of the question that I was going to post so figured would ask here. I too am considering trying out the new Andromeda. I am currently using Cog 3.04 and want to test out the new Andromeda. The TiBu I have right now is from when i was on stock as I just recently purchased this and Cog was my first flash.. Would i want to continue to use that backup when i flash to andromeda, or would it be better to run a full backup with tibu while cog is on there and then flash to andromeda and use the cog backup??
also,, from above, i could possibly just skip the step with odin and go straight to andromeda? or do I need to run odin and put it back to stock before going over to andromeda?
thanks
zug
Hey Zug,
Just flashed andromeda last night via method outlined above...did not revert to stock at all (no odin). Only issue thus far is market only showing very few installed apps under 'My Apps', but I think this is a common issue. Will research solution tonight (I did have some issues getting back all apps from TiBu, but after I restored missing apps twice and rebooted a few times they all appear to be back). Also my simi clock widget comes and goes, not sure why...might clear dalvik cache to see if that helps.
Regarding TiBu, it saves apps and data. It is not ROM specific...you just back it up, then after you flash new ROM you restore missing apps with data (do NOT restore system data).
EDIT: Resolved the My Apps Market issue (only a few were showing after flash) by going to Settings, Applications, Manage, go to Market, Clear Data, reboot. Search is my friend.
i897 running Andromeda 2.0
Thanks Madtowndave.. i might give that a try.. so, since my phone is rooted and what not, i can just go to the guide and start at the portion about puting the new rom on the sd card, rebooting it and what not in recovery and select that zip and flash it right ? (well condensed version of course) and it should all be good?? guessing if this fails can always use the odin and wipe it and go back?
since i added a few new apps, guessing then that i should use tibu and go ahead and reback up everything since this rom does the master clear and then reload them right?? and hate to ask.. but how do I do the nandroid? newbie still to android and i know that just backs up the rom, but is it a app to dl from market? was fishing around in phone and didnt quite see it yet. .but figured i would do a nandroid in case i want to go back to cog.. this smart?
thnx again
zug
I think most of your questions are answered by others in this thread...
One thing I noticed last night is that I only got red (voodoo) cwm recovery menu via 3 button or long press power and reboot to recovery...when I rebooted to recovery via ROM Manager, I got the green cwm recovery menu. Not sure if this matters, but in another forum (on Vibrant phone, our sgs cousin), they said to flash ROM via the red voodoo cwm menu (since cog and andromeda both employ voodoo you can leave it enabled).
Nandroid backup you can do either from ROM manager or in cwm recovery...
Also andromeda wipes the system data, not a master clear...your data on 16 gig internal memory should not be affected, but is very good idea to backup everything to pc per the flash custom ROM guide.
i897 running Andromeda 2.0
Thanks again madtown.. going to give it a try now.. as andromeda just finished DL'ing
Good luck, hope it goes smooth for you as it seemingly has for me...Feel like a bit of a heretic for not flashing to odin first...maybe I'm just lucky.
i897 running Andromeda 2.0
hmm. ok. .so did the reboot to recovery and installed andromeda.. did it take a tad bit for yours to boot into the phone portion after it got to the andromeda screen?? mine seemed like it was hanging and was about to worry.. but finally booted in.. so figured would see if yours did too? .. gonna test stuff out now and restore tibu
Yeah, did for me too...and yes I was worried. Pretty sure this is very normal on first boot into new ROM in general. Like I said, TiBu was a bit cranky for me and required 2 restores and reboots...
Really enjoying this ROM, btw.
i897 running Andromeda 2.0
yeh.. im still doing the install from tibu (getting paid version after tomorrow since payday since im hating have to select install for every app ) .. and then will reboot and test .. though one thing ive noticed that is diff from the video is the lock screen.. in his review it was the lock button and he swiped it up.. mine is set to a puzzle piece by default?? any idea??
edit.. k mine was a 1st time go for apps restored with tibu .this is pretty nice.. it does appear to be a lot faster/smoother than cog so far.. though the Keep the lights on app should keep my bottom buttons on all the time right? least thats what i thought i was from the video and mine seem to still fade out.. even though i hit the app and it said it was enabled..
changing unlock is in settings, display...
Dunno about lights, mine just worked. Make sure service started and reboot I guess.
i897 running Andromeda 2.0
ok.. that was what it was for the lock part.. thnx .. didnt know that was there for those 4 choices.. thought only could do the none, pattern, pw etc..
everything went fine until i decided to load my contacts/sms etc from tibu.. now when i rebooted to add them, i keep getting the message "Sorry, The application Swype (processcom.swype.android.inputmethod) has stopped unexpectedly.. please try again" constantly getting things like that about swype.. any idea what happened or what i need to do?
edit.. sucked it up and re-flashed ;( will just sync contacts and deal with the ones missing for now ;(
Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard
Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)
No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?
I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.
I will try the wipe version
What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App
I was still on stock (froyo 2.2). Actually still on it today
You were right. The wipe version worked fine. I have now to decide to keep it or not...lol
ROM is awasome was worth well the trouble.
Glad it worked out for you - have fun with the rom
Sent from my Desire Z
Hello again. Like in subject.
Issue happened when i tried to flash Liberty 5.1 ROM. Well i did not read all requirements ;/ - but i do have a nandroid backup that works like a charm (and i don't know why?)
specially about Radio: 2708+ and SPL: 1.33.0013d.
So i flashed it on Radio 26.91i and Hayakuro's SPL.
Than i read other requirements
3) Flash recovery-patch.zip.
So Dream was stuck in G1 logo. After super wipe i deciced to make 3) Flash recovery-patch.zip.. So i did. Still stuck on G1 logo. So i used this CMTD removing zip and i deciced to flash Radio: 2708+ and SPL: 1.33.0013d.. SO i did. Still nothing. i cannot flash any rom. Even DRC83_base_defanged gives a G1 stuck. Even logcat is't ready at the moment, and i cannot reboot it via SEND+Menu+END... battery removing, restoring nandroid, and on the road again.
Well i am stuck right now in 1.6 SuperD with RamHack, Radio: 2708+ and SPL: 1.33.0013d., 128 SWAP, 512 EXT which is superior fast, but i'd like to test other roms from time to time, and i am wondering why the device is being blocked on other roms. MTD should be restored, and even if i flash other rom on my nandroid backup (i remamber it should normally give bootloop) i am stuck with G1 logo.
If anyone could help me with this issue it would be super. I flashed many things to my G1 over the years (and this is third G1 ) but i have never been is situation when logcat shows -waiting for device-...
PS: i never got LIBERTY rom working :/
I have installed BananaBread 4.0 by Banana4444 and i think it's working. Logcat talks to me like crazy, Bootanimation breaks the glass. I wonder why...
Well i can see desktop
After a while playing with dekstop i will try to install something else and check if it will work.
Sometimes the remove.zip doesn't seem to work, I noticed that sometimes it needs to be flashed twice to get it to stick. You can always flash amonra again just to make sure.
Does adb work when you are using super d right now? If not then you probably have a driver issue. If it does then make a nandroid (sounds like you did) wipe all, supperwipe, fastboot -w, grab a known stable Rom (maybe ezgingerbread or froyobylaszlo) and flash that in recovery along with any gapps/kernel/etc. (Froyobylaszlo has gapps and kernel packaged with the Rom so try this one as nothing else needs to be flashed)
Sent from my Desire Z using xda premium
Sometimes the remove.zip doesn't seem to work, I noticed that sometimes it needs to be flashed twice to get it to stick. You can always flash amonra again just to make sure.
-Well i tried to flash it once, and after i sent AmonRA via fastboot. just to be sure its clean. It gave me no effect.
Does adb work when you are using super d right now? If not then you probably have a driver issue. If it does then make a nandroid (sounds like you did) wipe all, supperwipe, fastboot -w, grab a known stable Rom (maybe ezgingerbread or froyobylaszlo) and flash that in recovery along with any gapps/kernel/etc. (Froyobylaszlo has gapps and kernel packaged with the Rom so try this one as nothing else needs to be flashed)
- i tried to flash Defanged, superD, super E, superF, CM5,6,7,9,10, FroyoByLaszlo, Liberty, CronMod, Superfast and chromatic - every gave same effect. I have nandroid via recobery, and logcat works every time. just new flashed roms are stuck before logcat can be run from /system.
In the evening i will try Laszlos rom and i will post results here.
Dude. Are we the last G1 forum readers?
_________________________________
EDIT:
Now everything works... so just need to be on newest updates.