Related
I'm currently using the wildfire. I rooted it and installed rom manager.
I did backup my rom (CWRv3.2.0) and installed the wildpuzzle rom (Newest one).
But i think forgot to wipe off the data. After installing the rom, it booted fine but it says that my phone memory was low.
I waited for a very long time but it does not respond. Hence, i thought something was wrong and tried to go to cwr and did a factory reset.
But now it gives me a black screen after the htc logo.
And after 10 to20 minutes and it still does not respond. I went back and did a restore(before the wildpuzzle rom I've installed)and it came out that my phone cannot boot and stucked in a loop. (after 2 turns it went back to cwr)
I'm scared that i might bricked my phone.
Help please! Much appreciated!
When you do a Factory Reset in Clockworkmod, you need to flash a ROM again. Also, if you read the thread completely, WildPuzzle 2.3.2 does NOT work. It was released untested by danne (as he stated), and, various tests by users show it didnt boot.
EDIT: And if you are talking about Android 2.2 Sense ROM's, you will need to flash it using Clockworkmod 2.x. They are not supported on 3.x
So do i have to flash a new rom like CyanogenMod ? Sorry, I'm a complete noob at these. Edit: Its the Wildpuzzle 2.2 froyo v0.8 rom.
Clubbysupercharged said:
So do i have to flash a new rom like CyanogenMod ? Sorry, I'm a complete noob at these. Edit: Its the Wildpuzzle 2.2 froyo v0.8 rom.
Click to expand...
Click to collapse
Yeah flash the CyanogenMod 7 ROM. But before you install this ROM please make sure to Wipe the data, Clear cache partition and also to clear dalvik cache and then proceed to install the CM7 ROM
Yes! Thanks a lot! Flashed Cm7 Nightly Builds 2.3.4. Running perfectly
EDIT: Wifi does not connect lol, stucked on locating ip address.
Since i got my defy i had play with many roms (miui, official 2.3.4, MS2Ginger, WajkIUI and now Argen2Stone 2.0),
well when my phone boots for first time i set my blur account etc.
and after some time i got a reboot, and after that everytime i put my pin
i got continuously FCs and then reboots again!
My Stats:
MB525
Green Lens
What's going on??
Anyone have an idea?
ive not experienced it personally but from numerous posts ive read on here it sounds like you need to change the setvel settings in boot menu. there is a big thread about setvel settings
In the Argen2Stone Thread they say that it's not overclocked..
And i have the same issue even if i flash everything..
I tried also Official Froyo CEE, MIUI, and now i am testing the leaked 2.3.4 unrooted..
It seems stable, i flashed it about 2 hours ago..
But i will take a look on the SetVsel threads..
Thanks btw
Well, I Flashed Again Argen2Stone 2.0 and set the Overclocking on the default values, but nothing changed..
Right after i sign into my Google Account some google apps FCs,
then My Defy reboots and shows com.motorola or smthng unexpectedly closed
and then reboots again in a loop.. -.-'
UnRatedDi said:
Well, I Flashed Again Argen2Stone 2.0 and set the Overclocking on the default values, but nothing changed..
Right after i sign into my Google Account some google apps FCs,
then My Defy reboots and shows com.motorola or smthng unexpectedly closed
and then reboots again in a loop.. -.-'
Click to expand...
Click to collapse
try flashing a stock froyo sbf and then flash your custom rom, i change roms to find something interesting but till now haven't yet faced problems like you.
and also when you are on a custom rom and are planning on shifting to another one, i feel its best to start from scratch (froyo)
get a clean froyo, root it and install 2ndinit and make a back up so that you can restore the back up to get everything working.
hope this helps!
sUpErwHoO said:
try flashing a stock froyo sbf and then flash your custom rom, i change roms to find something interesting but till now haven't yet faced problems like you.
and also when you are on a custom rom and are planning on shifting to another one, i feel its best to start from scratch (froyo)
get a clean froyo, root it and install 2ndinit and make a back up so that you can restore the back up to get everything working.
hope this helps!
Click to expand...
Click to collapse
I always start from froyo because i had upgrade to 2.3.4 by SBF so i have to..
Now i flashed 2.3.4 again official leaked and no-rooted, and it seems stable..
Could the Rooting being the problem?? :S
Maybe if I flash Argen2Stone again and unroot it right after the flash, solve the problem..
Not that make sense that rooting is the problem but i don't know what else to think.. Maybe a virus? -.^
From what i had experienced ms2ginger 1.0 did have some FC problems. So that must have carried on to this rom. I suggest you wait till they update to ms2ginger 2.0 as base
The problem is not only on Argen2Stone.. :\
WajkIUI was unstable too, giving me FCs on google's framework or something..
Also unstable,as i mentioned earlier, was the nandroid backup of the Official Leaked Rom 2.3.4-134 DFP 74 that was rooted..
Now i'm on 2.3.4-134 DFP no-rooted.. installed by SBF and it's stable for more than 1 day since i flashed it..
:S
Also, when i tryed roms in the past, ex(MIUI, Leaked 2.3.4), they were working like a charm..
After the last flashes i did, the whole FC thing started.. :\
I flashed WajkIUI, Ms2Ginger2.0, then WajkIUI again.. Then started..
On WajkIUI, Framework was stoping all the time and i changed the rom to
the new 109 sbf that i found here.. It's a China.Retail or smthing..
FCs and reboot again.. , so i flashed Argen2Stone to give it a try..
The same, FCs and reboot..
Then i flashed 2.3.4-134 DFP nandroid backup Rooted*, but FCs and reboots again..
Only 2.3.4-134 DFP 74.sbf no-rooted is ok :S
Upon changing ROMs, did you wipe the Dalvik cache? Give it a try.
Always before flashing: Data Wipe, Cache Wipe, Dalvik Cache Wipe.. :\
Pffffff
hey plz help me i get reboots with official roms .
and when i try custom rom i do not get reboots but network gets lost .
i wonder the reboots happen to avoid network loss in official .
plz suggest me one rom which does not reboot and no network loss
I flashed Froyo 2.2 cee and it's stable..
Try this one
On the other stock roms that reboots, you get unexpectedly closed com.motorola.synml...??
and google apps FCs?
2.2 cee also reboots .I think its a hardware issue
Sent from my GT-P1000 using xda premium
Mine Too...
I Think Thats Happening When I Push Hard My Phone..
Especially If I Do Things When Just Booted.. :\
Have U Found Anything?
Good day everyone! I would like to ask for some help if it wouldn't bother.
I previously have WajkIUI 1.10.21 installed on my 2nd init. I have installed the Multiboot plugin (http://forum.xda-developers.com/showthread.php?t=1364659) and installed the CM9 12-2-2012 build on 2nd boot.
However when I updated the 2nd boot to CM9 12-11-2012 build, the 2nd boot stays stuck on the red M logo. Because of that, I installed the "kernel" on 2nd boot which was supposed to boot the build. Unfortunately, it only resulted to a boot loop for my CM9.
When I tried to boot from 2nd init (which still has my WajkIUI), it suddenly stopped booting as well. I tried to recover using my recovery file but to no avail, 2nd init still won't boot.
So my phone's condition now is: it is able to run CWM recovery on both 2nd boot and 2nd init. Will I still be able to boot my 2nd init? Will I still be able to restore to my latest recovery file? If yes, can anyone guide me on how to fix my 2nd init boot?
Thank you very much everyone!
I think its mentioned in the defy cm9 thread.
Its not possible to flash any newer version including 111207 in second Boot.
i think i made the same mistake too...
but i dont know wether i had to reinstal primary boot...
you could try to flash miui on primary boot so that you can do atleast anything...
if you want cm9:
wipe everything
instal cm9 111207.zip
instal cm9 111213.zip
im using cm9 and everything is great, except camera, wich in fact isnt working at all
hope it helped, greetz esok
esok44 said:
I think its mentioned in the defy cm9 thread.
Its not possible to flash any newer version including 111207 in second Boot.
i think i made the same mistake too...
but i dont know wether i had to reinstal primary boot...
you could try to flash miui on primary boot so that you can do atleast anything...
if you want cm9:
wipe everything
instal cm9 111207.zip
instal cm9 111213.zip
im using cm9 and everything is great, except camera, wich in fact isnt working at all
hope it helped, greetz esok
Click to expand...
Click to collapse
Thanks! Now I'm running the Dec13 build
I guess it's about the kernel which messed up. Motorola is so *** for locking the bootloader.
Anyway, thanks again! I'll try to install multi boot again and install Wajkiui on 2ndboot )
arvs0z said:
Thanks! Now I'm running the Dec13 build
I guess it's about the kernel which messed up. Motorola is so *** for locking the bootloader.
Anyway, thanks again! I'll try to install multi boot again and install Wajkiui on 2ndboot )
Click to expand...
Click to collapse
Think this doesn't work either, because of the Kernelchange
but maybe you could post the result of this test.
Would like to install cm7 as second boot, cause of the camera and all my old data
esok44 said:
Think this doesn't work either, because of the Kernelchange
but maybe you could post the result of this test.
Would like to install cm7 as second boot, cause of the camera and all my old data
Click to expand...
Click to collapse
Yes, apparently installing a 2.2 based rom on the virtual system doesn't work (won't get past the M logo again) even when I apply the 2.2 kernel on the virtual system.
So I guess we're stuck on manually choosing our main rom. I also have my data on my older rom (not to mention, app highscores, etc) and I miss my defy's camera, but the ICS rom is so hard to resist.
arvs0z said:
Yes, apparently installing a 2.2 based rom on the virtual system doesn't work (won't get past the M logo again) even when I apply the 2.2 kernel on the virtual system.
So I guess we're stuck on manually choosing our main rom. I also have my data on my older rom (not to mention, app highscores, etc) and I miss my defy's camera, but the ICS rom is so hard to resist.
Click to expand...
Click to collapse
Yeah it is....
AHHHHH damn it.
hmmmm well nevermind, think i will stay with ICS...
titanium backup works, so maybe as a tip for you:
install old rom,
make backup,
install ics,
restore backup,
some data may be back
Yes, I tried that before but for some reason, during restore, Ti force closes on my ICS.
Anyway, I'm fine without my old data for now Thanks Esok
same issue here
did wipe data and cache
install from sd
selected CM7.zip
finding update package
opening update package
opening update package
installing update
done
cynogen mod splashscreen appeared
waited for 20 minutes..and still at splashscreen
what to do ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
any help ?
die2mrw007 said:
same issue here
did wipe data and cache
install from sd
selected CM7.zip
finding update package
opening update package
opening update package
installing update
done
cynogen mod splashscreen appeared
waited for 20 minutes..and still at splashscreen
what to do ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
any help ?
Click to expand...
Click to collapse
try removing the battery. then put it back in and power up. see if it boots up. depending on which cm7 rom you were using, there's a known "stuck in boot" problem and removing battery method will overcome it.
^ Yes, try removing the battery and restarting the phone. One other solution could be applying the 2.2 Kernel after the installation of CM7 (only if you are using Defy and the base ROM of CM7 is 2.2) because I tried installing a CM7 nightly and had to apply the kernel
Kernal
I have a Defy I tried flashing to a few different versions of CM7, but it keeps stopping on the boot logo. I tried flashing from stock, so do I have to change my kernal? If so, how?
phatboyjr said:
I have a Defy I tried flashing to a few different versions of CM7, but it keeps stopping on the boot logo. I tried flashing from stock, so do I have to change my kernal? If so, how?
Click to expand...
Click to collapse
are you saying you were still on stock rom and you tried to install cm7? what was your stock rom and have you flashed any full sbf? what were the steps you did to install cm7?
Yeah, I was running the stock 2.2 and tried installing CM7.
I rooted my phone, then installed 2ndinit boot loader. Wiped caches/factory reset and used CWM to install from a .zip file on the SD card.
No idea how to set up RSDLite..
to install CM7 follow the steps in this faq :
http://forum.xda-developers.com/showthread.php?t=1065798
phatboyjr said:
Yeah, I was running the stock 2.2 and tried installing CM7.
I rooted my phone, then installed 2ndinit boot loader. Wiped caches/factory reset and used CWM to install from a .zip file on the SD card.
No idea how to set up RSDLite..
Click to expand...
Click to collapse
so far so good. could be the rom you were flashing. were you trying to flash the nightlies by any chance? all the latest nightlies do not come with the kernel. you either have to flash the stable release first, or the cm7-kernel-signed.zip, inorder to have the correct kernel before you can flash the nightlies.
do not flash any full gb sbf or you can get yourself in trouble.
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)
Hello there! I really hope you can help me with this, because I don`t have any other ideas or even the courage to try new ones. I recently bought a defy plus and after tens of pages read on the Internet about kernels, SBFs, ROMs and other android stuff I decided to start modding it. It came with a stock 2.3.6 Android, which I swapped for a ParanoidAndroid 2.14 (with Android 4.1.1), which I liked a lot, but I was quite laggy.
Then I decided to look for other ROMs and I wanted to install CM7. But here is my problem: I can`t. I tried to flash this file (cm-7.2.0-jordan), but it didn`t work. Then I had to flash a SBF to get my phone back. I think it was the wrong SBF (filename: JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTTR_P013_A013_HWp3_Service1FF.sbf) because it bricked ( hard brick, I couldn`t even start it), but luckly I had it fixed cause I still have my guarantee (which is a mistery for me, how did they do it? didnt they see it was rooted and this broke the terms of the guarantee?).
Anyway, they re-softed it and now I have a working phone. I rooted it, installed 2nd init and tried again. Now with a nightly version of CM7: cm-7-20130301-NIGHTLY-jordan. It still goes into a bootloop. I went through all the steps, root phone, install 2nd init, Wipe data/factory and Wipe cache and install from sd card.
My first and most important question is: do I have to be on stock android (meaning I have to flash the stock 2.3.6) every time I want to flash a custom ROM? Or can I be on, let`s say ParanoidAndroid, and change directly to CM10?
And my second question: How can I install CM7 for defy plus?
Thank you for your future responses.
Ok, I figured out the CM7 part, I think I was trying to flash a wrong nightly file. I got another one and I finally have CM7 on my phone. But, please, can someone give me an answer to my first question: For every custom ROM I install, I have to go back to stock 2.3.6 every time? Or can I flash, for example a MIUI, right now, on my CM7, without going back to stock rom?
No need to flash stock every time. Data should be wiped along with cache
Sent from my MB526 using Tapatalk 2