Can not install ROMs - Huawei Ideos X5 U8800

Here are my problems:
1st and more important most roms wont boot in my u8800pro. I started with official 2.2.2 that came with the phone. I rooted the phone and installed recovery 5.0.2.7. Later I decided to try a different rom. I downloaded CM 7, kalo's, ics, MIUI (both gingerbread and ics). I installed CM7 first. After the update finished I rebooted the phone. It got stuck on the CM start/splash screen. Rebooted and the phone run. Unfortunately it kept powering off or rebooting on its own.
After that I tried all the other gingerbread ones. All of them get stuck on the start/splash screen. The one after the huawei flower thing.
All of the ICS ones load but I get no network for some reason.
Just to point it out I wiped data and cache and calvik everytime and I followed the instructions I found in the roms forum posts.
Atm am stuck with CM 7 and the random power off/reboot issue.
And that is problem no2. I dont mind using CM 7 if that can be fixed.
Any suggestions welcome

Well I managed to install stock 2.3.5 using the instructions in the #9 answer of this post http://forum.xda-developers.com/showthread.php?t=1405375&highlight=cm7+reboot+problem

Related

[Q] Installing Virtuous Fusion

Hey everyone.
I would appreciate some help or suggestions. Maybe someone will know the problem, which I can't seem to figure out. First thing first, I couldn't post in the release thread because I don't have the proper post count.
Anyways, I am not new to installing ROMs on my phone. I can install and run CyanogenMOD easily, and have done so many times. My phone is rooted. So I went from the stock ROM on the MyTouch 4G to CyanogenMOD 7, with no problems. I used it for a while, and then when I saw Virtuous Fusion come out, I wanted that installed. I had tons of trouble getting it to work, even though I was doing everything I was supposed to do. Reset my phone, cleared all caches and data, pretty much cleared everything out. I tried installing from the zip several times in clockwork recovery, and it wouldn't get me past the boot screen. The boot screen would either loop forever, and never get past it, or the boot screen would load up for 3 seconds and then the screen would go completely black (in a state where it looked like the phone turned off).
Eventually, after about the 10th install (which were done all the same exact way), the Fusion ROM decided to work on me and everything went perfectly. This was the first day it was released. I saw the ROM has been through some updates, so I decided to do the recommended clean install of the new version. I am having the same problem as I did before with the boot screen. I temporarily flashed Cyanogenmod so I can have a working phone again, but I would really like to be on Fusion. My favorite ROM out of all the ones I have tried. Does anyone know what could be causing this?
What version of ClockworkMod are you using? Make sure you're on 3.0.2.4 to insure ultimate reliability. Also verify the MD5 hash that eViL provides before flashing. Not doing so means you could have any number of problems caused by a corrupt file download.
Are you rebooting into ROM MANAGER. This ROM is not suppose to be loaded while in the Android OS.

[Q] Nexus 7 boot problem-kernel/rom issue

Hey there! I was updating my version of Paranoid Android and my kernel and it seemed fine at first but It yield some odd problems. I went into Clockworkmod recovery and Flashed my rom and kernel I then proceeded to wipe my cache and dalvik cache. I have done this many times before on many devices. I encountered a problem when I rebooted for the second time, I got the Android is updating apps display and I continued to get it every time I booted. The device would also randomly turn off when the screen dimmmed. I proceeded to set out and fix it. Here are the steps I took and the problems it caused.
Flashed stock rom-would not boot properly
Flash RESET kernel-I messed up and though this was a real kernel, my problems escalated from here.
Flashed stock rom and recovery.
Flashed reset kernel and then real kernel-Still had problems.
Flashed stock rom
My problems from all this accumulated somewhat and I can barely boot into fastboot. I get weird static screens and weird white noise sounds. It does not always let me boot into android and will get to the google logo 1 out of ten tries.
These is really unnerving and I have no clues whats what.
Note: I am using Faux123's kernels and his reset kernel.
Thanks a lot for any help!!!

[Q] Help! Quarks CM10 does not boot

I tried loading the latest build (CM10 11/28) onto my defy. I completely forgot to load gapps afterwards and went ahead and rebooted. Now, it gets stuck on the cyanogenmod logo and does not boot past that. The only thing I can do is remove the battery. When I reboot, the same thing happes. Unfortunately, I no longer get the boot menu so I can't even run recovery from my backup.
How can I fix this so I can use my phone again?
atlcr said:
I tried loading the latest build (CM10 11/28) onto my defy. I completely forgot to load gapps afterwards and went ahead and rebooted. Now, it gets stuck on the cyanogenmod logo and does not boot past that. The only thing I can do is remove the battery. When I reboot, the same thing happes. Unfortunately, I no longer get the boot menu so I can't even run recovery from my backup.
How can I fix this so I can use my phone again?
Click to expand...
Click to collapse
Nevermind...apparently pressing vol. down when the LED flashes blue gets me to a boot menu. Pheww!
Got it loaded, but having several problems: cannot connect to Play store, cannot receive phone calls, and email is spotty.
Please ask all questions in Q&A. Thread moved there.
atlcr said:
Got it loaded, but having several problems: cannot connect to Play store, cannot receive phone calls, and email is spotty.
Click to expand...
Click to collapse
Your Gapps not working correctly, probably you installed incorrect ones, I recommend you to repeat the whole process:
1 full wipe x2 (you loose data so if you have data ensure yourself a backup)
2 flash stock sbf with rsd lite
3 root your phone
4 install 2ndinit
6 install cm10 from custom recovery
7 full wipe again
8 boot phone at least once
9 install quarx minimal gapps (thats your actual problem, your gapps not working correctly)
10 wipe again
11 restore backup if any.
3ze said:
Your Gapps not working correctly, probably you installed incorrect ones, I recommend you to repeat the whole process:
1 full wipe x2 (you loose data so if you have data ensure yourself a backup)
2 flash stock sbf with rsd lite
3 root your phone
4 install 2ndinit
6 install cm10 from custom recovery
7 full wipe again
8 boot phone at least once
9 install quarx minimal gapps (thats your actual problem, your gapps not working correctly)
10 wipe again
11 restore backup if any.
Click to expand...
Click to collapse
I don't think he has to flash the sbf, just flash gapps n wipe data n cache. also try dalvik cache
Sent from my MB526 using xda premium
You could simply install a new .zip from recovery. You could use the same CM10 11/28 or any other rom. This shoud work out for you.
I experienced the same with my Defy today and I installed a new CM 10 09/05 by Epsylon and it worked like a charm.
Thank you for the replies!
I had to flash it a hundred times to get it to work (I kept getting write access errors for cache folder). What ended up working was to wipe everything and install the 9/24 build. From there, I rebooted and installed (without wiping) the latest build along with the correct gapps. It works fantastically now! My phone is soo much more responsive and I'm loving CM10.
3ze had it right. I was using the latest gapps (12/2) instead of the "minimal" version in the quarx dir.
I haven't noticed a battery drain as has been widely reported here. In fact, it seems to be less of a drain now though that is likely due to the fact that I wiped everything and only installed apps I needed this time around. Tons of unnecessary apps could explain why my battery life was less before.
I have noticed a slight difference in reception now though. Places that used to be fine for connecting to the network (Tmobile) have now become less strong and frequently dropping out. I wonder if the signal strength could have been messed with?

[Help] GT-7510 wifi froze after working fine and rebooting continuously

I successfully rooted my Tab from ICS to JB 4.1.2 a few days ago and it has been working fine. It suddenly froze in GMail app this evening. Held down power and attempted reboot. All fine until several revs of the CyanogenMod circle then it froze for a few seconds and then blank screened and rebooted with the Samsung Galaxy Tab 10.1 logo before going back to the CyanogenMod circle. Only stops the looping if I power from the mains. Battery is at about 55% and charging.
I have CWM-based Recovery v6.0.1.5 and I installed JB from cm-10-20121112-EXPERIMENTAL-p4wifi.zip
Can anyone help? I'm new to rooting etc..
Many thanks,
Stuart
Try booting into recovery and doing a full wipe of everything.
Sent From My GalaxyClass StarShip
Thanks
SouthPhilly said:
Try booting into recovery and doing a full wipe of everything.
Sent From My GalaxyClass StarShip
Click to expand...
Click to collapse
Many thanks for the reply SouthPhilly. It didn't work
There seemed to be a problem with formating /data. It just stopped when I tried it. Also stopped if I tried restore. The good news is that I did eventually overcome the problem by following qbking77's excellent info on
How to Unroot / Unbrick the Samsung Galaxy Tab 10.1 - Latest at www dot youtube dot com/watch?v=KYBs98R9rTs with file info at
www dot qbking77 dot com/samsung-galaxy-tab-1012.html
which results in a stock original unrooted GT-7510. From there I rooted back into CWM recovery and reflashed CM10 so I'm back with a working version of 4.1.2
I hope this info may help others unfortunate enough to get stuck like me.
I'm now happy again.
Best wishes to all.
Stuart G3SNA (QTHR)
Well perhaps not quite so happy!
For some strange reason I could not get the USB port to work. It did with my first attempt at flashing to CM 10 - JB 4.1.2 days ago but not now. I have tried all ways several times so eventually I returned to the qbking77 version of the stock 3.2, copied my CWM backups back to the sdcard, then reinstalled CWM recovery and restored from the backup. I now have what appears to be a fully working tab with USB connectivity running 4.0.4 ICS again. I'll stay with this untill JB gets a bit more stable. You never know, pink pigs may fly and Samsung may issue an OTA update :laugh:
Why didn't you flash a nightly instead of a ROM thats dated last month? The latest one runs fine on my p7510
http://get.cm/?device=p4wifi
Sent from my GT-I9100
I didn't know where to find the nightly files when I first did the root and rom flash. I just followed the links I could find using google. The whole thing looked good to start with and I ran it for the best part of a week before it froze up on me. I learned a lot in the last few days and now feel confident in what I'm doing. I did download last night's nightly this morning and flashed the rom. When I connected the usb cable to my pc failed to connect so I reverted to my original zip file thinking the nightly had an issue. Low and behold the usb cable connection failed with this as well. In both cases I did all the wipes and formats just like the first time. After that I gave up and decided to try to put my Tab back to ICS using the CWM backup I made as recommended before I started the first time. I'm no novice as far as computing is concerned but I haven't rooted an android device before.
If you take a look around the forums here you will find I am not the first to fail to find the nightly files. Perhaps a sticky with the link would be useful?

Frustrated! Soft bricked?

I was running Liquidsmooth 2.9. Wanted to try out the newest leak from Liquid running KitKat.
Downloaded everything, new gaps, etc. Went to install and received a (Status 7) error twice. Updated o the latest TWRP and tried again.
Received the (status 7) again, tried one more time for good measure and it worked.
Immediately noticed that this build was not stable or suitable for a daily driver and tried to go back to my previously made backup.
For whatever reason it wasn't recognized in recovery even though I could see it when navigating in the files.
I tried desperately to move the back up so it could be recognized but to no avail.
Decided to just download the official 2.37 build of Liquidsmooth and the old gaps and reflash. I have done this now three times successfully but
can't get past the splash screen.
Back up isn't working, flashing rom isn't working, now I'm stuck with a soft bricked device and getting extremely frustrated. What is my next move?
1967ls2 said:
I was running Liquidsmooth 2.9. Wanted to try out the newest leak from Liquid running KitKat.
Downloaded everything, new gaps, etc. Went to install and received a (Status 7) error twice. Updated o the latest TWRP and tried again.
Received the (status 7) again, tried one more time for good measure and it worked.
Immediately noticed that this build was not stable or suitable for a daily driver and tried to go back to my previously made backup.
For whatever reason it wasn't recognized in recovery even though I could see it when navigating in the files.
I tried desperately to move the back up so it could be recognized but to no avail.
Decided to just download the official 2.37 build of Liquidsmooth and the old gaps and reflash. I have done this now three times successfully but
can't get past the splash screen.
Back up isn't working, flashing rom isn't working, now I'm stuck with a soft bricked device and getting extremely frustrated. What is my next move?
Click to expand...
Click to collapse
Wrong thread buddy
Lol
Retail N3

Categories

Resources