Brick? - myTouch 4G Q&A, Help & Troubleshooting

I was trying to install cm6 on my phone so i could install cm7. I installed cm6 and now my phone only goes to the splash screen and just sits there.. i booted in to clockwork recovery and non of my back up will work just sits at the splash screen...

xXy3kXx said:
I was trying to install cm6 on my phone so i could install cm7. I installed cm6 and now my phone only goes to the splash screen and just sits there.. i booted in to clockwork recovery and non of my back up will work just sits at the splash screen...
Click to expand...
Click to collapse
What color is the text in your recovery screen?

oRANGE i flashed it to 3.00005 or what ever

Stock, CM6 and all Froyo (Android 2.2) based ROMs are incompatibile with CWM 3.x. That can only be used with Gingerbread (Android 2.3) ROMS like CM7. Install CM7, and you'll be good to go.
Take a look at http://forum.xda-developers.com/showthread.php?t=944681 from TrueBlue_Drew. It's a way of switching between the various versions of CWM. But it won't be useful until you have a working phone.

xXy3kXx said:
oRANGE i flashed it to 3.00005 or what ever
Click to expand...
Click to collapse
If you installed CM 3.x then you need to flash Cyanogen CM7. You'll get a working phone. Don't forget the g/apps either.

i downloaded cm_glacier_full-32.zip and the gapps the phone boots past the splach screen than keeps going through the boot animation

xXy3kXx said:
i downloaded cm_glacier_full-32.zip and the gapps the phone boots past the splach screen than keeps going through the boot animation
Click to expand...
Click to collapse
Try downloading 31, wiping the had set clean, and try a fresh start.

i can get the 32 build to boot with no gaps installed but when i install the gapps thats when i get the boot loop i downloaded gapps-gb-20110120

xXy3kXx said:
i can get the 32 build to boot with no gaps installed but when i install the gapps thats when i get the boot loop i downloaded gapps-gb-20110120
Click to expand...
Click to collapse
thanks for supplying the exact version of the g/apps. Did you by chance check the md5sum? should match 45e175c25a498c8945c543d92d92e782
and are you installing the G/apps pre or post installing the ROM?

Oops I had the wrong gapps file its all good now bro thank you for your time and help I'm very grateful for people like you!! Thanks braa
Sent from my Bubba kush device! ;/

Related

Can't Restart my CM MT3G?

I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Probably because you have a lot of apps?
If not, reflash it.
tmc_adio07 said:
I have flashed the new CyanogenMod and the Cyanogen Recovery 1.4 and when I wipe everything and flash, it'll load up and I can use the phone 100% perfectly, but once I reboot my phone, or turn it off and on, it never goes past the green boot screen. Anyone have any solutions/reasons why it does that? It's with every single Cyanogen mod too, i've tried several of them.
Click to expand...
Click to collapse
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
mt3g said:
what do you actually flash and what is the actual process, you shouldnt have any issues after it boots up the first time, wipe everything and make an exterior partition meaning get rid of your cyanogen recovery 1.4 and get amon ra's latest... look in the dev section and read up on cyan's page on how to flash the rom
Click to expand...
Click to collapse
Thanks for help man, right now I'm running dwang's rom 100% perfect w/ no issues at all. it can reboot and everything just fine. I'm just a little worried on going back and trying to flash cyanogens.
When I installed it, I first did the root process, downloading the .apk file and going through all that part smooth, then I downloaded and flashed the Cyanogen Recovery 1.4, and from there I downloaded the two files (DRC83_base and the latest cyan's rom, i forgot the version #) and applied update from SD, first doing DRC83 and right after doing the rom itself, without rebooting the phone. It loads up A-OK and I can installl the apps and go about my business, but once I need to restart my phone, it just never turns back on. I'm puzzled completely...I even did the whole unroot and reroot thing and STILL i'm not having any luck.
K I got confused in there some where did you flash a cyan rom at all in there I read that you flashed the drc83 zip file but sounds like you just flashed that and booted the phone lol... never tried that but.... any way it seems like you are doing everything correct onlything I could suggest is make sure you have the correct htc base image, and make sure you wipe and repair everything!!!!! and also try a differant download of cyanogen as you might have gotten a bad one or something I have never had any issues with a cyanogen rom except maybe a FC back on 4.0xx or something
兄弟,估计你刷成砖了。同情ing。。

Help! My HTC HD does not startup anymore

I don't knwo where to post this exactly so here it goes.
I installed revolution 2.09 on my rooted HTC HD without any problems.
Run perfectly. Then today I installed a ROM of a theme from this forum as well called media 1.3 with rom manager.
After the reboot my phone only shows a the text android with a slight moving glow over it. It does not repsond to anything any more. I removed the battery but the same thing is happening.
Did I brick it? What can I do?
Willem Kloppenburg said:
I don't knwo where to post this exactly so here it goes.
I installed revolution 2.09 on my rooted HTC HD without any problems.
Run perfectly. Then today I installed a ROM of a theme from this forum as well called media 1.3 with rom manager.
After the reboot my phone only shows a the text android with a slight moving glow over it. It does not repsond to anything any more. I removed the battery but the same thing is happening.
Did I brick it? What can I do?
Click to expand...
Click to collapse
thats just the default android boot screen, looks like the theme messed up your framework... hold on i'll make a .zip you can flash from recovery to fix it
Thanks, but how do I get the zip on the phone? It does not react to anything anymore. I attahced it to my PC but nothing....
Willem Kloppenburg said:
Thanks, but how do I get the zip on the phone? It does not react to anything anymore. I attahced it to my PC but nothing....
Click to expand...
Click to collapse
im just downloading the rom for you now so i can extract the framework, if you pull your battery out, you can either plug in your charger while its off, this will bring up recovery, or while its off, hold vol down and press power, that will take you to bootloader, and just pick recovery from the list, now when in recovery, if you navigate to the mounts and storage menu, choose the option mount usb storage, you can now connect to a pc as a disk drive and copy stuff to your sd card
im having trouble uploading attachments to xda at the min dya want me to upload it to megaupload for you?
AndroHero,
Thank you for helping me out. I didn't know about the vol down press power option which allows you to acces the sd card and intall a new rom. I had the revolution rom 2.0.9 already. It's installing as we speak. Much thanks for the tips!
To early hooray. I choose the option with the revolution zip for a complete install. After the install I selected rebouut system now. Now it stays on the white HTC screen with the text HTC quitely brilliant. Flashing every 3 seconds or so....
What to do now?
Everything is resolved. revolution is up and running again. I had to un the fullwipe.zip and that did it!
THANKS a lot for all the tips....again
Willem Kloppenburg said:
To early hooray. I choose the option with the revolution zip for a complete install. After the install I selected rebouut system now. Now it stays on the white HTC screen with the text HTC quitely brilliant. Flashing every 3 seconds or so....
What to do now?
Click to expand...
Click to collapse
Did you do a full wipe before re-flashing your ROM? even if you did just repeat the process , full wipe /cache, /dalvik-cache, /system and then re-flash the rom fingers crossed it should work
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
mo123456789 said:
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
Click to expand...
Click to collapse
boot into recovery do a full wipe (system, data, cache and dalvik-cache) then re-flash your rom
mo123456789 said:
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
Click to expand...
Click to collapse
Could it be possible that you installed cwm 3005 and tried a restore with that. I had the same problem. Went back to cwm 2.5.x and then restore worked.
Sent from my Desire HD
I think there will be a lot of scare because of this CWM 3x...
Same happened to me the other day, stupidly accecpted the update prompt from Rom Manager, did my backup and went to install Cyanogen 6... Got stuck at HTC logo next boot.
Thankfuly, had Leedroid 2.0 on the SD, too, and that one flashed properly
Thing is that when I try to downgrade the Recovery to 2.5x I get an error and really can't be bothered with ADB pushing stuff around, so using Cyanogen 7 for the time beeing
Anyhow, CWM 3.x is likely your problem, easy to fix ^^
Wanting to change my theme on the Samsung spica I had theexact problem on cyanogen mod. Had to redo the whole rooting and installing the Rom again to get to work.
Sent from my Desire HD using XDA App
yes, is some script...back to recovery 2.x

[Q] CM7 on a HBOOT 1.01 Legend - is it possible??

Okay brief background:
Originally stock VFAU supplied Legend, updated to the stock Froyo. Rooted by (roughly) following the steps outlined in the How to root HBoot 1.01 thread and am now happily able to flash roms using ClockworkMod 3.0.0.6 "fake flash" update.zip
Was keen to try out CM7RC2 on this phone so I have downloaded the update and Gapps .zips from the Cyanogenmod wiki page.
Tried multiple times now to flash the CM7 update and the relevent Gapps, always formatting user data / cache / dalvik before hand. After the process, I am always able to boot into CM7 on the device, but it appears the Gapps update hasn't been applied properly / at all. For example - on initial boot, I don't get the google android setup wizard, so no way to link the phone to my gmail account. Gmail app isn't installed, and when I try to launch Market it just goes to a white screen for a second, and then back to the launcher.
I'm wondering if this is related to the fact that the phone is on HBOOT 1.01, and S-ON? or is there another explaination? eg, a specific kernel, or radio that I should be flashing before I try to flash CM7 (nothing is mentioned in the install guide over at CM wiki).
Thanks in advance.
are you shure ou downloaded the right gapps
the one touse is "gapps-mdpi-20101020-signed"
karlanal said:
are you shure ou downloaded the right gapps
the one touse is "gapps-mdpi-20101020-signed"
Click to expand...
Click to collapse
Hey mate, thanks for the quick reply! Just to clarify - are you sure this is the right version of Gapps for CM7 on the Legend?? Looking here under the "Google Apps Version" section it appears that the correct version for all devices running CM7 should be Gapps-gb-20110307-signed.zip and that gapps-mdpi is for CM6??
I tried your suggestion nontheless, and with that version of Gapps flashed - I'm now getting a boot-loop of the cyanogen boot animation
I'm on HBOOT 1.01 (Vodafone Legend) and CM7 was the first I tried, though it was back around the nightly build 31. I didn't have any issues and CM7 started up straight away. I realised I was missing all the Google stuff so did a separate flash, maybe you could try this. I'm yet to try the RC version hopefully no issues here...
EpicSauce said:
I'm on HBOOT 1.01 (Vodafone Legend) and CM7 was the first I tried, though it was back around the nightly build 31. I didn't have any issues and CM7 started up straight away. I realised I was missing all the Google stuff so did a separate flash, maybe you could try this. I'm yet to try the RC version hopefully no issues here...
Click to expand...
Click to collapse
I have tried flashing the gapps package as a separate flash (after the intial flash to CM7, booting into CM7, then reboot into recovery to flash Gapps), and the result has been the same as when I flash them together.
I had wondered about trying a nightly, but being new to CM roms please forgive my next question. To flash a nightly, do I first have to flash CM7 RC2, then flash the nightly, or can you just flash the nightly by itself, then Gapps over the top??
I'm definitely willing to give it a try at this stage.
Flashing the nightly won't need a prior RC2 flash, its a self contained package so you shouldn't have any problems. Hopefully the Gapps flash works this time.
black beard said:
Hey mate, thanks for the quick reply! Just to clarify - are you sure this is the right version of Gapps for CM7 on the Legend?? Looking here under the "Google Apps Version" section it appears that the correct version for all devices running CM7 should be Gapps-gb-20110307-signed.zip and that gapps-mdpi is for CM6??
I tried your suggestion nontheless, and with that version of Gapps flashed - I'm now getting a boot-loop of the cyanogen boot animation
Click to expand...
Click to collapse
yes i was wrong, gave you the wrong gapps suggestion
i was allways using "gapps-gb-20110120-signed" and all was working great
EpicSauce said:
Flashing the nightly won't need a prior RC2 flash, its a self contained package so you shouldn't have any problems. Hopefully the Gapps flash works this time.
Click to expand...
Click to collapse
Well tried flashing the latest nightly last night, full wipe, then flash, then reboot, then reboot into recovery and flash the Gapps and it worked!! Don't really understand why something like that wouldn't work with the RC
karlanal said:
yes i was wrong, gave you the wrong gapps suggestion
i was allways using "gapps-gb-20110120-signed" and all was working great
Click to expand...
Click to collapse
Thats cool mate - made me recheck myself anyway

[Q] Defy won't go past the boot logo

Good day everyone! I would like to ask for some help if it wouldn't bother.
I previously have WajkIUI 1.10.21 installed on my 2nd init. I have installed the Multiboot plugin (http://forum.xda-developers.com/showthread.php?t=1364659) and installed the CM9 12-2-2012 build on 2nd boot.
However when I updated the 2nd boot to CM9 12-11-2012 build, the 2nd boot stays stuck on the red M logo. Because of that, I installed the "kernel" on 2nd boot which was supposed to boot the build. Unfortunately, it only resulted to a boot loop for my CM9.
When I tried to boot from 2nd init (which still has my WajkIUI), it suddenly stopped booting as well. I tried to recover using my recovery file but to no avail, 2nd init still won't boot.
So my phone's condition now is: it is able to run CWM recovery on both 2nd boot and 2nd init. Will I still be able to boot my 2nd init? Will I still be able to restore to my latest recovery file? If yes, can anyone guide me on how to fix my 2nd init boot?
Thank you very much everyone!
I think its mentioned in the defy cm9 thread.
Its not possible to flash any newer version including 111207 in second Boot.
i think i made the same mistake too...
but i dont know wether i had to reinstal primary boot...
you could try to flash miui on primary boot so that you can do atleast anything...
if you want cm9:
wipe everything
instal cm9 111207.zip
instal cm9 111213.zip
im using cm9 and everything is great, except camera, wich in fact isnt working at all
hope it helped, greetz esok
esok44 said:
I think its mentioned in the defy cm9 thread.
Its not possible to flash any newer version including 111207 in second Boot.
i think i made the same mistake too...
but i dont know wether i had to reinstal primary boot...
you could try to flash miui on primary boot so that you can do atleast anything...
if you want cm9:
wipe everything
instal cm9 111207.zip
instal cm9 111213.zip
im using cm9 and everything is great, except camera, wich in fact isnt working at all
hope it helped, greetz esok
Click to expand...
Click to collapse
Thanks! Now I'm running the Dec13 build
I guess it's about the kernel which messed up. Motorola is so *** for locking the bootloader.
Anyway, thanks again! I'll try to install multi boot again and install Wajkiui on 2ndboot )
arvs0z said:
Thanks! Now I'm running the Dec13 build
I guess it's about the kernel which messed up. Motorola is so *** for locking the bootloader.
Anyway, thanks again! I'll try to install multi boot again and install Wajkiui on 2ndboot )
Click to expand...
Click to collapse
Think this doesn't work either, because of the Kernelchange
but maybe you could post the result of this test.
Would like to install cm7 as second boot, cause of the camera and all my old data
esok44 said:
Think this doesn't work either, because of the Kernelchange
but maybe you could post the result of this test.
Would like to install cm7 as second boot, cause of the camera and all my old data
Click to expand...
Click to collapse
Yes, apparently installing a 2.2 based rom on the virtual system doesn't work (won't get past the M logo again) even when I apply the 2.2 kernel on the virtual system.
So I guess we're stuck on manually choosing our main rom. I also have my data on my older rom (not to mention, app highscores, etc) and I miss my defy's camera, but the ICS rom is so hard to resist.
arvs0z said:
Yes, apparently installing a 2.2 based rom on the virtual system doesn't work (won't get past the M logo again) even when I apply the 2.2 kernel on the virtual system.
So I guess we're stuck on manually choosing our main rom. I also have my data on my older rom (not to mention, app highscores, etc) and I miss my defy's camera, but the ICS rom is so hard to resist.
Click to expand...
Click to collapse
Yeah it is....
AHHHHH damn it.
hmmmm well nevermind, think i will stay with ICS...
titanium backup works, so maybe as a tip for you:
install old rom,
make backup,
install ics,
restore backup,
some data may be back
Yes, I tried that before but for some reason, during restore, Ti force closes on my ICS.
Anyway, I'm fine without my old data for now Thanks Esok
same issue here
did wipe data and cache
install from sd
selected CM7.zip
finding update package
opening update package
opening update package
installing update
done
cynogen mod splashscreen appeared
waited for 20 minutes..and still at splashscreen
what to do ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
any help ?
die2mrw007 said:
same issue here
did wipe data and cache
install from sd
selected CM7.zip
finding update package
opening update package
opening update package
installing update
done
cynogen mod splashscreen appeared
waited for 20 minutes..and still at splashscreen
what to do ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
any help ?
Click to expand...
Click to collapse
try removing the battery. then put it back in and power up. see if it boots up. depending on which cm7 rom you were using, there's a known "stuck in boot" problem and removing battery method will overcome it.
^ Yes, try removing the battery and restarting the phone. One other solution could be applying the 2.2 Kernel after the installation of CM7 (only if you are using Defy and the base ROM of CM7 is 2.2) because I tried installing a CM7 nightly and had to apply the kernel
Kernal
I have a Defy I tried flashing to a few different versions of CM7, but it keeps stopping on the boot logo. I tried flashing from stock, so do I have to change my kernal? If so, how?
phatboyjr said:
I have a Defy I tried flashing to a few different versions of CM7, but it keeps stopping on the boot logo. I tried flashing from stock, so do I have to change my kernal? If so, how?
Click to expand...
Click to collapse
are you saying you were still on stock rom and you tried to install cm7? what was your stock rom and have you flashed any full sbf? what were the steps you did to install cm7?
Yeah, I was running the stock 2.2 and tried installing CM7.
I rooted my phone, then installed 2ndinit boot loader. Wiped caches/factory reset and used CWM to install from a .zip file on the SD card.
No idea how to set up RSDLite..
to install CM7 follow the steps in this faq :
http://forum.xda-developers.com/showthread.php?t=1065798
phatboyjr said:
Yeah, I was running the stock 2.2 and tried installing CM7.
I rooted my phone, then installed 2ndinit boot loader. Wiped caches/factory reset and used CWM to install from a .zip file on the SD card.
No idea how to set up RSDLite..
Click to expand...
Click to collapse
so far so good. could be the rom you were flashing. were you trying to flash the nightlies by any chance? all the latest nightlies do not come with the kernel. you either have to flash the stable release first, or the cm7-kernel-signed.zip, inorder to have the correct kernel before you can flash the nightlies.
do not flash any full gb sbf or you can get yourself in trouble.

ICS ROM- Doesn't get past animated boot logo

I just installed the Energy CM9 rom onto my fire. It starts to boot but never gets past the animated loading screen. I have also tried the same thing with the Hash COde ICS Rom. Any ideas?
micromarty said:
I just installed the Energy CM9 rom onto my fire. It starts to boot but never gets past the animated loading screen. I have also tried the same thing with the Hash COde ICS Rom. Any ideas?
Click to expand...
Click to collapse
What Rom did you come from? Did you wipe cache, dalvik cache, factory data reset, and system? Did you check the MD5 for the zip?
micromarty said:
I just installed the Energy CM9 rom onto my fire. It starts to boot but never gets past the animated loading screen. I have also tried the same thing with the Hash COde ICS Rom. Any ideas?
Click to expand...
Click to collapse
I second this. I'm using the CWM-based recovery. Is there any way to get into recovery before the CM9 boot starts?
geokhentix said:
I second this. I'm using the CWM-based recovery. Is there any way to get into recovery before the CM9 boot starts?
Click to expand...
Click to collapse
I would assume you press and hold power button at firefirefire boot screen until it turns from green to orange, which will load recovery. That's the way it works with twrp.
Sent from my Kindle Fire using xda premium
micromarty said:
I just installed the Energy CM9 rom onto my fire. It starts to boot but never gets past the animated loading screen. I have also tried the same thing with the Hash COde ICS Rom. Any ideas?
Click to expand...
Click to collapse
Did you try the original CM9 ROM from http://forum.xda-developers.com/showthread.php?t=1411895 ?
Please make sure to do a "factory reset" on CWM if you switch between ROMs.
nind said:
Did you try the original CM9 ROM from http://forum.xda-developers.com/showthread.php?t=1411895 ?
Please make sure to do a "factory reset" on CWM if you switch between ROMs.
Click to expand...
Click to collapse
I did and it took forever to boot but it worked.
micromarty said:
I did and it took forever to boot but it worked.
Click to expand...
Click to collapse
That's usual for the first boot, it should be very much faster on the next boots.
I had this happen when I installed the ICS Energy rom. I wiped my KF back to stock and flashed the rom back onto the KF. I let it sit on the boot animation for maybe a minute or two and it came back up.
I guess on the initial boot you gotta be patient haha

Categories

Resources