Related
I rooted my hero and tried out a few roms but non seem to polished yet so was wanting to finda stock rom while keeping root of course, Id mainly like the stock one with the ability to run apps from sd card.
have you tried fresh 1.0 its pretty close to stock. If you want you can just return to your nandroid that you did after you rooted but before u installed any ROMs and thats basically a rooted Stock ROM
yeah im gonna try that because now I cant do anything, I hope I didnt mess up my phone, no matter the update I apply(and I try wiping to) it just sits at the htc screen.
How do you apply the nandroid backup?
I just basically have the folder with everything in it on desktop
boot into recovery mode and go down to the listing that says Nandroid Restore.
also when you install a new ROM it isnt rare for it to take up to 10 minutes to boot.
yeah i mean id wait 30-even 45 mins, it just sits at the htc screen, and sometimes the lock screen will even appear, i jsut kept getting errors for force close
and id get to a permission screen, itd say like overclock at the top and ask for permission?
any idea what that is and what todo?
Nandroid Restore. I assume you did make a nandroid right after you successfully rooted correct?
yeah its doing the nand. restore now. hopefully all is well. just waiting for it to finish restore.
ive never had a problem rooting, my g1 always worked fine.
ah phew, thankfully I had a backup. and i was thinking, is their honestly any reason to go to a rom atm? I mean for my g1 I used one because it was faster, quicker, more features, and had apps2sd.
but atm for hero atm doesnt look like a top notch one yet?
also can the stock rom with root do apps2sd?
and easiest way?
firstboot scripts can keep your phone at the htc boot animation for 5-10 minutes. I don't know if you waited that long or not but generally I have seen that first boot with a custom rom take a little while to get things setup right.
samrozzi said:
yeah i mean id wait 30-even 45 mins, it just sits at the htc screen, and sometimes the lock screen will even appear, i jsut kept getting errors for force close
and id get to a permission screen, itd say like overclock at the top and ask for permission?
any idea what that is and what todo?
Click to expand...
Click to collapse
obelisk79 said:
firstboot scripts can keep your phone at the htc boot animation for 5-10 minutes. I don't know if you waited that long or not but generally I have seen that first boot with a custom rom take a little while to get things setup right.
Click to expand...
Click to collapse
He already stated he waited way more than 10 mins....
Fresh 1.0 makes your phone quicker, I wasn't going to ROM until a really customized and polished one came along but after trying Fresh, I'd highly recommend it.
Hey all, I've been running Ic3ROM 2.6 or 2.7 (can't remember now) for a while. Upgraded to that from the two previous versions of Ic3ROM.
Right now I cannot flash ANY ROM. I always end up having to restore my nand backup.
I've tried flashing DarchDroid 2.5, 2.6, 2.6.something, and 2.7. I've tried flashing Ic3ROM 2.9. Every time I do it flashes fine but when I boot I get stuck on the black HTC loading screen for 30+ minutes. Sometimes I'll hear the phone vibrate and see it start that loading screen over, too.
This is very frustrating as I'm such a fan of trying out different ROMs and the latest darchdroid looks fantastic (love AOSP).
Any ideas? I've tried wiping, wiping battery stats, rotate settings, dalvik, even my SD card.
remove your SD card from your phone after you flash, see if it boots then.
Thanks, will try that tonight. Hadn't even thought of it.
(Waiting on a call back about a major job interview so won't do it today at work, heh.)
No luck. I got impatient and tried your suggestion, Kcarpenter, and had no luck.
Thinking I'll just have to struggle with the RUU tonight. The only reason I'm so adamant about flashing a new ROM is that my phone reboots randomly when I hang up or when I try to answer a call. Occasionally just for fun it reboots when I look at it.
Is_907 said:
The only reason I'm so adamant about flashing a new ROM is that my phone reboots randomly when I hang up or when I try to answer a call
Click to expand...
Click to collapse
Here, try the OC kernel fix for those issues......http://forum.xda-developers.com/showthread.php?t=705074
Is_907 said:
I've tried flashing DarchDroid 2.5, 2.6, 2.6.something, and 2.7. I've tried flashing Ic3ROM 2.9. Every time I do it flashes fine but when I boot I get stuck on the black HTC loading screen for 30+ minutes. Sometimes I'll hear the phone vibrate and see it start that loading screen over, too.
Click to expand...
Click to collapse
Does your dalvik debug monitor (ddms.bat) output anything when this keeps happening? If so could you post that for us?
smolck said:
Here, try the OC kernel fix for those issues......http://forum.xda-developers.com/showthread.php?t=705074
Click to expand...
Click to collapse
That's not exactly the problem I'm having... no FC, just reboots.
But I'll try this anyway when I get home. Can't hurt, right?
Can you run adb logcat when it's booting? If you can post it on pastebin, we can probably help you out a bit more.
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.
I am trying to flash MIUI coming from CM 7.1.0 but everytime i reboot into recovery it will stay on recovery for a second or two then just reboot the phone back to CM. can someone tell me what the problem is here?
Have you tried to reflash the recovery yet?
Sent from my HTC Glacier using XDA App
no how do i do that?
nevermind i know how
EDIT: the reason it is doing that is because the trackpad is "stuck" and before i can scroll down to do what i want it clicks reboot phone
does anyone know how to COMPLETELY disable the trackpad? because mine is stuck so it will select things at random and makes the phone very hard to use. i have tried different roms so this has to be a hardware issue. i would rather just disable it if it is possible rather then go through with trying to get a replacement.
thanks
NickDoughty said:
does anyone know how to COMPLETELY disable the trackpad? because mine is stuck so it will select things at random and makes the phone very hard to use. i have tried different roms so this has to be a hardware issue. i would rather just disable it if it is possible rather then go through with trying to get a replacement.
thanks
Click to expand...
Click to collapse
The problem is that any software solution to disabling the trackpad would be wiped out when you started the flash of a new ROM.
So you might end up disabling it to start the flash of a new ROM, then whatever you did to disable it would get undone during the flash, and you COULD (probably unlikely, but COULD) end up with the stuck button causing a worse problem during the final stages of the ROM flashing.
I can't imagine what problem it would cause. I'd just be nervous about going through the flashing process with a button on the phone sending signals to the processor constantly.
I think I found out the cause of some bootloopings and its the "Log Switch" option in project menu.
When we try to root the rom and the the phone reboots:
A)if he reboots ok, you must go again into project menu (*#*#2846579#*#*) and "switch off" the Log.
Everyone tell us we must switch this thing on in order to root the phone but no one says that we should turn it off again after proccess completed....
B) if starts immediatly with bootlooping and never booted againd after the rooting proccess just take the battery out andenter into recovery (vol up + Power). Once there make a "Data factory reset" and reboot.
The phone will then start normally this time with no Bootloopings.
With luck you have SU installed and the phone is rooted.
If yes, just go to project menu (*#*#2846579#*#*) and "switch off" the Log.
If not just try the rooting again
But the major deal is the Log Switch.
Hope it helps anyone
I never had bootloops with 2.3 official rooted and log switch was turned on before and after
I'm happy for you!
Moved to General
Thought this may be helpful to some, it has no place in the development section.
Thanks for the contribution, i would usually close, but as it could be helpful, on this occasion i will move it.
Take it easy
O_G
yes don't close it please as I noticed that many had bootloop issues with these releases. I was one of them but this finished after switching the log of. In my caes that solved my problems.
I had thought that too but none of the combinations i tried worked.
I had tried switching off Logging,factory data reset,flashed again without rooting and after 2-3 days that everything seemed that worked normal and i had loaded all apps i wanted, bootloop appeared again and had to factory data reset again in order to use phone.
So i gave up and reverted to 2.2
I never had bootloops but if that's really what's causing it, that's a great catch!
Congrats!
well as I said with me, since I have done this the bootlooping stoped.
Before Everytime I reboot the bootlooping started and only stoped with a factory reset. Then I tried to switch Log Off again and not a single bootloop and more than 48 hours.
Flashed OC kernel, UOT Kitchen, etc etc and phone running perfect.
Look, I have flashed and tested this rom many many many times and alwas endup with bootlooping eventually. This did the trick for me and I consider it a major step as I can now use the rom freely and without being afraid.
As I said, is just 1 more Idea that people having this issue could try out and see if helps.
I just took the liberty of sharing this so that in case o dispair for some, they can have other alternatives.
Didn't help me, actually it did the opposite...my phone didn't boot loop until I went and touched the freaking "Log switch" option...should have let it ON...GRRRR....Got to taste Huawei's bad medicine again...or my own...I should have known; if it ain't broken, don't try to fix it!
lololol
Huawei's each one with own personality...
Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Tell me about it.
SilveRRing said:
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Click to expand...
Click to collapse
You understand it opposite m8.
You must turn the Lon On to root the phone.
After root my advice is to turn it back Off again as it was from the beginning..
Ah ok, nevermind then. lol
my x5 dont have bootloop but this topic will help very people,thanks for the trick lol
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
driuda you have a theme of UOT Kitchen??? I make one for me but failed,please help me?i dislike stock theme is for children hehehe
at the moment I only used UOT this time to change the battery icon to battery percentage circular.
Its one of those must haves that I miss from official rom, the battery percentage....
Coking a theme is very easy. You just choose all the option you want and in the end upload the framework-res.apk and SystemUI.apk files and wait for the coking.
After that pick up the file and flash it with CWM.
mhh i dont think that the log switch is the only thing that causes bootloops.
first i installed 2.3.5 and a few hours later i switched the og on. The bootloops started.
So i had to do a factory reset...
Now after the reset I quikly turned off the log switch. but just a few hours later it started again bootlooping......
any other ideas? or do i have to go back to miui? when yes can i do the following?
: 1. factory reset
2. get root
3. install cwm
4. install my backup?
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Druida69 said:
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Click to expand...
Click to collapse
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
levibuko said:
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
Click to expand...
Click to collapse
if it is to downgrade and then move forward to any other rom, custom or not, you can use any version don't loock spexifically to a german one.
Here you have a list of stock rom:
http://forum.xda-developers.com/showthread.php?t=1167882
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800 (MOdaco Wiki)
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8800_IDEOS_X5 (XDA Wiki)