Database Users

2.1 Leak randomly restarting

Hello everyone. I'm not sure if this has been posted, I did a search, and didn't see anything related to my issue. I installed the newest 2.1 leak, and my phone will randomly just power itself off. I've wiped the memory and reinstalled a few times. I'm just running the basic system, with Handcent, Pdanet, Droid Live lite, and Astro file manager installed on it. Any suggestions as to what may be causing the problem, or what I can do to try to fix it?

Leak is a curse word around these parts. you said you "wiped" a few times. are you on ROOT? if so, you shouldnt be using the plain root. you should download a ROM, (Ivans 0.8T2, Senseable, Evil Eris...) put it on your sdcard, wipe, then flash one of those. So IF you have ROOT, then change your thread title, otherwise people such as myself may get medieval on you.

Out of curiousity, why shouldn't one use plain root? I have yet to flash a ROM because none of the ROMs seem to be bug free. Am I wrong?

meanm50 said:
Out of curiousity, why shouldn't one use plain root? I have yet to flash a ROM because none of the ROMs seem to be bug free. Am I wrong?
Click to expand...
Click to collapse
the plain root is more buggy than any ROM actually. Ivan's rom has fixed some bugs (not sure which, sorry. but hes trustworthy) and Senseable is just a themed version of Ivans rom. you're better off with a ROM since devs are always working to fix bugs. some but (like the signal standy issue) probably wont be fixed unless HTC releases a newer update for the official release.

[Q] Crash on all custom roms

Hi everyone,
I recently acquired an X10 and first thing to do was, of course, upgrade to froyo. Although, frustratingly I am not having any luck with any custom roms. All present the same problem: the phone boots to launcher, will stay on for 3/4 seconds and then crashes and reboots. I've followed instructions accordingly and made sure to have the correct baseband but to my demise, still no luck.
Is this a common problem with this phone? Anyone know anything that I can try? I'm ripping out my hair here, and getting very fed up with this phone!!

Most reboot once or twice upon launch but then its fine. U need to be patient
Sent from my x10 on gingerbread

I waited as you suggested but it just keeps on rebooting countless times until the battery eventually ran out. Could it be a hardware problem of some sort?

Thats a tipical problemwhen you got the wrong baseband instaled.
Flash the correct baseband for the ROM you are trying to use.

Do a clean flash with seus, then use flashtool to root and xrec. Or try to flash a plain baseband file from the collection, also afterwards clean dalvik cache.
Sent from my LG-P990

The SE update (stock) rom is BB 54. I tried Achotjan rom on bb 54 and same problems. I also tried TWlauncher Ultima 4 flashed on BB 52 and still had the same problems. This may be a silly question but is there a suggested BB to use? Is a higher BB better than a lower one? I didn't have this much problem flashing my Milestone

Hey man the rom tells you which baseband is best. Read the instructions. If you have the same problem. Then boot into recovery and flash cobratos baseband patch
Sent from my x10 on gingerbread

ahmedre said:
The SE update (stock) rom is BB 54. I tried Achotjan rom on bb 54 and same problems. I also tried TWlauncher Ultima 4 flashed on BB 52 and still had the same problems. This may be a silly question but is there a suggested BB to use? Is a higher BB better than a lower one? I didn't have this much problem flashing my Milestone
Click to expand...
Click to collapse
Go to dev section and look for roms treth and flash whit flashtool either rogers or era polan rom then flash your favorite rom i flash a lot,, the best ive use is zdzihu freexperia x10 beta 4
Sent from my X10a using XDA App

[HELP] Freezes and Reboots w/Custom Kernels

Hi there,
Ok, here is my last try to get a fix before I quit. I have a problem only related with Custom ROMs so I expose it in the Dev zone. Sorry if it is not correct.
For those who haven't follow the Perfect Recovery topic, I have one of the so called X5 Black Sheep. Initially these X5's appeared in Portugal and the synthom was stuck forever on IDEOS screen when enter in CWMv4.0.0.5 from genokolar. Finally stockwell have modified the CWMv4 with the kernel from MIUI and we can now enter in and flash the new Custom ROMs.
The thing is, my X5 keeps freezing and restarting in ALL custom ROMS. I have tried Oxygen, CM7, void and MIUI. ALL with same result. Even the ClockWorkModv4 from stockwell freezes and restarts sometimes when making or restoring backups.
I think it is something related with I/O SDcard as the reboots/freezes happens 90% when making something with it (mounting SDcard in PC through USB, or in Antutu when testing SDcard) but I have tried without SDcard and also with 3 different SDcards. All with same result.
I have absolutely no problem with Official and stock B137 ROM. Only with custom kernels (except SuperBoot from Paul fo Modaco that works 100% stable). Another example is I am absolutely stable with B137 stock but, if I put the boot.img from franciscofranco kernel for void, I can boot but again I have freezes and restarts.
What do you think the problem is? Do I have a faulty X5? Although is strange that with official kernel or SuperBoot everything works stable.
Any help, please?

I have exactly same problem!
I bought a x5 2 days ago. Catched up to the rom scene and tried to root the phone.
The phone was also stuck on ideos logo when trying to boot recovery 4.
Tried the recovery for the black sheeps and worked! Installed the rom and was amazed by the speed and usability.
Downloaded a lot of apps's and it started crashing. So I tried to remove app by app and the problem remains!
The first time it crashed I had problem turning the phone again (even after taking the battery out!).
Now sometimes crashes on standby and turns off.
Most frequently crashes during phone calls.
In one afternoon more then 8 crashes!
Tried to remove the SD card and now i'm waiting to see if the problem is solved.
So the problem is real. I must have a black sheep. And the cure for the black sheep is partially working since it must have some bugs in it..

maxusz, are you portuguese? Because I only have knowledge of Black sheeps in Portugal. At least here in xda never saw anyone complaining from any other country except Portugal, which is odd.
Regarding your problem, it is a bit different than mine. When I flash a custom ROM or put a different boot.img (except SuperBoot), I get freezes and restarts right off the boot. Sometimes I have time to complete a Antutu, but that is rare. Most of the time it hangs within 2 or 3 minutes after booting.
And, as I said, even in stockwell's CWMv4 I have freezes and restarts because it uses MIUI's kernel.
It seems that I have a different hardware from other X5's but... on the other side, I have no issue at all running B136 and B137 ROMs. I really can't understand what is the problem and I am very sad as I bought this model because it was getting a very good development community and now... I'm stuck with stock firmware.

Go to TMN and demand to change the device for a new one.. tell them that it doesn't boot.. if you are in those famous 15days after buy.. if it goes to warrantly you may not have lucky.
Or demand you money and wait for the new remittance of ideos x5, once TMN x5 is out of stock, at least at Lisbon. good luck m8

Been there, done that and I got another black sheep... I am still in that 15 days period although I don' t want to spend my life doing this until I got a normal one.
I would rather prefer to understand and fix whatever is wrong with these X5.
Sent from my u8800 using XDA App

Go there get your money back and wait for brand new X5s in a couple of weeks. Much better than waiting for ever for a working fix which might never happen, since not everyone has the same issue.
best of lucks Royal ;(

If I have to guess - and watching the differences in consistency of the product - I would say there's some difference in HW and thus missing a driver for something. unfortunately, this is just a guess that need proper investigation if this is plausible.

I might do that. I just hope that TMN have stock again very soon.
I am no dev nor programmer but I really like to know the technical difference between these models and the normal ones.

lourenzo said:
If I have to guess - and watching the differences in consistency of the product - I would say there's some difference in HW and thus missing a driver for something. unfortunately, this is just a guess that need proper investigation if this plausible.
Click to expand...
Click to collapse
Anything I can do to check that?

Probably the easiest way to do this is find out why/when it is rebooting... noein already tried to help you, right? try to catch is attention: is examinations must be all done by now
I'm no expert - just guessing...

RoyaL said:
Anything I can do to check that?
Click to expand...
Click to collapse
After a restart, use an app like Root Explorer or ES File Explorer (or adb) to grab the /proc/last_kmsg file and post it here. That should help the devs to find out what is different with your phone.

I am from Portugal!
Bought mine from TMN Aveiro!
Mine also got stuck when installing recovery. I had to try differente boot.img and then the one it worked was the one for the black sheeps

atiatinini said:
After a restart, use an app like Root Explorer or ES File Explorer (or adb) to grab the /proc/last_kmsg file and post it here. That should help the devs to find out what is different with your phone.
Click to expand...
Click to collapse
Before testing I was checking and I can confirm that I do not have any file or folder inside /proc named "last_kmsg".
Any clue?
I was thinking... Could this be caused by I have upgraded to B137SP04 Official ROM and this changes anything in the system that is used by any custom kernels?! Does this makes any sense?
Because the B137SP04 is later than any custom ROMs. For example, void was first created based on FLB (I think) that was based on first B137 ROMs. SP04 came after.
Just a shot in a dark.

nope - I also cheked and couldn't find that file (unless it's hidden).

RoyaL said:
I was thinking... Could this be caused by I have upgraded to B137SP04 Official ROM and this changes anything in the system that is used by any custom kernels?! Does this makes any sense?
Because the B137SP04 is later than any custom ROMs. For example, void was first created based on FLB (I think) that was based on first B137 ROMs. SP04 came after.
Just a shot in a dark.
Click to expand...
Click to collapse
I don't think so... I had the same problem... CWM 4.0. I upgraded from TMN ROM to B137 (Czech Omitel) and afterwords I've instaled MIUI custom ROM (with CWM 3...) and upgraded to CWM 4 after stockwell update.

can't find that file either! did a search of it and it's nowhere to be found!

rimsilva said:
I don't think so... I had the same problem... CWM 4.0. I upgraded from TMN ROM to B137 (Czech Omitel) and afterwords I've instaled MIUI custom ROM (with CWM 3...) and upgraded to CWM 4 after stockwell update.
Click to expand...
Click to collapse
And you have no problem, right?

no problems!

RoyaL said:
Before testing I was checking and I can confirm that I do not have any file or folder inside /proc named "last_kmsg".
Any clue?
Click to expand...
Click to collapse
That's odd... Try to do an adb logcat until your phone restarts and post it here. Or you can do it directly from your phone: install the 'Terminal Emulator' app, open it and enter 'su', and then 'logcat > /data/logcat.txt' commands. Wait until your phone restarts. Then use Root Explorer or ES File Manager to grab that file (/data/logcat.txt) and post it here.

Hmm... This sounds a bit like the issue I am having with custom kernels on my X5, bought in Sweden in April or so.
I tried a couple of overclocked kernels on top of the stock ROM a while back and they all crashed my phone in less than an hour so I gave up on those. I am still on the original ROM (no OTA updates here in Sweden) and have not tried or moved to recovery v4 yet.
Which custom ports and ROMs actually work well on the black sheeps?
Need I say I am little disappointed in Huawei...

How to flash CM 7.2 RC3 from 2.2.2?

i bought cheap milestone 2 and wanted to try CM on it
rooted, installed CWM
tried to flash CM 7.2 RC3 and it fails after "checking kernel version..."
so i guess my 2.2.2 is too old
went back to wiki, tried to flash their downgrade rom VRZ_A955_2.3.20_1FF_01.sbf hoping that it will get me to the right spot
no joy here as it fails (running as admin etc.) with "Phone is not compatible with multi-interface super-file."
any suggestions what to do now, as this is where i start worrying that i might do\flash something stupid and brick it

Hello!
Sorry if I'm wrong but, wouldn't be needed do update to 2.3.6 first?
Yet, this could help:
http://forum.xda-developers.com/showthread.php?t=1310641
It says that you can update from Froyo.

actually it was just me being dumb as i tried to install
update-cm-7.2.0-RC3-droid2-signed
instead of
update-cm-7.2.0-RC3-droid2we-signed
as WE in filename means that this is rom for global, gsm version (that i have)
it updated ok, but all i get now is motorola logo and then black screen, i can't even get CWM to start...

Hi, first you may know, there are two different phones Droid 2 and Milestone 2 (A953), maybe you are trying to flash wrong sbf to your phone.

pepe55 said:
Hi, first you may know, there are two different phones Droid 2 and Milestone 2 (A953), maybe you are trying to flash wrong sbf to your phone.
Click to expand...
Click to collapse
yup, just figured it out, had to flash back to 2.2.2 with
MILS2_U6_2.4.24_SIGNED_UCAMILESTONE2B1B80E100E.0R_UCXMILE20RTGB_P040_A013_HWp2a_Service1FF.sbf
and is working now...
for some reason i thought that droid 2 global = milestone 2
what should i look for if im interested in most stable rom for milestone?

Indeed, be sure of the sbf version.
Try going back to stock and do it again, cleaning data, cache and dalvik before and after update.
*didn't see that it worked hehe
Most stable roms, IMO are MIUI 2.5.25 and CM7
Now i'm trying CM9 (20120602) and i'm enjoying, still checking. Seems like it's worth the try.
Still some issues to solve, like recording, etc... but looks like good for daily use.
People say that MIUI tends to give some compatibility issues sometimes. And Cm7 fails to run some apps... like ShadowGun (well, in my Miles it fails hehe).

I'm very happy with MIUI from Will5, check it. It has very good battery life, the rom is smooth and stable and very addictive =D. I got small amount of forbidden crashes. I'm trying other roms as well but always come back to MIUI until better rom comes out, if it happen sometime. It has froyo kernel and i dont have any strange touchscreen bug, but the touch responsive is a little less then newer kernel, thats no problem for me.

trying it now, installation hints states "Flash UPDATE_2.5.25.zip from cwm 4.x.x.x or greater"
how to get cwm 4x?
all i found is 2.something in cm wiki and 3.1 in bootmenu
anyway i installed it with 3.1.0.0 and it seems to be ok

I installed it as you without any problems, I think it can be flashed from recovery from droid2bootstrap. If you dont like MIUI you can try another ROMS maybe original 2.3.4 sbf, in developer section is manual to get out the blur (and bloat) from stock roms. I test it someday but Im happy with MIUI.

pepe55 said:
I installed it as you without any problems, I think it can be flashed from recovery from droid2bootstrap. If you dont like MIUI you can try another ROMS maybe original 2.3.4 sbf, in developer section is manual to get out the blur (and bloat) from stock roms. I test it someday but Im happy with MIUI.
Click to expand...
Click to collapse
miui installed fine, it looks great, but after some basic configuration launcher start FC, as i dont have time to experiment just now i flashed latest CM7 i found (cm7-120221-1901-NIGHTLY-Milestone2.zip) and it is working perfectly, just as good as on my LG P990

[Q] Rooting a U8800 that's currently on 2.2...

Good evening all,
Basically I'm looking to root my girlfriends fathers U8800, it's currently running android 2.2. He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
I've read there are 3 different types of models for this handset. How do I know which one we've got? If that's relevant?
I've found this thread that seems dead easy to follow, http://forum.xda-developers.com/showthread.php?t=1420728 , am I ok to proceed?
When I've rooted it, do I just flash a rom via CWM like I would with my galaxy s? And will I be caught out with bootloader issues or little things like that?
Thanks in advance.

If the device is the U8800 regular model(not pro or plus) you can follow the guides of the link.
And yes, you can flash a rom from cwm recovery.
Only one suggestion. If you flash the latest stock gingerbread rom(I think is the 522), search for a thread called "get your pink screen back" on developing section. The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.

Thanks for that, I'll get on it tomorrow with an operational head. I'll do the pre root checks and make sure I have everything I need in place before I get going.

dancer_69 said:
If you flash the latest stock gingerbread rom(I think is the 522)
Click to expand...
Click to collapse
It's 528
dancer_69 said:
The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Click to expand...
Click to collapse
*locked pink screen.
Sent from my GT-P1000 using Tapatalk 2

If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!

Dave759 said:
He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
Click to expand...
Click to collapse
Did you look to see what is causing the battery drain? I have a friend with a stock GT540 that had serious battery drain. Turns out it was the GoSMS program. Deleted the app and now his phone lasts 5 days between charges. Switching a rom won't help if the problem is an app.
1) Get cpu spy and see if it is going to deep sleep
2) If not sleeping, turn off running applications one by one and test via cpu spy to find out which one is causing it not to sleep.
3) Either remove the offending app or use Autorun Manager to modify the receivers (if rooted)
You can fix his problem without changing his rom. If he wants root, superoneclick can root 2.2, I just used it the other day. Also make sure he is on the latest 2.2: b138sp04 or b163. I prefer b163, even though it is the China rom, because I like the Huawei launcher better that stock.

A.C.A.B. said:
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Click to expand...
Click to collapse
That's not true... official 2.2 is the slowest thing in existence. If he just needs stability then Ezets CM7 is the answer. There are no bugs with it (except wifi tethering) and it's much much faster than stock...
Also he can undervoltage it to preserve battery life more than stock ROM.
Sent from my U8800

You want the best 2.2 you try Void Eridanus. Everything works.
Want the speed, OEX rom it's a Ferrari. Everything works less the mms with data off.
You can also keep the stock Rom, root it and just apply a ffranco kernel. This way you gain the speed.
3 good solutions here.
I'm don't revert to stock Rom for 2 reasons, cam quality and battery life, otherwise i would use stock Rom without a shadow of a doubt.
In terms of stability and all working it's stock 2.2 Rom and this is unquestionable!!!
I have been trying ALL roms and ALL respective versions since July 2011 therefore I do speak by personal extended experience
I repeat once again, in the conditions you mention leave the phone as it is. If you want to do something just root it and that's it.

as a matter of facts i had my phone with so many rooms that i can even say how many but if u want stability i recomend oxygen... if u want stability and good looks use miui 32...
last .32 miui that i used was from miui portugal in english and nothing to say about that...
battery for 2 days and all smoth...
but my phone is weird... he can take almost every rom and be usable...

The issue with miui pt versions it's the cam quality that is horrible. It's just this detail that it's not very good. The rest it's perfect.
Sent from Odin's device!

Hey everyone, back for an update and some other steps. basically, he got frustrated with how the battery so he went out today and bought the newer huawei. Reading eveyones comments here i think its due to the ammount of apps and being on froyo hasn't helped any thing, but anyways its now my new toy to play with. So far, followed the link i posted in the first thread, rooted and installed the latest CWM (v5). I'm now a little confused when it comes to the get the pink screen back, should i follow this thread http://forum.xda-developers.com/showthread.php?t=1457490 now before flashing a new rom or afterwards?
Again thanks for all the help, I'm almost done bothering you all for now
Edit: Reading on some ROM's and the comments above, i should install B518 stock ROM then flash the bootloader fix from the thread posted above then i can install other ROM's? If so where can i get the stock B518 ROM and how do i know which version I'm using? Sorry and thanks again.

First, which rom you have now?
You can find the version from settings -> about phone.
If you have a newer than 518 version you need to change the bootloader with the one from 518. If you have 518 you don't.
Also check which version of kernel you have(is on about phone also)
If you have a 2.6.32 version(which mean that you have froyo rom), you can flash only roms with this kernel version. If you have a 2.6.35 version, you can flash roms with 2.6.35 kernel or 3.0.8(as aurora ICS).

Basically its a stock froyo rom, im looking to get to gingerbread by the end of tonight but currently im stuck on the huawei splash screen after i did a data reset in CWM. Can still get to CWM though.

What rom you want to flash now?
A custom gingerbread based of froyo's kernel 2.6.32 like CM7.2, oxygen or miui, or the official gingerbread?

Im not particularly bothered, something that won't brick the phone and is stable. I'm more worried as to why it wont boot now after a data reset.. any suggestions for that?

You can use adb and logcat function to see where the problem is. Usually when some errors prevent device to complete the boot proccess, this piece of code loops. You need to have some knowledge of programming though, but maybe is something easy.

and now i have blue screen.. what can i do? or have i bricked it?

Where you have blue screen and what you did?
Usually blue screen instead of recovery mode, means that the recovery.img is deleted from .cust_backup/Image folder

basically, i formatted something, reboot and soon as the huawei logo appear a blue scrren rolls down. when i plug the phone into the pc it detects a folder but its empty, the phone is detected as qualcomm now..

Yes, seems that you formated the partition which has the Image folder with all system images. So, now you need to flash an official rom. You can either flash a froyo or a gingerbread rom. You can avoid this only if you previous had take a backup of this folder. In this case just put all files in (empty now) image folder.