tmobile g2 wont boot - G2 and Desire Z Q&A, Help & Troubleshooting

hi to all my phone wont boot up when it was working i had rom cm nightly 50 installed and kernel baconbits 0.3 vision installed it work fine until i had a factory reset then the phone got stuck into HTC i took the battery out then hold down vol down and power tried to go into cw recovery v2.5.1.3 it says E:cant mount CACHE:recovery/command E:cant mount CACHE:recovery/log E:cant open CACHE:recovery/log
can someone please help me ty

After it prints those things on the screen can you still use clockworkmod?
Sent from my T-Mobile G2 running Cyanogenmod.

no it goes to a black screen then i hit power button then it goes back to cw recovery with the errors

Sorry to be redundant but when it goes back to cwr can you at that point preform a recovery? Or do a factory reset maybe?
Also you dont need baconbits when you install cm. Baconbits was kind of a sample kernel before cm was released.
Sent from my HTC Vision using XDA App

whouwit510 said:
hi to all my phone wont boot up when it was working i had rom cm nightly 50 installed and kernel baconbits 0.3 vision installed
Click to expand...
Click to collapse
If you've got Cyanogen installed, then you shouldn't be trying to use Baconbits on top. Baconbits is designed to be used on top of the stock ROM, to give you some of the CM functionality.
Edit - oops, sorry, didn't notice the previous poster already said that.

Exactly. From what I've seen trying to use baconbits on top of cyanogenmod is a very dangerous and unstable combination.
Sent from my T-Mobile G2 running Cyanogenmod.

Related

[Q] Won't boot after changing ROMS.

I was running Gingervillain 1.4 but wanted to try CM 6.1.1 with a theme I saw on a different forum. I used CW to flash to the CM rom and did nandroid backup and wipe before installing.
While installing the CM rom, it got to the end and gave me this:
e:can't open /cache/recovery/log
e:can't open /cache/recovery/log
e:can't open /cache/recovery/last_log
e:can't open /cache/recovery/last_log
I had a good recovery of my stock rom and tried to flash that, but it gave me the same error. If I tell CW to reboot system, it hangs on the HTC screen. I am able to get into hboot/recovery via Vol Down/Power and have tried wipe cache, wipe devlik cache, and even the wipe/factory reset and then it went past the HTC screen to the Tmobile G2 screen, but boot-looped on that screen.
After Vol Down/Power, this is my info:
Vision PVT ENG S-OFF
HBOOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.03.02.26.M
eMMC-boot
Aug 20 2010, 16:51:01
I read a few threads, and this one stuck out:
http://forum.xda-developers.com/showthread.php?t=842495
However, the links are now dead
I haven't used ADB, but I have it downloaded and installed since I figured I would need it.
What version of recovery are you using?? Also have you tried flashing latest cm7?? And get same errors
Im am using the latest CW mod. Like 3.0.5 or something. I havent tried CM7. Should I?
Yes try cm7 a try and see if you get same error
The latest recoveries 3..... are for 2.3 roms only. To go back to 2.2 you need one of the older ones again, the 2.9.... recoveries.
Sent from my HTC Vision using XDA App
wileykat said:
The latest recoveries 3..... are for 2.3 roms only. To go back to 2.2 you need one of the older ones again, the 2.9.... recoveries.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yea what he said...I just wasn't sure what vz your other rom is/was.. but 2.2 roms need recoveris 2.XX and any rom that is 2.3+ need recovery 3.xx
Ok, i downloaded CM7 and gapps and am going to try those. I wonder why I was able to go back to my stock rom before...maybe just got lucky I guess.
i will post back in a few minutes and say whether it worked or not.
Ok, I downloaded CM7 and gapps to my computer, and turned the phone on to get into recovery. enable USB storage and transferred CM7's zip and gapps zip to my sd card. So far so good, CM7 is up and running... So if I ever want to go back to a Froyo rom, I just need to have a CW that is 2.xx, correct?
Indeed my friend, that is correct.
Sent from my HTC Vision using XDA App
wait what? the new recovery should let you flash 2.2 and 2.3 correct?

Stuck at boot screen, help please

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

Can't flash a new rom

Hi all
can't flash my desire hd anymore
and the phone boot only to the recovery.
after a full wipe,i try to flash a new rom, up to 80% and the progress bar does not move.... meaning that the flash does not complete:-(
my phone is s-off and root
I flashed different rom before and all worked
could someone help me please?
thx in advanced
Hi bassjam
bassjam said:
Hi all
can't flash my desire hd anymore
and the phone boot only to the recovery.
after a full wipe,i try to flash a new rom, up to 80% and the progress bar does not move.... meaning that the flash does not complete:-(
my phone is s-off and root
I flashed different rom before and all worked
could someone help me please?
thx in advanced
Click to expand...
Click to collapse
What Rom is it you are trying to install?
Is there any error message showing when it stops?
At a guess It sounds as if you are trying to install a Corrupt Rom, you need to check the MD5 Checksum that come with the Rom to make sure they are not corrupt on download, before you try to install them.
What you need to do is download the Rom again, check it's Checksum With this MD5 Check 2.1 tool.
Then delete the bad Rom that on your SD Card, and replace with the new download [Checked with MD5 Check] Rom, and flash it.
Take Care
TheQuest
Agree with I'm TheQuest. That's maybe because of bad download. redownload back the rom and put back to your SD card. Do the nandroid restore (but if you dont have nandroid backup before, this also can be done by taking out your sdcard and put into your laptop/card reader).
Thx for your answers
The problem appeared with the cynanogen RC4
this rom was installed since a week and i was on RC3 before
one day, I powered off the phone, then powered it on, and the phone boot only to the recovery.
I tried to flash the last leedroid but nothing
After that I knew it was not from the cyanogen rom.
For the moment, to solve the problem, i flashed (on bootloader) the last official WWE ruu(1.72), flash ok but the phone was very very sloooowwww
especially to install the sence, after unlocking simcard, I have a white screen with htc logo during 20 min. and only after that, I can start the configuration.
so i decided to back to ruu 1.32 to root / S-off the phone again
After that I try to install the cyanogen rom again
What do you think about that?
Hi bassjam
bassjam said:
Thx for your answers
The problem appeared with the cynanogen RC4
this rom was installed since a week and i was on RC3 before
one day, I powered off the phone, then powered it on, and the phone boot only to the recovery.
I tried to flash the last leedroid but nothing
After that I knew it was not from the cyanogen rom.
For the moment, to solve the problem, i flashed (on bootloader) the last official WWE ruu(1.72), flash ok but the phone was very very sloooowwww
especially to install the sence, after unlocking simcard, I have a white screen with htc logo during 20 min. and only after that, I can start the configuration.
so i decided to back to ruu 1.32 to root / S-off the phone again
After that I try to install the cyanogen rom again
What do you think about that?
Click to expand...
Click to collapse
If you Change ROM's you are always advised to do a FULL WIPE.
Moving to Cynanogen RC4 from RC3 should not have caused your problem, but even when Updating a Rom you are advised to wipe the Cache Partition and the Dalvik Cache
Take Care
TheQuest
My problem is not yet resolved
actually I download rommanager to get the recovery
my phone is so slooooowwwwwww...
after that I will try to flash new rom with a full wipe before ;-)
if it doesn't work --> the phone will go on "after sales service" :-(
Hi bassjam
bassjam said:
My problem is not yet resolved
actually I download rommanager to get the recovery
my phone is so slooooowwwwwww...
after that I will try to flash new rom with a full wipe before ;-)
if it doesn't work --> the phone will go on "after sales service" :-(
Click to expand...
Click to collapse
Yes do a full wipe, it should help with the speed, good luck.
Let us know how you get on please?
Take Care
TheQuest
is the first time such a problem that happens
I had a htc magic, hero, desire and windows mobile phone before
with each phone, I had at less similar problem
for the first time, I wonder if this is not a hardware problem like writing speed of the processor...
for the moment i finished radio s-off, eng-off, and i put the recovery with fastboot( problem to get recovery with rom manager)
It's time to full wipe, about 30 minutes to wait if not more...
edit: full wipe ok after 15 min, i'm going to wipe with fastboot to be sur!?
redit edit: flash the phone with cyanogen rc4...
thx
something in recvory or perhaps on i didn't see it before
I actually use CWM 2.5.1.2
i have in the recovery screen:
E: can't mount CACHE: recovery/command
E: can't mount CACHE: recovery/log
E: can't open CACHE: recovery/log
Could someone explain me what does it mean?
thx
Hi bassjam
bassjam said:
something in recvory or perhaps on i didn't see it before
I actually use CWM 2.5.1.2
i have in the recovery screen:
E: can't mount CACHE: recovery/command
E: can't mount CACHE: recovery/log
E: can't open CACHE: recovery/log
Could someone explain me what does it mean?
thx
Click to expand...
Click to collapse
You should try to updating CWM to 3.0.0.6, and that should clear that. [hopefully ]
Take Care
TheQuest
amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
For those who have the same problem, read the previous post ;-)
Hi bassjam
bassjam said:
amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
Click to expand...
Click to collapse
Glad to hear you have managed to get it fixed.
Take Care
TheQuest
bassjam said:
amazing!! it works!
flashed leedroid rom with CWM 2.5.1.2 and all is ok( it was impossible to flash cyano with this recovery)
i can now upgrade to cwm 3.0.0.6 and flash cyanogen rc4
very big thx
For those who have the same problem, read the previous post ;-)
Click to expand...
Click to collapse
Yes CWM 2.x can't write the ext4 partitions required by Gingerbread so you require cwm 3.x, you could have flashed this from Fastboot without first flashing a new ROM. If you didn't have CWM 3.x in the first place this was probably the source of your problems.
I don't believe it!
phone works during 5 five with cyanogen rom, I put the wifi on, and then bootloop( recognized problem on RC4)
i pull out the battery then restart the phone, and the phone has not started and the stay blocked to htc logo
PB: I have no recovery, impossible to to flash another rom. When I launch recovery, phone blocked on htc screen!
I tried to flash ruu 1.32 or 1.72 on fastboot mode... but phone still blocked on htc screen...
I don't know what to do
pls help
thx

[Q] Really need help....phone will not boot

Ok....search and cant figure it out....Been working on this for two days now......Wife has a g2 and I had to downgrade to root....I did that and everything seemed fine....I then Rooted phone and everything there seemed to be fine....I tgen wanted to download Virtuous Affinity rom but it said I had to DZ hboot...here is where i messed up.......I had made a backup of the stock rom yesterday so I put the PC10img on the root of sd card..rebooted into hboot and ran update by pressing volume up....after everything was done I went back into recovery and went to reload back-up of rom and all clockwork does is show reboot system ,apply update etc and down at bottom says E: cant mount/ cache/recovery/ command........etc
now I understand I dont have a rom after the flash but now I can put any on because when I hit any of the install from sd or back up and restore it goes to that page and just sits there.........I am so lost know and dont know what to do...can someone please help me
You probaby flashed the wrong pc10img file...check the md5 sum against that oof the file...another thing is you can try a higher recovery becuasue I remember when u flash a hboot it replaces the recovery...try flashing the latest version of clockwork via adb...if not that refer to the devs
Sent from my HTC Vision using xda premium
Did you use the power button to try reload the rom from recovery? Cause that might be your problem.
Use the trackpad or camera button in recovery.
-Nipqer
Sent from my HTC Vision using xda premium
yes...its not letting me do anything...so frustrating....should i just try to find a new pc image and flash it like a update
sluggersix said:
yes...its not letting me do anything...so frustrating....should i just try to find a new pc image and flash it like a update
Click to expand...
Click to collapse
Don't flash any image that don't belong to the g2
Sent from my HTC Vision using xda premium
sluggersix said:
Ok....search and cant figure it out....Been working on this for two days now......Wife has a g2 and I had to downgrade to root....I did that and everything seemed fine....I then Rooted phone and everything there seemed to be fine....I tgen wanted to download Virtuous Affinity rom but it said I had to DZ hboot...here is where i messed up.......I had made a backup of the stock rom yesterday so I put the PC10img on the root of sd card..rebooted into hboot and ran update by pressing volume up....after everything was done I went back into recovery and went to reload back-up of rom and all clockwork does is show reboot system ,apply update etc and down at bottom says E: cant mount/ cache/recovery/ command........etc
now I understand I dont have a rom after the flash but now I can put any on because when I hit any of the install from sd or back up and restore it goes to that page and just sits there.........I am so lost know and dont know what to do...can someone please help me
Click to expand...
Click to collapse
I believe those errors are "normal" after switching hboots... were you following this guide here: http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html?
If you haven't read it, it might help...
Ditamae said:
I believe those errors are "normal" after switching hboots... were you following this guide here: http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html?
If you haven't read it, it might help...
Click to expand...
Click to collapse
I understand the errors down at bottom is normal....but the day before I backed up rom so I didnt do that when it came to that in the directions......so now when I try to do anything in clockwork everything is there but when I try say restore rom or install from sd....once you click on it it stops......and phone will not load because there isnt a rom installed anymore
Maybe you could try flashing a different recovery image to your phone via fastboot. Perhaps try flashing 4EXT Recovery by madmaxx82. Then reboot into recovery via fastboot and see if it'll let you restore or flash a ROM. Just a thought...
Sent from my HTC Vision using XDA App

custom MTD partition, Nandroid and CWM problem

Hey Guys,
sorry for creating a new thread but I am at a loss right now.
I followed the instructions in this post:
http://forum.xda-developers.com/showthread.php?t=1233340
at the point (in step 2)
Once this is done, do NOT reboot. Go to Advanced Again and select Reboot Recovery
Click to expand...
Click to collapse
i got a problem! I started clockworkmod recovery v2.5.0.2 (pretty sure about that)out of rom manager and did all above the mentioned point. step by step. but after flashing the bravo-recovery-v1.5.3-CustomMTD.zip, my display just went black. light on but black. sorry for my bad english - hope u guys know what I mean. ^^ no matter if I pressed the ok button or the P-OFF of my wildfire.
after taking out the battery I only was able to boot in recovery mod version 2.5.0.1
I thought i just go on with the next step -
Once Clockworkmod Recovery Reboots, Restore your previously taken nandroid backup
Click to expand...
Click to collapse
but here i get the error: error while restoring /system/!
what can I do? I think the version of the recovery is the problem!? while making the nandroid backup no errors occurred!
please help me I need this nasty phone
When you are trying to create custom partitions, do not boot into recovery from ROM Manager. (ROM Manager uses Temporary ZIP recoveries which cannot be modded. I should have added this to that guide :/).
Power off your phone, start in HBoot, navigate to RECOVERY, and use this Clockworkmod to create Custom MTD partitions. For now, to get your phone in working order, just flash any ROM temporarily. Then try again. Use the same version of CWM to restore as you did when creating the backup.
Also, are you sure it is 2.5.0.2? AFAIK, there isn't a version like that.
3xeno said:
Also, are you sure it is 2.5.0.2? AFAIK, there isn't a version like that.
Click to expand...
Click to collapse
Lol, maybe he means 5.0.2.0?
To OP, try flashing a PC49IMG.zip of Clockworkmod Recovery 5.0.2.0, and try again.
Sent from my Wildfire using Tapatalk 2 Beta-5
thanks guys got the same idea later on time. long night indeed.
Yes i meant this version sry - as mentioned, laaate night ^^ no power after 3 days of bootloops (because of supercharger script, LOVE IT!! and have to beat the odds)and I dont wonder - same thing today. fresh rom, got the gapps on it, V6_SuperCharger_for_Android-Update9_RC8.1 and then bootloop bootloop.
A few hours earlier, I intuitionally did as you wrote in the post above. BTW when the wildfire has about 300mb internal space - your mtd guide worked ain't it!? ^^
... so i flashed CM update-cm-7.2.0-RC1, via the installed CWM v2.5.0.1
everything fine until now because I do whole thing again. Your custom MTD Partition guide first, then installing update-cm-7.2.0-RC1 (is it possible to update to a stable version, when its finished, out from that?) or better a stable or nightly build? Lastly I try to supercharge my mobile again. The wildfire is definitly in need of this oom fixings. (I think the built-in kernel tweaks make my buzz unhappy...) THIS SCRIPT IS GREAT NEED NEED NEED haha.
\\edit:
Right now I try flashing clockworkmod recovery v5.0.2.0 via the old version. Sometimes when I am in the recovery I get a black screen after selecting a menueitem. Then I press P-OFF and get back to the superior menue - it does not work this way everytime. Every second time I stuck on the black screen. Problems problems everywhere
scarfur said:
thanks guys got the same idea later on time. long night indeed.
Yes i meant this version sry - as mentioned, laaate night ^^ no power after 3 days of bootloops (because of supercharger script, LOVE IT!! and have to beat the odds)and I dont wonder - same thing today. fresh rom, got the gapps on it, V6_SuperCharger_for_Android-Update9_RC8.1 and then bootloop bootloop.
A few hours earlier, I intuitionally did as you wrote in the post above. BTW when the wildfire has about 300mb internal space - your mtd guide worked ain't it!? ^^
... so i flashed CM update-cm-7.2.0-RC1, via the installed CWM v2.5.0.1
everything fine until now because I do whole thing again. Your custom MTD Partition guide first, then installing update-cm-7.2.0-RC1 (is it possible to update to a stable version, when its finished, out from that?) or better a stable or nightly build? Lastly I try to supercharge my mobile again. The wildfire is definitly in need of this oom fixings. (I think the built-in kernel tweaks make my buzz unhappy...) THIS SCRIPT IS GREAT NEED NEED NEED haha.
Click to expand...
Click to collapse
Good to know. Welcome to the Wildfire
Thanks if I helped
\\edit:
Right now I try flashing clockworkmod recovery v5.0.2.0 via the old version. Sometimes when I am in the recovery I get a black screen after selecting a menueitem. Then I press P-OFF and get back to the superior menue - it does not work this way everytime. Every second time I stuck on the black screen. Problems problems everywhere
Click to expand...
Click to collapse
I am S-OFF but didn't wanted to update the recovery right now. getting impatient. So I did exactly the same as the last time (described above. black screens in recovery - or hopping to steps like "apply this zip?" even if i didn't selected one, then I press the P-OFF button and selected the zip.)
Somehow everything works -.-
Now I've my second try in CM 7.2 RC1
I doesn't rly have the heart to try the supercharger script again - want to prevent stucking in bootscreen. What should I do?
Nandroid backup, run the script, if bootloop then restore (flashing the bravo-boot file after restore to get your partitions back as always). Thats what i did last time, and didn't try the script again. Too bored of bootloops.
Sent from my HTC Wildfire using Tapatalk 2 Beta-5
yes, god save the nandroid backup!
Second try - suddenly everything worked fine for me, thanks to everyone
can be closed
greetz

Categories

Resources