Related
i've flashed CM7, and i reboot it, .. after 15min, the screen is the same, what should i do now?is it normal? i'm getting panic
What screen, if it's HBOOT screen, maybe something wrong in the boot process.
If it's CM7 splash, it was being installed.
use adb and type in "adb shell" and then type "logcat -C", if the log is running, the phone is booting
Funnnny said:
What screen, if it's HBOOT screen, maybe something wrong in the boot process.
If it's CM7 splash, it was being installed.
use adb and type in "adb shell" and then type "logcat -C", if the log is running, the phone is booting
Click to expand...
Click to collapse
i reflashed it, and my WF rebooted again and again, is it normal?
did you try a full wipe (wipe data/factory reset) before reflash ?
as I say, try to go into shell and use logcat, it'll provide you the log process and maybe you will know if there's something wrong
Funnnny said:
did you try a full wipe (wipe data/factory reset) before reflash ?
as I say, try to go into shell and use logcat, it'll provide you the log process and maybe you will know if there's something wrong
Click to expand...
Click to collapse
yes, i wiped my WF before flashing.. sorry i'm just a newbie here, i dont know what is logcat..
my phone freezes now on the cyanogemod screen.. what should i do next? should i wait?
I've been stuck at bootanimation often too... solution: flash hcdr kernel 4.1 before and after installing cm7, reboot system now and that should do it!
Sent from my HTC Wildfire using XDA App
lol8888 said:
I've been stuck at bootanimation often too... solution: flash hcdr kernel 4.1 before and after installing cm7, reboot system now and that should do it!
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
can you give me the link pleaassee?
what should i do?flash hdcr before cm7 right?
should i remove my battery now?
4.2 kernel is fine, but you can flash 4.1 if you want:
http://forum.xda-developers.com/showthread.php?t=798471
flash CM7 first, and then flash 4.1 kernel.
Just wait, the first boot when you flash ROM can very long (around 20min, usablly 5,10min for me)
Funnnny said:
4.2 kernel is fine, but you can flash 4.1 if you want:
http://forum.xda-developers.com/showthread.php?t=798471
flash CM7 first, and then flash 4.1 kernel.
Just wait, the first boot when you flash ROM can very long (around 20min, usablly 5,10min for me)
Click to expand...
Click to collapse
hopes it work.. i'm getting panic here..
am i allowed to connect my charger in case my battery gets low?
the bootanimation shows now..
ijestan said:
hopes it work.. i'm getting panic here..
am i allowed to connect my charger in case my battery gets low?
the bootanimation shows now..
Click to expand...
Click to collapse
my phone is ok now!!! thanks a lot!!!
can you give me some instruction of how can i make battery last? actually this is the reason wwhy i flashed this rom
okay, first try to install setCPU, free for xda member, search in the forum
set the min around 160 or >200Mhz and max ~600 or anything you want.
set 3 profile
Screen off: 160-~300
Baterry<20%: 160-~400 or 500
Temp >45: 160-~400
it'll help because you optimize the CPU use.
turn-off some animation, don't use live wallpaper (CM7 use it by default, so turn it off)
Funnnny said:
okay, first try to install setCPU, free for xda member, search in the forum
set the min around 160 or >200Mhz and max ~600 or anything you want.
set 3 profile
Screen off: 160-~300
Baterry<20%: 160-~400 or 500
Temp >45: 160-~400
it'll help because you optimize the CPU use.
turn-off some animation, don't use live wallpaper (CM7 use it by default, so turn it off)
Click to expand...
Click to collapse
thanks!!! CM7 is soooo awesooommee!!!
how about openvpn?
ijestan said:
thanks!!! CM7 is soooo awesooommee!!!
how about openvpn?
Click to expand...
Click to collapse
do i need to flash the gapps?
ijestan said:
do i need to flash the gapps?
Click to expand...
Click to collapse
If you want Google Apps like Market, GMail etc. Then yes.
Folks,
I was playing around with the roms and BAM
My phone wont start anymore, it keeps hanging on the Android logo from Kyrillos 7.
I tried flashing other roms, but there's no help here...
Help...
Please
May the phone gods be with me........ 8-0
I'm still able to get in the download, so I guess he's not totaly bricked, right????
factory reset from recovery and reboot it might take a while.
RafayelG said:
factory reset from recovery and reboot it might take a while.
Click to expand...
Click to collapse
problem is that it keeps hanging in the ANDROID logo that shines, then suddenly stops, and resets this logo and it all starts all over, very strange...
I'm also able to install the Destiny Rom, and it boots well, but after xxx minutes this version also locks....
I had no problems with K7 OC before (only it locked after restart some days later, that was the prob)
How can I completely reset my phones internal memory?
Could this be unrepairably damaged?
SOLVED !
I can sleep good now !!!!
sorry, I panicked, because I tried several times and nothing worked.
Thanks for the advice !
(can I delete this topic?)
could you explain your solution?
mankokoma said:
could you explain your solution?
Click to expand...
Click to collapse
Of course
I formatted with Pc software at first.
I got many times locked at startup (mostly after installing programs, so the phone needs access to the SD)
I installed K7, then flashed the G3rom into it.
And then, most important:
I formatted the SD card from within the Clockwork Manager CWM.
Of course, this erased both partitions (so make backup), but at least now it works
Do you have similar problems?
no, not yet... but maybe it'll help in future & others & just curious... where's the tnx button in this app?
Sent from my GT-I5800 using XDA
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 everyone.
I got a problem here. As the topic title tells you, I got stuck on the ICS bootanimation. I am running OneCosmic's RC 3.1 and Devil's Kernel. Let me tell you what happened. I raised my Live_OC from 110% to 125%. It froze my phone and automatically boots into CWM after that. And if I turned it on again and got back to the PIN unlocker, it froze again and sends me back to CWM. I did Cache/Dalvik Cache reset, but didn't work. So I figured to reflash the Devil's Kernel which was on my SD card. It didn't work. Then I wiped all the stats and tried again, but it's still stuck on there. I don't know what to fix now. The Devil's Kernel is the only thing I have on my Internal SD card and I cannot reflash another rom/kernel on it. Any ideas how to fix this?
I did not make a Nandroid Backup because I didn't expect this to happen.
You will probably have flash a stock rom via odin and go through the whole rooting and flashing process again. I did a similar thing to you and thats what I ended up having to do. Having a nandroid doesn't fix the problem either, I tried, so don't kick yourself. Just start again
Chileno4Live said:
Hello everyone.
I got a problem here. As the topic title tells you, I got stuck on the ICS bootanimation. I am running OneCosmic's RC 3.1 and Devil's Kernel. Let me tell you what happened. I raised my Live_OC from 110% to 125%. It froze my phone and automatically boots into CWM after that. And if I turned it on again and got back to the PIN unlocker, it froze again and sends me back to CWM. I did Cache/Dalvik Cache reset, but didn't work. So I figured to reflash the Devil's Kernel which was on my SD card. It didn't work. Then I wiped all the stats and tried again, but it's still stuck on there. I don't know what to fix now. The Devil's Kernel is the only thing I have on my Internal SD card and I cannot reflash another rom/kernel on it. Any ideas how to fix this?
I did not make a Nandroid Backup because I didn't expect this to happen.
Click to expand...
Click to collapse
Flash stock ROM using Odin.
You have no other choice.
Livewings said:
Flash stock ROM using Odin.
You have no other choice.
Click to expand...
Click to collapse
No other choice?? If he can enter CWM, he could just use nstools reset zip from nstools thread: http://forum.xda-developers.com/showthread.php?t=1333696 and problem probably solved.
Edit: I'm assuming he's using nstools to liveOC (as I don't even know other apps for that ATM).
Edit 2: I just examined that reset script and it might not work since mounting should be little different (at least in my phone ).
But you could also just mount data in CWM and use adb shell to delete that preferences file (look correct directory from that reset.sh)
Sent from my sandwiched SGS
Or if you have glitch kernel on your phone flash that.
It has built in ns tools cleaner
Sent from my GT-I9000 using XDA App
Het Guys thanks for replying. I fixed IT myself by reflashing The devils kernel. I got to the installation wizard but IT kept force closing so i couldn't Get in. I tapped The four corners toe skip The installation wizard, reflashed onecosmic rc3.1 and then devil kernel. Now it is working
Thanks for the solution via odin though. I Will keep IT in mind.
Thanks
Verstuurd van mijn GT-I9000 met Tapatalk
Hello, this is my first post here and I have searched for a similar post or issue but have been unsuccessful finding anything.
Please forgive me if I have posted in the wrong area, missed a solution somewhere and/or have not explained anything correctly/clearly.
My Nexus 7 (2012) (I installed Cyanogen on it (and updated it once) through their installer and it has run perfectly for months) started rebooting randomly one morning. I turn it on and it seems to be normal, then it will suddenly reboot. The time between reboots varies ranging from 30 seconds to a few minutes. I can not install or update any apps and any settings changed are reset back to what they were previously upon reboot. I have tried a factory reset and while it appears to wipe everything (all caches and data) when I reboot it is the same as before the reset (I also receive this message (after all other processes are complete) during the data wipe "E: unknown volume "/sdcard/.android_secure" "). I am able to turn on developer options but then the random reboot occurs and it is turned off. I have plugged it to my computer and see it listed, but can not access anything on it.
My intention is to wipe it using my computer (fastboot?) but I am at a standstill due to the rebooting and being unable to turn on developer options.
Any ideas or suggestions would be greatly appreciated.
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
kcipopnevets said:
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
Click to expand...
Click to collapse
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
pdn190 said:
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
Click to expand...
Click to collapse
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
kcipopnevets said:
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
Click to expand...
Click to collapse
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
pdn190 said:
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
Click to expand...
Click to collapse
You can always try. Also make sure you check md5 before flashing, that may explain why stock didn't flash correctly.
And I still can't get anything to work. Most recently I tried using wugfresh and EVERYTHING works except when it writes bootloader.img at the start. I feel like I am close but then it reboots back to cyanogen. lol