I dont know what is causing it, i have done fastboot, wipe cache, dalvik cache and factory reset everything!!
I remember i loaded LiquidSmooth on it and it was working very good until i wanted to unlock the network so i had to put back the stock rom on.
I didnt kno about the RSD way so i jus made a back up from my other atrix hd running stock rom and restored it with CWM on my other Atrix HD that is giving the problem of boot loop now. Ever since i did that i wouldnt pass boot screen, no matter how much i flash rom, recovery and everything.
I feel like the is some corrupted files that needs to be cleared but it wont work with CWM wiping and formatting, need something better to wipe completely the files like superwipe or sumn.
Are you running the latest version of CWM? Maybe try a different recovery program such as the Touch version?
Yea... i tried everything i think is possible
audit13 said:
Are you running the latest version of CWM? Maybe try a different recovery program such as the Touch version?
Click to expand...
Click to collapse
I did try the touch recovery, phillz cwm recovery, twrp not working on it tho as it does not respoond to the touches
as i said tho, i think the problem is with corrupted files from when i restored a back that i got from another phone. i think i need something like superwipe or so to get rid of every file on the phone
If you have CWM on it, go to your "mounts and storage" and "mount /system", reboot and see if that works.
Related
Hey sorry if this has been asked before i couldn't find it anywhere so there is some problem with my phone i don't know what is happening every time i use to install a new Rom it use to install perfectly without any fc's boot loop errors etc, but from past 2 days i don't know why any ROM i try to install (even the one which i use to work perfectly) will not install perfectly there will be fc's boot loop error wont pass the X when i switch on the phone. Please help its driving me crazy
Make sure your wiping old data in recovery.. and if flashed a new kernal or radio could also cause a problem too
ilostchild said:
Make sure your wiping old data in recovery.. and if flashed a new kernal or radio could also cause a problem too
Click to expand...
Click to collapse
yes i did Wipe data/factory reset ,Wipe cache,Wipe Dalvik-cache but just now i discovered that after doing this and still last installed rom has not been wiped its still there wtf what should i do and yes i did install 2.6.34.1_AVS-925mV_BFS_1113Mhz kernel how do i completely wipe everything???
Umm also do wipe sd partition, then do another wipe factory and cache-.. then do a repair sd then try to flash new rom.. this is what i usually do when i install new roms
still no luck i even did clear storage then wiped everything and i dont use app2sd(ext) i dontunderstand what to do i even tried with the clockworkmod's recovery still the same
sorry man, My only guess and idea is try to flash back to a normal kernal, then flash rom.. only thing i can come up with atm, or you can wait and see if some one that comes up with a better solution
where can i find norman kernel or any kernel which can fix this?
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
Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.
some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that
Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).
I mean wipe cache partition from recovery. just try it and ley us know if it works
Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.
if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??
Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.
well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..
When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?
i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!
OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.
I've tried to look everywhere for info on this issue and the closest I got was in the developers thread where someone was going to flash from Fresh 2.4 to CM 6. Apologies if I'm completely dense here.
There seem to be tons of ins-and-outs that I'm not yet hip to like hboot versions and clockwork vs fastboot and etc.
I am running Fresh 2.4 and I'm getting the "Low on space" trouble that others have noted. I downloaded cyanogen 7.0.3 to my SD and installed ROM Manager. I am able to boot to ClockworkMod and can select the zip to install from. After CM installs I reboot and can't get past the boot screen. (As a side note, I notice the videos all have a white background with black HTC while my boot is gray HTC on black background.)
Is there something I'm missing? The only thought I had was to revert back to completely stock ROM and try to start all over again. Thanks!
1. Are you using any other mods/tweaks - Firerat's, Data2ext or such?
2. Did you wipe everything before flashing CM? Or what steps did you take before flashing CM?
andythegreenguy said:
1. Are you using any other mods/tweaks - Firerat's, Data2ext or such?
2. Did you wipe everything before flashing CM? Or what steps did you take before flashing CM?
Click to expand...
Click to collapse
1) no other tweaks. Just put Fresh 2.4 on and started using it.
2) In the ROM Manager I backed up after flashing to ClockworkMod. I've used that backup to get my phone working again. I also checked the boxes to wipe everything as I told it to install cyanogen from the SD card. I've also tried booting to recovery manually and scrolling to wipe/restore to factory before trying to install cyanogen from zip.
Make sure you wipe EVERYTHING
YoungSinema said:
Make sure you wipe EVERYTHING
Click to expand...
Click to collapse
From manual recovery (power + volume down -> home button) I "wipe data/factory reset" and I "wipe cache partition". I also "wipe dalvik cache" and "wipe battery stats" in the advanced menu.
I still get a persistent gray HTC text on black background boot screen.
tunafishman said:
From manual recovery (power + volume down -> home button) I "wipe data/factory reset" and I "wipe cache partition". I also "wipe dalvik cache" and "wipe battery stats" in the advanced menu.
I still get a persistent gray HTC text on black background boot screen.
Click to expand...
Click to collapse
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©
MattCrystal said:
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©
Click to expand...
Click to collapse
Yup. Id agree.
#Root/Hack-Mod_Always*
MattCrystal said:
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©
Click to expand...
Click to collapse
I've downloaded 7.0.3 twice and also 7.0.0 just for fun. All through my home internet onto a macbook pro and transferred via USB to the SD card.
I'll try again and make sure to only use the manual recovery. Also, thanks for the aosp suggestion!
It's a no-go on everything.
Formatted boot, system, data, and cache. Wiped dalvik cache and battery stats. Tried to install a fresh copy of CM7 and also tried AOSP 2.3.4 with same steps.
The only thing that doesn't stall at the boot screen is my backup.
There must be something about versions that is wrong here. Something isn't playing nice.
Excuse me sir. Don't mean to but in here. But I think you missed the part were matt suggested you reflash your recovery. Its good advice. Whatever your current recovery is try reflashing it, repeat the necessary wipes and flash your rom of choice. You can reflash your recovery threw adb or if your s-off threw an hercimg.zip or if you have a nand you can boot into you can do it threw terminal or rom manger.
#Root/Hack-Mod_Always*
Personally I bootload to flash any recovery but also I'm s-off. Its extremely easy and all you have to do is rename the file and move it to the root of the SD card. Using terminal emulator is also very easy if your not s-off. If your still unsure about some of this just keep asking us. More than willing to help. Here ill make it a little easier. Go find the s-off thread and make it happen. Ill throw you my renamed version of green lantern recovery. Trust me it works perfect. Still clockwork. Just different. Then all youll have to do is bootload the recovery then reboot to recovery. And you already know how to do that.
1st go to that s-off link
Dropbox link to greenlantern
http://db.tt/ORAwPdX
The file is named
greenlanternHERCIMG.zip, just delete the greenlatern part and it's good to go.
Heres the s-off thread. All you need is the zip in the bottom of the op. Then flash it through manual recovery as always now
Get the recovery working first then we can help fix the flashing rom if it continues
http://forum.xda-developers.com/showthread.php?t=759955
*I use bootloader just to be a dork really and watch it load for that 2 seconds it takes then reboot, but who's phone doesn't like a reboot .. honestly.
®patience is a virtue©
did the same thing bro
noob here
nandroid, nandroid , nandroid,,,got it?
wipe data,
wipe cashe,
wipe dalvic,
the only thing I do different sometimes ( when having trouble flashing)
format data,
formet cashe,
format system,
flash rom and enjoy
Learned this from a Dev that used to be here but is gone now. dont know why it works but it does.hope it helps
Update? Be nice to know what's happened
®patience is a virtue©
tunafishman said:
I've tried to look everywhere for info on this issue and the closest I got was in the developers thread where someone was going to flash from Fresh 2.4 to CM 6. Apologies if I'm completely dense here.
There seem to be tons of ins-and-outs that I'm not yet hip to like hboot versions and clockwork vs fastboot and etc.
I am running Fresh 2.4 and I'm getting the "Low on space" trouble that others have noted. I downloaded cyanogen 7.0.3 to my SD and installed ROM Manager. I am able to boot to ClockworkMod and can select the zip to install from. After CM installs I reboot and can't get past the boot screen. (As a side note, I notice the videos all have a white background with black HTC while my boot is gray HTC on black background.)
Is there something I'm missing? The only thought I had was to revert back to completely stock ROM and try to start all over again. Thanks!
Click to expand...
Click to collapse
Try Using the Firerats Tweek for the Low Space Issue!
As for the other Issue Firerats may Also Fix that Problem!
*Sent on My*
Fast as its Ever Been....
"Sprint" Hero.... Running My, *ExEnHeroC* Rom, w/Kifno's Twist, Also The XDA-BLUE.apk!! "Page 10" of My Thread!!
http://forum.xda-developers.com/showthread.php?t=957867
http://www.megaupload.com/?d=WTMLMK6M
http://www.mediafire.com/?bb1axugm0bw7oro
http://m.youtube.com/index?desktop_uri=/&gl=US#/profile?user=PMGRANDS
Hello!
Today, i decided to install cyanogemmod on my 2x. So i downloaded ROM manager and downloaded cyanogenmod. everything went fine until i was going to boot for the first time. I got into a bootloop. so i tried taking out the battery and all that stuff but it still would't work. So i tried to recover the phone. I recovered it to a month old backup (I could not find the one i made in ROM manager before i installed cyanogenmod) The recovery went fine. But, when i rebooted it got into a loop on the lg logo! (the one without the loading bar) it would just load the lg logo, be there for like 10sec, then it would do the same. I tried recovering one more time, but it didn't work. The same thing happend. What should i do? :S Should i wipe data/factory reset?
EDIT: My phone was on android 2.3.4 before i download cyanogenmod.
BTW before i installed cyanogenmod, i forgot to clear cache and data. I was in a hurry so i did't notice the screen popping up, I automatically pressed "ok" without selecting anything.
Thanks for the help
- Kashif
Different partitions... Look for something called backtoext3 in the dev section (or somewhere else) The problem is that when you flash a custom rom like CM you convert your filesystem to EXT4, while stock is EXT3.
So basically what you have to do is:
1) Reboot into recovery
2) Wipe everything
3) Flash Backtoext3 zip
4) Restore Nandroid.
This should work. this will take you back to stock.
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
kashi169 said:
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
Click to expand...
Click to collapse
Yes
Flashing backtoext3 is just flashing the zip file you put on the sd card. (and then install zip from SD ) an then restore your nandroid stock backup and you're back on stock.
But you said you wanted to try CM right? In that case, wipe everything (factory reset/data + cache + dalvik) and then flash the CM7 rom and you have CM! Don't worry about backtoext3, your partitions are already on EXT4, because of your prior CM flash.
Ohh! Thanks Can you send the files for cm (2.3.4)? I've found some, but im not sure if my phone is compitable with them :S im really afraid to mess something up again
My. Signature. (CM7 temasek's KANG = the best CM7 at the moment )
I did everything and i got into a bootloop at the skating andriod screen again
OK, restored my phone back... Now it wont connect to the network and the battery has a question mark inside it. It also says the battery level is 999% heelp
Nvm, got my phone back to normal still dont understand why cm wont work...
You need cwm5 to flash cm.
I have a G2x, which is basically the same phone. But anyway, I would recommend nvflashing CWM and not getting it from ROM Manager.
CWM 5.0.2.0 will do just fine, but it is indeed old...
Anyway, are you sure you waited long enough on the CM boot screen? The first boot might take a couple of minutes. (4 or 5)