Develop Bugs

tmobile g2 wont boot

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.

Aborted flash of all roms

Hi all. Im having a strange problem with flashing roms. I am not new to this and have been problem free for a while. I went from fresh 3.4 to myns rls4. Then went to fresh 3.5 and tried to go back to myn from there. I use clockworkmod and recently updated to 3.0.0.0. I have tried flashing the roms in rom manager and by booting up in recovery. I was able to load a backup and am currently set up as follows:
unrevoked forever (used 3.21 before reading forever might fix this issue)
fresh 3.4
netarchy kernel
bootloader screen
supersonic evt3 ship s-off
hboot-0.97.0000
micro-041f
touch panel-atmelc03_16ac
radio-2.15.00.09.01
Heres what it says when I try to install any rom. All roms do and say the same thing.
clockworkmod recovery v3.0.0.0
installing
finding update package
opening update package
installing update...
installation aborted.
This is from flashing while in recovery using volume down and power button method. Any advice?

Wrong place to post.
Sent from my PC36100 using XDA App

joedesu1 said:
Hi all. Im having a strange problem with flashing roms. I am not new to this and have been problem free for a while. I went from fresh 3.4 to myns rls4. Then went to fresh 3.5 and tried to go back to myn from there. I use clockworkmod and recently updated to 3.0.0.0. I have tried flashing the roms in rom manager and by booting up in recovery. I was able to load a backup and am currently set up as follows:
unrevoked forever (used 3.21 before reading forever might fix this issue)
fresh 3.4
netarchy kernel
bootloader screen
supersonic evt3 ship s-off
hboot-0.97.0000
micro-041f
touch panel-atmelc03_16ac
radio-2.15.00.09.01
Heres what it says when I try to install any rom. All roms do and say the same thing.
clockworkmod recovery v3.0.0.0
installing
finding update package
opening update package
installing update...
installation aborted.
This is from flashing while in recovery using volume down and power button method. Any advice?
Click to expand...
Click to collapse
i think that clockwork 3.0 is causing problems

At OP: I Clockwork 3.0 appears to have some bugs. Hold on tight.
@aimbdd: You're not a mod, nor did you help at all (in answering the question or telling him what you did). You're actually FAR worse than he is. If you're not going to post something productive, please don't post.
On that note, this question should be in the Q&A section for future reference

aimbdd said:
Wrong place to post.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I apologize for my ignorance on the matter but I agree with the above statement that it takes more/equal time to respond like this then it would to direct me in a productive place. Ill be more careful next time

How can i delete this thread?

I had to switch to RA to flash a new rom. I couldn't even downgrade to the clockwork recovery to 2.5. I was having the same problems as OP with Clockwork 3.0.0.0.
Sent from my PC36100 using Tapatalk

david11c said:
I had to switch to RA to flash a new rom. I couldn't even downgrade to the clockwork recovery to 2.5. I was having the same problems as OP with Clockwork 3.0.0.0.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I had to do the same. I'm using RA as a result

Reading clockworkmods tweets it appears the new clockwork is only for the new hboot and doesn't work with the older hboots. Install amon ra 1.8 and you should be golden. You won't be able to use rom manager after you install aman ra.

[Q] lost...after attempted rooting, stuck

Hi everyone... I have been doing a bit of searching with no luck so far. And I searched a lot but no luck in finding my stituation and don't want to screw up the phone completely...
I bought a D-Z used, Bell Rom. It showed to be S-Off, but when i checked to see if it was rooted with RootCheck, it said it wasn't. So I started the process of applying Visionary for Temprooting and then on terminal emulator, I got the error: exec format error...and, stupid me, decided to keep going. I followed the rest of the process, up to step 10 on http://theunlockr.com/2010/11/30/how...g2-htc-vision/.
But when i turned phone back on, it got stuck on the white screen with the green htc logo....
If I vol-down/turn on, i see:
Vision PVT ENG S-OFF
HBOOT-076.2000 (PC1012000)
MICROP-0425
RADIO-26.03.20.26_M
eMMC-boot
Aug 20 2010,16:51:01
HBOOT and the options:
FASTBOOT, RECOVERY, FACTORY RESET, SIMLOCK, SYSTEM INFO, IMAGE CRC
On system info it says
OS Ver.-1.34.666.5
When I put the battery in it, plugged into charger, it goes into ClockworkMod Recovery v3.0.0.5 and below the menu it says:
ClockworkRecovery v3.0.0.5
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
the phone says S-off: should I just copy some rom and launch the flashing? If so, a zip to the SD card is the way to go, right?
Or is something bad and should I attempt first loading a stock rom? (I guess not, because it says S-Off!).

It sounds like whatever you did in your rooting process wiped your system, causing the phone to be stuck at the htc screen. So yes, put a ROM zip on your sd card and try to flash it. I would wipe system before you do though. Again, it sounds like the systems already wiped, but it won't hurt anything to wipe again.
On another note, I don't know what the unlockr root process is, but afaik, the recommended rooting method is to stay away from Visionary and use the Gfree method in the G2 wiki. It's much safer than Visionary.
Sent from my HTC Vision using XDA Premium App

heybobitsme said:
It sounds like whatever you did in your rooting process wiped your system, causing the phone to be stuck at the htc screen. So yes, put a ROM zip on your sd card and try to flash it. I would wipe system before you do though. Again, it sounds like the systems already wiped, but it won't hurt anything to wipe again.
On another note, I don't know what the unlockr root process is, but afaik, the recommended rooting method is to stay away from Visionary and use the Gfree method in the G2 wiki. It's much safer than Visionary.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
What would you suggest? Any custom Rom as zip should do then? Any potential damage/ risk of bricking?
thanks!

santiargy said:
What would you suggest? Any custom Rom as zip should do then? Any potential damage/ risk of bricking?
thanks!
Click to expand...
Click to collapse
lucky you! - someone before you S-OFFed the phone!

read the stikies next time. http://forum.xda-developers.com/showthread.php?t=1025135

santiargy said:
What would you suggest? Any custom Rom as zip should do then? Any potential damage/ risk of bricking?
thanks!
Click to expand...
Click to collapse
first, download any untouched flashable sense rom (make sure it's not a full rom with hboot, radio etc, just /system)
place the rom.zip on your sd card
reboot with vol down
choose recovery
wipe cache and wipe data/factory reset
choose install zip form sd (not update), then select the zip and press trackpad
hopefully this is all you will have to do to make the phone functional again

here is a flashable rooted /system from a stock sense rom: http://forum.xda-developers.com/showthread.php?t=1012763
hope this will help

petarpLab said:
lucky you! - someone before you S-OFFed the phone!
Click to expand...
Click to collapse
thanks for you help. I'm trying it now.
I had tried the other method... but it didn't work out. I should have read more before going for what looked simpler - visionary.
I will report soon. Hopefully, i will have a phone and not a piece of wall...

THANK YOU!!!!! IT WORKED PERFECTLY. I GUESS I CAN NOW GO TO Cyanogen, right?

santiargy said:
at this point, I don't want to screw up anymore...
wipe cache, ok
wipe system? Not an option... got wipe data/factory reset. is that the option? you refer to?
Click to expand...
Click to collapse
yes, do this one.
p.s. sorry for the rant earlier.

Hmm.. maybe try this rom?
HTML:
http://forum.xda-developers.com/showthread.php?t=1074391
Someone on that thread mentioned fixing a bricked(or almost) phone with it..

Mkarin said:
Hmm.. maybe try this rom?
HTML:
http://forum.xda-developers.com/showthread.php?t=1074391
Someone on that thread mentioned fixing a bricked(or almost) phone with it..
Click to expand...
Click to collapse
this is a G2 rom, not DZ. it's dangerous to mix them if we are talking about full stock roms. bricks happen from such mixes.

santiargy, any success?
ah, i mised a post.
I am really glad to hear it worked.

[Q] Oddities after reverting to stock.

So, after a bunch of shenanigans involving Clockworkmod errors and busted wifi, I decided to revert my incredible back to stock from Cyanogenmod by flashing the PB31IMG.zip through hboot. Prior to this, I had tried to flash a fresh install of Cyanogenmod, which didn't fix my problems and produced errors in CWM along the lines of:
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
A quick search revealed that these errors pretty much rendered CWM useless for flashing, wiping, etc. so I didn't bother trying and just flashed the stock HTC rom.
The phone is working swimmingly so far, but I've noticed some oddities that I thought I should get sorted out before possibly going to another rom.
Booting into hboot reveals that I still have s-off. Shouldn't flashing the stock image give me s-on?
Booting into revocery gives me an image of a phone with a red triangle/exclamation mark. What does this mean?
Before I found these issues I was planning to run unrevoked to flash CWM and root again, but now I'm hesitant. Any help would be excellent.
PS. Here is a thread detailing the CWM issues I had prior to this, if that helps anyone.

Sounds like the stock Android recovery. You'll need to get a recovery from Doug Piston.com that you can flash the same way you just flashed the stock Inc image.
Sent from my ADR6300 using xda premium

So I could flash CWM through hboot without a problem? That sounds great, but I still have the s-off issue. I found that I have s-off, but I don't have root access. As far as I can tell, I think need to rerun unrevoked, is that right? Can I run it safely even though I already have s-off? It looks as though unrevoked forever has an s-on tool that I can flash through recovery-should I do that before running unrevoked?
UPDATE: I got a little impatient and took matters into my own hands. I managed to get Cyanogen up and running, and I'll list what I did for anyone with similar concerns. Thank you for the advice, RMarkwald.
1. Flashed CWM 3.0.0.8 through hboot (because 5.0.2.0 is what got me into this whole mess...)
2. Flashed Superuser through recovery (apparently s-off and root access are two different things. I had to flash superuser to gain root access.)
3. Rebooted into recovery, did a factory reset, wiped cache and dalvik cache.
4. Flashed Cyanogenmod, google apps, incredikernel, and superuser through recovery.

Why do my rom's not install properly? Stuck on HTC screen

I tried installing the Sense Bliss and CM7 ROMs and the Bliss just boots back into the CWM after a failed boot and when I try to install CM7, it just hangs at the HTC screen. I did everything perfect. S-off, rooted and wiped the data, the cache and the dalvchk thing in that order. What am I doing wrong?
Also, when I try to go into bootloader, it doesn't let me scroll up or down and immediately tries to install the hboot IMG10 or whatever and trying to make it turn into S-ON again. I don't know how to stop it either.

I think that you have to install the desire z h boot to flash sense roms and for cm7 check the md5 sums of every file maybe that the problem
Stewie just said that!

monkey hung said:
I tried installing the Sense Bliss and CM7 ROMs and the Bliss just boots back into the CWM after a failed boot and when I try to install CM7, it just hangs at the HTC screen. I did everything perfect. S-off, rooted and wiped the data, the cache and the dalvchk thing in that order. What am I doing wrong?
Also, when I try to go into bootloader, it doesn't let me scroll up or down and immediately tries to install the hboot IMG10 or whatever and trying to make it turn into S-ON again. I don't know how to stop it either.
Click to expand...
Click to collapse
The PCIMG10 issue is that you you have that file on the root of you SDcard and the bootloader is designed to check for that. Your other issue is either the DesireZ Hboot mentioned earlier or you're running ClockworkMod Recovery v5, which is buggy as hell; if you have CWM v5 installed, downgrade to v3.
Sent from my HTC Vision using XDA App

First off, delete the PC10IMG.zip off of the sdcard to stop hboot wanting to reflash it.
Then you should probably check your phone partitions or something, maybe try reformat them in recovery, or flash a superwipe zip.
-Nipqer

Alright I'll give these a try and report here afterwards. Thanks!

hehe THANJS

It works! Thank you all!