Database Users

Can not install ROMs

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

[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?

[Q]Boot err:A5,70,00,00,23

Hallo all.
This is my first post so please have a bit of patience with me.
So I have a Defy MB525 red lens which I had rooted and installed CM 7.1 back when that was cutting edge. As development progressed and updates to CM 9, CM 10 and CM 10.1 became available, I upgraded with no problems.
Last year in Sept messed up a upgrade, compounded the problem and messed up the battery. Order new battery and wall charger for battery. Wait long time for battery (customs problem), at last all is here and fix frozen boot problem. Boot up to installed sbf to find I made more problems by flashing this DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf image. So now stuck with BL 7 and nowhere to go. Found this thread http://forum.xda-developers.com/showthread.php?t=1542956 which solved that problem (my thanks to the devs who sat down and found a way around this problem).
So now my Defy is rooted again, lets upgrade to CM 10 or CM10.1..........
Ooooops so what is this???????
Bootloader 09.10 ERR:A5,70,00,00,23
Every time I try to install I get this error. Every timehttp://forum.xda-developers.com/images/smilies/crying.gif. The only way to fix is to start power button and other finger on Vol+, now bootloader is OK, show no errors. The problem is that I have to start the install and root sequence from scratch using RSDlite 6.1.4, it is very time consuming.
I have searched internet and forums and found quite a few other people with the same error. But no understandable explanation for it, or a way to fix it.
I have tried CM 7.1, 7.2, 9, 10, 10.1 with kernel, without kernel, 2ndint, 2ndboot. No joy.
Is there a fix for it? Or a way around it? On one thread MSGinger 2 was mentioned, I have not tried it yet, but will look into it.
Thanks
It seems I cannot delete this post, could some one please delete it for me? For some reason my Firefox on win do not show the page properly and so I posted twice by accident.
My thanks

[Q] Phone will not start after first restart from a fresh flash

I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.

schmidty455 said:
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
Click to expand...
Click to collapse
Omni clearly states that it is an alpha, so you mileage may vary considerably.
Sounds kernel related. Have you tried just reflashing the kernel and seeing if it'll boot after that. Or trying a different kernel?

Thanks for the reply! I actually just fixed the problem on my own. I used Odin to flash a newer version of TWRP and then flashed omni, and it looks like everything is working just fine. I read a few people saying that they were having issues flashing kit kat roms with older versions of recovery, so I figured it was worth a shot.

Starting Android

Hi Everyone,
I have been on a rooted Android 10 build for the past 2 years, but found the battery was starting to drain quickly, so decided to upgrade to the latest version 11.
I have rooted phones many times, however im a bit stummped.
Initially when i rooted by flashing with Odin, my patched AP file, it would boot loop the start screen, however today i have got further and it boots to "android starting", but after 3 hours it hasnt moved from that point. I cant imagine this is normal\expected? I have tried to reflash a few times and wiped\factory reset before hand, using the main CSC instead of home_csc, but still the same result.
Any ideas? Am i missing something?
Cheers!

If anyone wants to reply with a potential fix for others, then please do, however for now i have managed to obtain root using a method someone else did on XDA.
Basically, i managed to install and run TWRP, then flashed a kernel in that. Now have an up to date phone with root.
Thanks for anyone who looks at this however.