I am trying to flash a kernel, but when I go to Rom Manager to boot CW all it does is stay on the Google logo with an unlocked lock. I know it's not bricked, but it's just... wtf? On 7.0.2 CM7 thanks.
reflash it from ROM manager. 3.0.2.4 is known to have bugs [you can retry if you want], its best if you go back to 3.0.0.5 or 3.0.2.5 (unofficial; found on forums)
Lol that worked, thanks, dunno why I didn't think of it.
Related
i tried flashing a CM rom with ROMmanager. but that program isn't working on my phone for some reason. every time i try to reboot the phone into the clockworkmod recovery screen, it just takes me to the phones normal recovery screen. i'm a bit of a noob because i've never done this before, so if anyone could give me an alternative to flashing a custom rom or just help me fix ROMmanager, that would be awesome. (i also planned on installing an overclocking kernel, so i don't know if other methods would have any effect on me being able to do that or not.)
try flashing with rsd lite 4.9
lumberjack40 said:
i tried flashing a CM rom with ROMmanager. but that program isn't working on my phone for some reason. every time i try to reboot the phone into the clockworkmod recovery screen, it just takes me to the phones normal recovery screen. i'm a bit of a noob because i've never done this before, so if anyone could give me an alternative to flashing a custom rom or just help me fix ROMmanager, that would be awesome. (i also planned on installing an overclocking kernel, so i don't know if other methods would have any effect on me being able to do that or not.)
Click to expand...
Click to collapse
While you are still on stock rom, the stock recovery will keep coming back on every reboot. Try flashing clockworkmod recovery from within Rom Manager, let the phone reboot and then flash it again. You should be able to flash a Custom Rom now.
This is how it worked for me.
DirkGently1 said:
While you are still on stock rom, the stock recovery will keep coming back on every reboot. Try flashing clockworkmod recovery from within Rom Manager, let the phone reboot and then flash it again. You should be able to flash a Custom Rom now.
This is how it worked for me.
Click to expand...
Click to collapse
well thats the problem. i flashed the clockworkmod recovery screen, but it's still taking me to the phones normal recovery screen.
Try flashing an alternate recovery then flash clockwork again. I had a similiar problem and this helped me.
Sent from my ADR6300 using Tapatalk
Everytime I try and restore a backup from cwm the phone reboots to the first mytouch boot screen and just stays there. Is there something I'm missing on how to restore a backup? I'm using cwm 3.0.0.5, I make a backup, then when I want to restore it, I wipe data and cache and hit restore backup. Once it's finished, I reboot the phone, then it just sits on the boot screen until I eventually decide to pull the battery.
j21blackjack said:
Everytime I try and restore a backup from cwm the phone reboots to the first mytouch boot screen and just stays there. Is there something I'm missing on how to restore a backup? I'm using cwm 3.0.0.5, I make a backup, then when I want to restore it, I wipe data and cache and hit restore backup. Once it's finished, I reboot the phone, then it just sits on the boot screen until I eventually decide to pull the battery.
Click to expand...
Click to collapse
Clockwork Recovery 3.0.0.5 will work only with 2.3 (gingerbread ROMs).
Since the stock ROM is 2.2.1 you need to use recovery image 2.x.
you are in luck though. re-Flash CM7 download Clockwork ROM Manager scroll to the bottom "All clockwork recoveries" and flash the highest 2.x version they have. Then you can restore your back up without problems.
Thanks, I actually found that exact answer about 10 minutes after I posted this. I did just that, flashed cm7 then flashed cwm 2.x. I wanted to try cm7 anyway, but after an hour just trying to get the market to work, I decided to just go back to good old iced glacier.
Sent from my HTC Glacier using XDA App
j21blackjack said:
Thanks, I actually found that exact answer about 10 minutes after I posted this. I did just that, flashed cm7 then flashed cwm 2.x. I wanted to try cm7 anyway, but after an hour just trying to get the market to work, I decided to just go back to good old iced glacier.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I bet you didn't flash gapps or the newer version of it. That's why you couldn't get the market to work.
Sent from my CM7 HTC Glacier using XDA App
coupetastic-droid said:
I bet you didn't flash gapps or the newer version of it. That's why you couldn't get the market to work.
Sent from my CM7 HTC Glacier using XDA App
Click to expand...
Click to collapse
I have no idea what I did, but eventually I got it all worked out. I'm now a very happy cm7 rc1 user with a 1.84GHz smartass kernel.
j21blackjack said:
I have no idea what I did, but eventually I got it all worked out. I'm now a very happy cm7 rc1 user with a 1.84GHz smartass kernel.
Click to expand...
Click to collapse
Glad it worked out for you, but you (and others who may have this problem) could save yourselves a lot of this by downloading TrueBlue's zip (from development sub-forum) and flash it. It has cwm 3.0.0.6 plus stock TMO recovery.
With CM 3.0.0.6 recovery (thanks to Option94 for that), you can backup/restore both Android 2.2.x (CM6) and 2.3.x (CM7). TrueBlue's thread OP gives you instructions on how to use it.
It is a modified ROM Manager that "disguises" cwm's 3.0.0.6 and the stock Recovery as cwm 3.0.0.5 and 2.5.1.4 respectively.
PS - if you use it - don't forget to "thank" him (and Option94 also).
UPdate - if you subsequently update ROM Manager, it does not wipe out the above scheme with the disguised cwm's - it still works the same (at least through ROM Manager 3.0.1.0).
gaww said:
Glad it worked out for you, but you (and others who may have this problem) could save yourselves a lot of this by downloading TrueBlue's zip (from development sub-forum) and flash it. It has cwm 3.0.0.6 plus stock TMO recovery.
With CM 3.0.0.6 recovery (thanks to Option94 for that), you can backup/restore both Android 2.2.x (CM6) and 2.3.x (CM7). TrueBlue's thread OP gives you instructions on how to use it.
It is a modified ROM Manager that "disguises" cwm's 3.0.0.6 and the stock Recovery as cwm 3.0.0.5 and 2.5.1.4 respectively.
PS - if you use it - don't forget to "thank" him (and Option94 also).
Click to expand...
Click to collapse
Did that yesterday, it works great.
Thats awesome news, I was just about to post the question about the 3.0.0.6 backwards compatibility with nandroid backups.. Thanks!
i have the same issue.i flashed CM7.its installed,now i go into ROM manager and scroll down and select "All ClockworkMod Recoveries" (2.5.1.4) but get "an error accured while flashing your recovery"?
what did i do wrong?am i missing some thing?
i also wanted to know how i install GAPPS while i have CM7 installed? thanks for any help
MTSDAN said:
i have the same issue.i flashed CM7.its installed,now i go into ROM manager and scroll down and select "All ClockworkMod Recoveries" (2.5.1.4) but get "an error accured while flashing your recovery"?
what did i do wrong?am i missing some thing?
i also wanted to know how i install GAPPS while i have CM7 installed? thanks for any help
Click to expand...
Click to collapse
ok i installed GAPPS ..but still having issues with the Clock work recovery
MTSDAN said:
i have the same issue.i flashed CM7.its installed,now i go into ROM manager and scroll down and select "All ClockworkMod Recoveries" (2.5.1.4) but get "an error accured while flashing your recovery"?
what did i do wrong?am i missing some thing?
i also wanted to know how i install GAPPS while i have CM7 installed? thanks for any help
Click to expand...
Click to collapse
Ignore all those BS. Go in Market and download Rom Manager 3.0.1.0 and then flash the latest 3.0.0.5 (orange) recovery image. Then place the GAPP anywhere in your SDCard long as you know where it is. Reboot it in to recovery but selecting it from Rom Manager and then when its booted select Install zip from SDCard> Choose zip from SDCard.
Flash the GApp.zip and be done. Just remember when you flash NB via full wipe you have to flash GApp.zip everytime but if you just mount new NB on top of old one then DO NOT flash GApp.zip again as it will still be on your device as it ment to be installed once in that case.
BlackSHELF said:
Ignore all those BS. Go in Market and download Rom Manager 3.0.1.0 and then flash the latest 3.0.0.5 (orange) recovery image. Then place the GAPP anywhere in your SDCard long as you know where it is. Reboot it in to recovery but selecting it from Rom Manager and then when its booted select Install zip from SDCard> Choose zip from SDCard.
Flash the GApp.zip and be done. Just remember when you flash NB via full wipe you have to flash GApp.zip everytime but if you just mount new NB on top of old one then DO NOT flash GApp.zip again as it will still be on your device as it ment to be installed once in that case.
Click to expand...
Click to collapse
thanks got gapps installed just fine but im having trouble with the rom manager im trying to install the laterClockwork recoveries (2.x)..but i keep getting an error
MTSDAN said:
thanks got gapps installed just fine but im having trouble with the rom manager im trying to install the laterClockwork recoveries (2.x)..but i keep getting an error
Click to expand...
Click to collapse
No you didn't do what I said then. Go to Market> Rom Manager (3.0.1.0)> Download/Install. Then run Rom Manager and flash 3.0.0.5(latest not 2.5.1.2/2.5.1.4). If you use 3.0.0.5 you don't have to worry about 3.x(orange) or 2.x(green) as you can run 2.2/2.3 based without changing it.
3.0.0.5 < not Rom Manager its Recovery.
3.0.1.0 < ver of Rom Manager with 3.0.0.5 Recovery frame.
Problem is for people who don't know it get confusing as 3.0.0.5 could mean Recovery and Rom Manager. As normally other software specify and have different type of scheme for framework and software but in this case they both share same number so it gets little confusing.
ok i installed 3.0.1.0 rom manager from market so now i should have no issues when restoring 2.2.1 roms or 2.3 roms?thanks for the help man im coming from a Vibrant that was lost/stolen..that vibrant was so easy to root lol.thanks again
MTSDAN said:
ok i installed 3.0.1.0 rom manager from market so now i should have no issues when restoring 2.2.1 roms or 2.3 roms?thanks for the help man im coming from a Vibrant that was lost/stolen..that vibrant was so easy to root lol.thanks again
Click to expand...
Click to collapse
Well if you flashed 3.0.0.5 Recovery then no you won't have to worry about Green(2.x EXT3) or Orange(3.x EXT4) as you can flash both.
I am somewhat new to this, I've been rooted for a while but finally got tired of the stock annoying stuff. I downloaded rom manager and kernel manager. I wanted to see if it worked so I flashed my kernel, it says its installed but it doesn't do a thing and when I do a reboot the menu still notes the original kernel. Wth!!!! And when I tried to do the cm7 rom it gets to the point where it tells me to restart recovery and it freezes on the HTC startup screen. I have to remove the battery to reboot it normally. Why is it doing this??? I have a stock rooted HTC EVO shift 4G. I do not have nand unlocked.
thronnos said:
I am somewhat new to this, I've been rooted for a while but finally got tired of the stock annoying stuff. I downloaded rom manager and kernel manager. I wanted to see if it worked so I flashed my kernel, it says its installed but it doesn't do a thing and when I do a reboot the menu still notes the original kernel. Wth!!!! And when I tried to do the cm7 rom it gets to the point where it tells me to restart recovery and it freezes on the HTC startup screen. I have to remove the battery to reboot it normally. Why is it doing this??? I have a stock rooted HTC EVO shift 4G. I do not have nand unlocked.
Click to expand...
Click to collapse
I'm no expert here, but I believe this has something to do with not having a custom recovery. Have a look in the EVO section for threads relating to amon-ra and ClockWorkMod (CWM). Hopefully this will help you around the recovery issue and allow you to flash your kernel.
Good luck!
just a thought mate.... you do know that you need to do a full wipe before installing CM7 & also make sure your using "Clockwork 3*** with CM7" & "not Clockwork 2*** with CM7" or you will get a bootloop!
Hope this helps
I have rooted several NS phones in the past and this time when I flashed the clockwork recovery image 3.0.0.5 crespo as usual everything was fine, when I updated the recovery to the latest 3.0.2.4 using ROM manager premium, the phone would take a long time to boot into recovery mode until finally it would just hang on the white google when booting into recovery mode???
I flashed back to the older 3.0.0.5 version and everything seems to be fine again? Is there a known bug with the newer version? Will the older version work with the upcoming 2.3.4 updates. Any help would be appreciated.
bakron1 said:
I have rooted several NS phones in the past and this time when I flashed the clockwork recovery image 3.0.0.5 crespo as usual everything was fine, when I updated the recovery to the latest 3.0.2.4 using ROM manager premium, the phone would take a long time to boot into recovery mode until finally it would just hang on the white google when booting into recovery mode???
I flashed back to the older 3.0.0.5 version and everything seems to be fine again? Is there a known bug with the newer version? Will the older version work with the upcoming 2.3.4 updates. Any help would be appreciated.
Click to expand...
Click to collapse
yea it it takes forever to load nothing to fix ATM i just use 3.0.0.5
if you want you could try a mod version 3.0.2.5 i haven't tried
http://forum.xda-developers.com/showthread.php?t=988686
Thanks for the info, I figured it was something with that version. I was going to flash the latest CM7 #66 Nightly to try 2.3.4 and wanted to make sure there where not going to be any issues.
By the way, I noticed you where running the latest nightly? I have 7.2 stable on my NS, can I just flash to the latest nightly or do I have to wipe and flash the latest google apps file to get the video chat function?
Actually i reverted back to 7.0.2 the new 2.3.4 nighty's seems to have issues mounting the sd card.
But to your question you dont have to wipe you can just update over 7.0.2 with new nightly and gaaps
Thanks for the heads up, I think I will stick with CM 7.0.2, I also run the netarcy kernel which has BTM and it has seemed to solve some of the issues I had with the CM kernel having random re-boots. I appreciate the information.
I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
CZ Eddie said:
I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
Click to expand...
Click to collapse
I dont know what ALOT of investment is.......but what i think happened here is this<<
You were on Gingerbread right, Infused v2.x.x and you made a Nandroid(thats fine)
u installed miUi and didnt have the luck you wanted...Thats fine
You went back to stock, and rooted and modded the Recovery so you could restore your nandroid....Thats fine
But if you went back to stock(Froyo Right) and try to load up a Gringerbread Nandroid on top it shouldnt work. Nandroids only back up the ROM not the Kernel......so you were in a sense trying to run a Gingerbread Rom on a Stock Froyo Kernel......
Go into CWM flash your Kernel, or use odin and flash a Ginger Kernel then go into CWM and RESTORE.
Happy FLashing
Didn't know that! That may explain a lot of my ROM frustrations.
I'll try this and report back.
Off to go find a suitable kernel....
I really should get my post count up so I can get past this horrible 10 post restriction.
Did you try initiating the flash through CWM or through ROM Manager? Honestly I don't prefer to do any work via ROM Manager, I always have more luck going through CWM and starting a flash from there. Kernel is the first place I'd start but you should also Factory Wipe and Cache Wipe each time you move between ROMs, sometimes you get very lucky and don't need to, most times you bork your phone, and if you're nandroiding back from a backup wiping before you restore is good practice just to make sure you don't leave anything behind from your old ROM.
I installed a gingerbread kernel:
http://forum.xda-developers.com/showthread.php?t=1212485
Version 1.1.
But it didn't work out.
So now I'm fighting with trying to get a stock Infused V2 ROM on there.
No luck yet. Once I do, I'll try the recovery again.
Btw, I'm using CWM for everything.
Go to mounts and storage in clockwork recovery then select format system then do your nand restore ...
Sent from my Samsung Infuse 4G - 1.6ghz
Wow, I was totally making some rookie (which I am) Android mistakes today.
Every time I tried to restore the backup image, I was doing it in CWM by selecting "install .zip from SD card". When I SHOULD have been using the "backup/restore" function.
I'm up & running again. All original apps/settings are restored. Great!
Now to start breaking things again, since I know how to restore from backup now.