Hello, i dont own this phone, but my friend does and for the first time today he rooted his phone and installed cm7, I told him to install the latest stable version I found on get.cm. After that, i sent him a file with gapps, told him to wipe dalvik cache and flash it, now hes stuck on the cm logo. Did he brick the phone? Usually i know my phone is bricked when stuck on Lg logo in my case. Has anybody experienced such thing? and can you maybe tell me the hotkey combination to enter recovery? He has the cm7 kernel. Thank you.
Robertodipuccio said:
Hello, i dont own this phone, but my friend does and for the first time today he rooted his phone and installed cm7, I told him to install the latest stable version I found on get.cm. After that, i sent him a file with gapps, told him to wipe dalvik cache and flash it, now hes stuck on the cm logo. Did he brick the phone? Usually i know my phone is bricked when stuck on Lg logo in my case. Has anybody experienced such thing? and can you maybe tell me the hotkey combination to enter recovery? He has the cm7 kernel. Thank you.
Click to expand...
Click to collapse
It's not bricked. Google the definition of "bricked" before using it.
Just reinstall the rom, this time flash gapps exactly after.
abaaaabbbb63 said:
It's not bricked. Google the definition of "bricked" before using it.
Just reinstall the rom, this time flash gapps exactly after.
Click to expand...
Click to collapse
And make sure you're using the right gapps meant for CM7.
Sent from my HTC Desire using xda app-developers app
Related
I just installed cyanogen 6.1.1 for my first time on my phone everything went correctly and then when it went to boot up its stuck at the boot screen. What do I do???
Someone plzzz help idk what to do???
Sinistah_ said:
I just installed cyanogen 6.1.1 for my first time on my phone everything went correctly and then when it went to boot up its stuck at the boot screen. What do I do???
Click to expand...
Click to collapse
Sinistah_ said:
So I just installed cyanogen 6.1.1. And its stuck at the boot up screen... what do I do????
Click to expand...
Click to collapse
Please do not start new threads when people are trying to help you. Wait patiently for an answer before starting a new one. You have started 4 threads already about rooting your phone and the problems you have. Invest some time in reading, learning and understanding the wikis. Thank you.
Sorry. I'm just paniking for the fact my phone is stuck on the boot screen and I'm jusst trying to get help asap. And actually the other thread was about if my phone was rooted so this thread is on another topic.
Are you still able to boot into recovery? And if so, what is displayed in your screen?
So I took the battery out, put it back in.. held power and the volume button it took me to where it says s-off n did a system recover. It worked!!! Haha... now I wanna try again but can u tell me what I did wrong??? I downloaded the cyanogen 6.1.1 and just started it up with the google stuff. It rebooted did its thing n stayed at the boot screen... am I supposed to clear something?? I read somethin like that when I was on google with my gfs phone. (I'm out somewhere... made me panik more since I don't have access to a computer atm)
Sent from my T-Mobile G2 using XDA App
Which version of ClockworkMod are you using?
Since you trie to flash a CM6.1. rom (which is froyo, android 2.2 based) you must use a ClockworkMod 2.5.x or below (or compatible).
And did you install Engineering HBoot? Sorry for asking, but it's unclear to me what you exactly have been doing already.
I did the visionary/gfree root last night without the hboot. And I tried the cyanogen 6.1.1 which was suggested by another user on here in one of my threads.
Sent from my T-Mobile G2 using XDA App
Btw my clockworkmod says 3.0.0.5
Whatever version that was on the market is the one I downloaded.
Sent from my T-Mobile G2 using XDA App
Apart from the fact that it seems to me that you skipped a step (hboot), which you have to perform , you are also trying to flash a 2.2 rom with the wrong recovery. Try with the 2.5 version in the thread http://forum.xda-developers.com/showthread.php?t=898151
HLeenders said:
Apart from the fact that it seems to me that you skipped a step (hboot), which you have to perform , you are also trying to flash a 2.2 rom with the wrong recovery. Try with the 2.5 version in the thread http://forum.xda-developers.com/showthread.php?t=898151
Click to expand...
Click to collapse
First of all, flashing the engineering HBOOT is not required unless you want to use fastboot on your computer. Also, if you used ROM Manager to flash ClockworkMod Recovery, that version is supposed to support both 2.2 and 2.3 ROMs. It was only the beta version of the recovery that was on this forum that only supported 2.3 and not 2.2---unfortunately, it was also labeled 3.0.0.5 and caused lots of confusion).
As far as why you are stuck at the boot screen, did you wipe data/cache when you flashed the ROM? Whenever you switch to a completely different ROM (as opposed to simply upgrading one), it's a good practice to. Also, the first time you start a new ROM, it'll take longer to boot up since the phone will be rebuilding its dalvik-cache (on CM6.1, it's be at a CM animation).
Ahh yeahhh okay good. So u cleared it all up for me n now my phone is running great
Sent from my HTC Vision using XDA App
Hello all,
I've followed the installation in the CM site
i've installed the latest stable via CWM
and now it keeps showing me the welcome to android "touch tge android to begin" and than it goes to the CM load animation
please help
flashed kernel ?
without right kernel phone wont boot up.
resolved
i used the one in the cm zipped file
but i've used the RC ver and it worked,
maybe i did something wrong the first time, i can't put my finger on it
thanks anyway
Wipe cache and others before flashing
abd_alazeez2002 said:
Wipe cache and others before flashing
Click to expand...
Click to collapse
Beat me to it. I had the same problem when I flashed FXP052 because I rushed and forgot to wipe the data and the delvic. Follow the wiki and you shouldn't have any problems
Sent from my LT15i using xda premium
Ok so I flashed it the first time and it was successful but noticed market was not opening so I flash the latest gapps for cyonogen mod and then everthing fc so wiped and flash and now it won't even boot it gets stuck on splash screen. Is it cause of SD card is on ext 4 or is it smellkus recovery or what?? Any help is much appreciative
Try wiping cache and dalvik then fix permissions in recovery.
Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.
Ryan_28 said:
Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.
Click to expand...
Click to collapse
Exactly...I've never heard of this rom for the evo. So I question it.
teh roxxorz said:
Exactly...I've never heard of this rom for the evo. So I question it.
Click to expand...
Click to collapse
no its for the evo its under evo general development it was just released
Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.
Ryan_28 said:
Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.[/Q
Yes I could go into recovery and I actually fixed the issue. I'm guessing it was the recovery itself that I was using because now I flashed Among RA recovery and now is booted and working fine. A great Tom overall. Thanks guys for your help
Click to expand...
Click to collapse
Not to bother anyone, but I was trying to run the droid GTRv2.0 ROM on my EVO 4G and it wont get past the first screen.
Hello! I have managed to root my phone, but I got the set up wizard message and the gapps error. After a google search it told me I had the wrong version of gapps. However, when I go to the official gapps page, the download for cm 10.1 only works with 4.2.2 and not 4.1.2. The one for cm 10.0 is for 4.1.2, but on the hercules downloads page, the 10.1 stable release is already out (that's the one I used!). Does this mean I have to run 10.1 without gapps, or downgrade to 10.0 if I want gapps?
Trust me, I have searched for this. Any help would be appreciated.
if you are on 10.1 grab the first one on the page http://goo.im/gapps also double check make sure you have no market installed if you do then you dont need any gapps install everything from the market
Alright
Ok, I'm gonna try that. +1 thanks for you. Man, I'm such a noob. :crying: :crying:
Bro all good we (I) was all there gotta start some where :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Roulette
krazierokz said:
Bro all good we (I) was all there gotta start some where :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
It's circling now...it's been at it for about 5 minutes now...the wait is unbearable!
Circling
It appears to have no end to the blue circling boot screen. I tried clearing cache and factory reset using CWM, no cigar still. Any fixes for this?
The CM version is the 10.1 stable release for hercules.
The gapps version is the 20130301 version.
which link did you flash for the CM what thread point in the right direction where you flashed from ? if you booted up the first flash and gapps were incorrect it shouldnt matter when you update the gapps it wipes the old files just make sure to wipe dalvik/cache and reboot
My Idiocy
I am retarded. I decided to go and unroot the phone and flash a stock rom and try again. I then flashed twrp via odin (which I prefer now) with no problems. But for some reason, no matter how many times I clear everything and try different kernels, the device will just not root. I have tried the superuser zips from the official site, I have tried the superuser from CWM's site, nothing works. Gah. Now what? Am I stuck stock forever?
Babbalabba said:
? Am I stuck stock forever?
Click to expand...
Click to collapse
Just use TWRP to flash whatever (Hercules) ROM you want. Make sure you wipe dalvik, cache, system and data.
Alright, I will try a wipe again, and then flash a custom ROM. If it doesn't root me I will report back with the situation. Thank you for all your help!
Um, just another question before I proceed with wipe and rom...if the ROM is based off of JB 4.2.2, such as Cyanogen mod, will my phone just run 4.2.2 as part of the rom, or will it be incompatible?
EDIT: Never mind...
I love you all forever. It works, and I have gapps running and root access. Thank you so much...I really don't know what to say.
i tried to install a custom bootanimation with ROM Toolbox and unfortunately now its stuck on the bootanimation. This aint the first time that app has done something to my phone to cause bootloop either. So would it be worth a try to swap out the bootanimation thru ADB with the stock one from my ROM and see what happens? If i can whats the location of the .zip and B4 u ask no i didnt make a nandroid. I just hate doing a factory data reset and having to reinstall er'ything but honestly it feels like i do it once a week anyways. Thanks in advance for taking the time to help meh.
A bootloop won't happen if ROM Toolbox simply changed the bootanimation, which means ROM Toolbox must have done damage to other parts of the system. Hence, even if you throw in a new bootanimation, it likely won't help. Just reflash the ROM you're using (without wiping /data) and see what happens.
Sent from Google Nexus 4 @ CM10.2
AndyYan said:
A bootloop won't happen if ROM Toolbox simply changed the bootanimation, which means ROM Toolbox must have done damage to other parts of the system. Hence, even if you throw in a new bootanimation, it likely won't help. Just reflash the ROM you're using (without wiping /data) and see what happens.
Sent from Google Nexus 4 @ CM10.2
Click to expand...
Click to collapse
that worked perfect thank you, but its kinda ironic cause every time ive flashed a rom, either a new one or just updating my current one, ive done a full wipe and factory reset and ive had to reinstall all my apps, nao im dirrrrrrrty flashin er'ything from here on out!!
DowneyJM said:
that worked perfect thank you, but its kinda ironic cause every time ive flashed a rom, either a new one or just updating my current one, ive done a full wipe and factory reset and ive had to reinstall all my apps, nao im dirrrrrrrty flashin er'ything from here on out!!
Click to expand...
Click to collapse
Only dirty flash when you do a version upgrade of the same ROM... If you dirty flash one ROM over a different one you may face all sorts of Force Close.
Sent from Samsung Galaxy Nexus @ CM10.2
same problem
DowneyJM said:
i tried to install a custom bootanimation with ROM Toolbox and unfortunately now its stuck on the bootanimation. This aint the first time that app has done something to my phone to cause bootloop either. So would it be worth a try to swap out the bootanimation thru ADB with the stock one from my ROM and see what happens? If i can whats the location of the .zip and B4 u ask no i didnt make a nandroid. I just hate doing a factory data reset and having to reinstall er'ything but honestly it feels like i do it once a week anyways. Thanks in advance for taking the time to help meh.
Click to expand...
Click to collapse
i have faced the same problem and restored boot image from backup it worked .