Database Users

[U8800] End of some Official 2.3 Bootloopings

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)

[Q] Please help fix my buddies Defy

Hey guys. I'm trying to fix my friends Defy for him. I've rooted my old Evo 4g, my wifes samsung transform, and her motorola Photon Q so I'm pretty familiar with rooting. But I'm having a problem with his Defy. Here's the skinny:
So his phone froze up on him. And after pulling the battery, it now won't boot. So I booted into recovery, and tried a factory reset. The factory reset won't complete. The little loading bars that go across the screen just keep going forever (I let them go for 3 hours straight one day). And I still can't get the phone to boot. So I figure, no big deal, i'll just root and install custom recovery. So I looked into rooting methods for the Defy, and they all seem to involve booting the phone. Does anyone have any ideas? Or know of a way to reflash the original recovery? I'm assuming the problem is the recovery. Thanks in advance for any help. And my buddy thanks you too.

You can use RSD to flash it with stock rom of your region. Do not flash any gingerbread rom if the phone never had gingerbread(you will have downgrade issues).
I don't want a Tapatalk sig!

never heard of rsd. Just looking into it. It seems people are saying I would need to wipe cash and data first? Problem is when I attempt to wipe cache it just goes on forever never finishes.

Any Luck M8
dhughes214 said:
never heard of rsd. Just looking into it. It seems people are saying I would need to wipe cash and data first? Problem is when I attempt to wipe cache it just goes on forever never finishes.
Click to expand...
Click to collapse
was just reading your post and was wondering if you have had any luck with your buddy's Defy ???

Flashing a fresh .sbf using RSDlite should fix the recovery problems, as it will overwrite it with a fresh one. The /system partition will be rewritten, also. After flashing, the phone might boot to the system already, but if not, just enter recovery and do a factory reset, now it should finish fine and boot fine, as well. (it doesn't matter if you do a factory reset before or after the flash)
Latest RSD Lite I've found is v6.1.4. You will also possibly need drivers, google for - "Motorola_End_User_Driver_Installation_5.9.0"
Keep us posted! Good luck

[Q] Defy plus - erased all partitions

Hi
I tried searching the forum but couldn't find anything similar.
I did something really stupid. I was going to install the CM10.2 ROM by quarx for my defy+ and i just wanted to wipe my mobile to make it clean slate before flashing the new ROM. Turns out, i did an extremely good job at it. I earlier had CM10.1 by quarx on my rooted phone. I went to TWRP recovery and selected advanced wipe and checked all options. When i tried to exit, it actually warned me that my phone is unrooted. I didn't understand why it said that and ignored it.
Big Mistake.
Now my phone is stuck at the Motorola logo, which i expected. But there's no custom recovery, which i did not expect. There is no blue led flashing when i reboot the phone anymore. The stock recovery is still accessible, but it won't install the CM10.2 ROM coz the signature is unverified or something.
What should i do now? Really need some advice.
P.S. my battery was around 20-25% before this happened. So i don't wan't to waste it by trying out something on my own and get caught mid-way while flashing something and brick my phone.

maddy.wolvie said:
Hi
I tried searching the forum but couldn't find anything similar.
I did something really stupid. I was going to install the CM10.2 ROM by quarx for my defy+ and i just wanted to wipe my mobile to make it clean slate before flashing the new ROM. Turns out, i did an extremely good job at it. I earlier had CM10.1 by quarx on my rooted phone. I went to TWRP recovery and selected advanced wipe and checked all options. When i tried to exit, it actually warned me that my phone is unrooted. I didn't understand why it said that and ignored it.
Big Mistake.
Now my phone is stuck at the Motorola logo, which i expected. But there's no custom recovery, which i did not expect. There is no blue led flashing when i reboot the phone anymore. The stock recovery is still accessible, but it won't install the CM10.2 ROM coz the signature is unverified or something.
What should i do now? Really need some advice.
P.S. my battery was around 20-25% before this happened. So i don't wan't to waste it by trying out something on my own and get caught mid-way while flashing something and brick my phone.
Click to expand...
Click to collapse
Flash the respective SBF using RSDLite. If your battery dies, then charge using mcgyver method or a universal battery charger.
Sent from my MB526 using Tapatalk

[Q] Defy does not start anymore

(this thread might also be called "A series of unfortunate flashes")
So, i was trying to upgrade my (obviously rooted) defy from a CM10.1 to CM11. Since this upgrade gave me the error message "set_metadata_recursive: some changes failed", i tried installing CM10.2 to see if it makes a difference and that worked. But i still wasn't able to install CM11. After another unsuccessful flash of CM11, i didn't remember to flash a working rom back on it again and instead rebooted the device. By doing, i was not able to get into recovery mode anymore. In fact, my phone just showd the red Motorola sign and seemingly did nothing. I was though able to boot into flash mode (by holding down the VOL-UP button) as well as into the motorola recovery (by holding down the VOL-DOWN button). The latter did not allow to flash anything, but i was able to delete the cache and so on.
So i decided to try and flash an sbf file. I downloaded sbf_flash.sh (running linux) and i downloaded the "Retail DE, AT, CH" sbf-file from hxxp://sbf.droid-developers.org. I got the device into flash mode and ran sbf_flash.sh which ran smoothly and rebooted the phone.
Now the phone won't power up at all. When i connect it to usb, the white led is on, but otherwise it's not giving me any sign of life.
Is there hope or should resign by smacking myself on the head?
regards.

tmcookies said:
(this thread might also be called "A series of unfortunate flashes")
So, i was trying to upgrade my (obviously rooted) defy from a CM10.1 to CM11. Since this upgrade gave me the error message "set_metadata_recursive: some changes failed", i tried installing CM10.2 to see if it makes a difference and that worked. But i still wasn't able to install CM11. After another unsuccessful flash of CM11, i didn't remember to flash a working rom back on it again and instead rebooted the device. By doing, i was not able to get into recovery mode anymore. In fact, my phone just showd the red Motorola sign and seemingly did nothing. I was though able to boot into flash mode (by holding down the VOL-UP button) as well as into the motorola recovery (by holding down the VOL-DOWN button). The latter did not allow to flash anything, but i was able to delete the cache and so on.
So i decided to try and flash an sbf file. I downloaded sbf_flash.sh (running linux) and i downloaded the "Retail DE, AT, CH" sbf-file from hxxp://sbf.droid-developers.org. I got the device into flash mode and ran sbf_flash.sh which ran smoothly and rebooted the phone.
Now the phone won't power up at all. When i connect it to usb, the white led is on, but otherwise it's not giving me any sign of life.
Is there hope or should resign by smacking myself on the head?
regards.
Click to expand...
Click to collapse
Your battery is dead. Charge it using McGyver method or with an external battery charger.
Sent from my Nexus 7 using Tapatalk

hotdog125 said:
Your battery is dead. Charge it using McGyver method or with an external battery charger.
Click to expand...
Click to collapse
It's a good idea, but i have another defy here and i've checked: the other battery is 80% charged but the phone still isn't going on...

tmcookies said:
It's a good idea, but i have another defy here and i've checked: the other battery is 80% charged but the phone still isn't going on...
Click to expand...
Click to collapse
Is RSD recognizing it?
Sent from my Nexus 7 using Tapatalk

hotdog125 said:
Is RSD recognizing it?
Click to expand...
Click to collapse
Who would have thunk? RSD Lite did recognize the phone and when it started flashing, the phone showed
"SW Update
In Progress.."
So, now what? Which sfb file should i flash?
Anyway, thank you so very much!

Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?

tmcookies said:
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
Click to expand...
Click to collapse
Yes, root again if needed.

I saw your other post in the cm11 thread about how your phone died.
I remember reading somewhere in the forums that you should go to cm10.2 before installing the updated recovery, and then install cm11.
I'm not sure if that's 100% accurate, and I couldn't find the link (sorry).
Couldn't hurt, though, seeing as you'd just have to do a few extra ROM flashes.
Good luck!
tmcookies said:
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
Click to expand...
Click to collapse

Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps. Hope it helps :angel:

after some effort - great on CM11!
leandrolutz said:
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps. Hope it helps :angel:
Click to expand...
Click to collapse
I had a simiilar problem - somehow after a similar failed CM11 install, I pressed that "reboot" button and my mb525 was dead. I did as suggested here, Except I happened to have CM10.1 not CM10 on the SD.
However I had a lot of trouble getting a successful boot after installing update-recovery.zip, and then also after installing CM11 with the updated recovery.
Now I have a great well-running defy on CM11. I don't exactly why it succeeded when it did - just repeatedly wipe and install and wipe until it worked.
The defy really runs well on CM11 - very responsive - it is robust both in HW and SW! - maybe I'll myke it my main phone again! (before the S3 or the xperia V) - Samy just ain't interested in my S3 - the community provides the same Android version for my defy as I have on my nexus 7 2013!!!
Many thanks to all who have contributed, especially quarx -

try this http://forum.xda-developers.com/showthread.php?p=48501247

[Q] Defy hard resetting itself on each boot.

Hi everyone!
I am having very strange problem with stock rom "JORDN _U3_6.36.0" from T-Mobile USA on standard Defy. Each time i power phone up, it starts booting up then restarts itself in to stock recovery and perform hard/factory reset. After that it boots normally, but all settings gone.
I am not using T-mobile sim or moto blur account , so i skip registration using "ebluroff" trick. Is that can be the cause of the problem?
Some backstory: when i bought the phone it had CyanogenMod 7 installed on it. I used it for 2-3 years,even updated it several times up to 7.2.
Then some time ago i started having issues with it, so i had to flash stock rom with 2.1 Android.
I decided not to do anything with the phone, until i got some advice, so i any help would be greatly appreciated.

What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk

thekguy said:
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.

DEN383 said:
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
Click to expand...
Click to collapse
Some update. After hours of digging i found out these thread http://forum.xda-developers.com/showthread.php?t=899450
So, i first flashed defy 2.2_boot_only FIXED FSB, then after reboot custom recovery started working, so restored Droid22 rom from it.
Phew, i knew it was possible. So now i have rooted chines (?) android 2.2.1 on my phone and working custom recovery. I am gona stick on it for a while until i find best 2.3.3. nandroid ROM.
Just wanted to clarify was it right order - first flashing fixed SBF then restoring nandroid backup? I couldnt get custom recovery working without updating bootmenu first.
I also wanted to add that i did custom recovery data|cash wipe before flashing fixed SBF, before AND after restoring nandroid backup.
I saw that lots of people had problem like me , hope my message will help.
Here is link to another forum which has working download links http://www.addictivetips.com/mobile...ed-rooted-android-2-2-froyo-on-motorola-defy/