Database Users

[SOLVED] ICS Cyber GR mod 5 first boot problem

Hello,
I'm new to custom ROM flashing and I fear something might've gone wrong. I basically rooted my Nexus S (i9020A) and tried to installed CyberGR mod v5 through clockwork recovery (after installing from market) I wiped dalvik cache but deemed it unnecessary to clear data because I had just rooted the phone , everything seems to have gone well, flashed the ROM, phone automatically rebooted, and now I am presented with a colourful boot screen (presumable the mod's one). Thing is, it has been like that for more than 20 mn :s, and I'm not sure what to do now, is this normal?

Hi,
it shouldn't take longer than 10 minutes.
Even though you just rooted your phone, follow the instructions in the OP and everything should be fine.
Go back to CWM, wipe everything and flash it again.
Have fun!

Thank you Kramonte, works perfectly now.
SOLVED

[Q] Is My Atrix Fixable?

My apologies, as I wasn't sure where to post this.
For a long time now I've been running CM7 both the nightlies and the weeklys with no issues. Yesterday I decided I would try Neutrino ROM and installed GT 2.5. After that I noticed I had no data connection so I attempted to patch the ROM using Notorious's recommendations to no avail so I installed 2.2 and the Google addons, Sync, etc..
All was working great, however everyone said 2.5 was better in the forums so I installed it again today and attempted to patch as explained and this time was successful. I had data connection again and all was well. About an hour later I went to use my phone and it was completely black.
I attempted to power it up and nothing happened. I finally had to pull the battery and was able to get it to boot up properly, however my data connection was gone again. I ran the sysctl -p command in terminal again and rebooted it to no avail. I finally decided to go back to 2.2 which worked properly last night, however after installing from the zip and the addon zips it went to the 'Dual Core' screen and then rebooted back to the 'Dual Core' screen and keeps doing that.
I attempted to go into Recovery Mode, however when it says 'Entering Recovery Mode' it just goes black and I can't power it back on. I then have to reseat the battery before I can get it to work.
I guess at this point, is there anything I can do to get my phone back? I've seen the hard brick messages and I don't have that (yet), but I am not sure, because I apparently can't get that far. Thanks for any help you can provide.
-Dave

Sounds like a hardware problem to me. I recommend taking it to a service center ( for me ATT has one I use.) and sometimes they can boot it up. Or they can maybe give you ideas.
Just to confirm you can't boot anything right??
Sent from my Atrix with XDA Premium App

Thanks for the response. I was unable to boot into Android Recovery, however I hadn't tried the others. After numerous searches I found information on how to use moto-fastboot to install RomRacer's Recovery image and after doing that I was able to get into Recovery (phew!). I did a complete wipe on the phone (Dalvik, system, etc) and installed Neutrino 2.2 with Lite gapps, United States (GPS), Sync, and Gtalk (for video) and shockingly it finally booted into the rom. I think at this point I'll leave it alone after restoring my apps via Titanium Backup.
My phone is now working again. Hopefully I can keep it that way.

JeRrYFaR said:
Thanks for the response. I was unable to boot into Android Recovery, however I hadn't tried the others. After numerous searches I found information on how to use moto-fastboot to install RomRacer's Recovery image and after doing that I was able to get into Recovery (phew!). I did a complete wipe on the phone (Dalvik, system, etc) and installed Neutrino 2.2 with Lite gapps, United States (GPS), Sync, and Gtalk (for video) and shockingly it finally booted into the rom. I think at this point I'll leave it alone after restoring my apps via Titanium Backup.
My phone is now working again. Hopefully I can keep it that way.
Click to expand...
Click to collapse
Awesome good to hear. I would change the title or at least add, solved problem
Sent from my Atrix with XDA Premium App

[Q] Team EOS Help needed with latest nightlies

Hi Guys,
I am not sure if I am posting in the right place, but I could use some assistance on the Team EOS nightlies. They won't let me post in the DEV section yet, becuase I am mostly reader, not a poster. Anyway....
I've been running the EOS roms for a while, but I can't seem to run any nightly past 74. 74 runs great, when I tried to update to 75 (rom/gapps/wipe cache) it won't get past the "DUAL CORE" logo. I thought I bricked my xoom, but I am able to boot to recovery, reflash 74 (gapps/wipe) and it boot with no issue. I did a full wipe, and tried again with 76 but no joy (77 wasn't out at the time). I thought it was a problem with n75 and n76. I flashed back to n14 and it works fine, and I can upgrade back to n74. Tonight I tried to update again to n77, but still no dice. I let it sit for 15 minutes at the "Dual Core" logo, and all I noticed is that is got warm, but still no boot.
Any thoughts? All advise is welcome!
BTW, this is for a Stingray 4g xoom
And while I have your attention, I love the work you guys do, and this community, it really makes Android something special!

Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.

Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.

Still not working right, very frustrated, but I have new information
dellenrules said:
Wipe cache, wipe dalvik, flash ROM, flash GAPPS, fix permissions. Do it in that order and you should be fine.
Also make sure your using the latest GAPPS. It should be dated 2012-03-17.
Good Luck.
Click to expand...
Click to collapse
bigrushdog said:
Weird. Try going into fastboot and do a full wipe of userdata, cache, and system. Then install. If need be, do a backup. This will totally wipe your device.
Click to expand...
Click to collapse
Thanks to both of you. I did try this. What I have discovered so far is that some of the flashing fun I have been doing with my may have caused so minor issues with my external SD Card. I backed up the internal to it, and pulled it. I went through the process of nuking the xoom entirely. I.E. Wiped Cache, dalvik, full wipe, factory reset, reset permission, and deleted everything off the internal SD (wasn't in this order, but it all got done) I was able to flash N77, without GAPPS fine. It seemed to run faster with nothing else installed. Rebooted a few times, no problem. I was stoked. I flashed gapps, 03-17 version (the latest). factory reset again so that it was fresh and wiped the cache (just in case). It booted again no problems, ran me through initial config, and then began downloading my apps back. It seemed to run much faster than it ever did before.
Then I rebooted it, without doing any titanium backup restores, just fresh tablet, N77 with my 90 or so apps freshly installed from the market, and it froze again at the "Dual Core" boot screen. I waited hoping for some delayed joy, but none came.
So I went back through the process once again, factory reset, N77 install, wipe cache, install GAPPs. Booted.....initial config, auto downloaded 90 apps from market, reboot......dead.
So then I just flashed N74 again, wiped cache, install GAPPS, initial config, app download.....reboot.......works fine.
<general frustration directed at tablet, not anyone here/>
What gives???? I can't tell what the difference in internal apps in the ROM are that could be conflicting with the ones installed from the market.
Why the hell is N74 working and N77 not, when the apps in both ROMs look the same?
Why does N77 work great when the apps aren't restored?????
Why don't I make a million dollars?????
Why aren't I emperor of the universe???????????????
</general frustration directed at tablet, not anyone here>
Thanks much for all your help!

alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...

I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.

fkntwizted said:
I Would stop dinking around with n77 and go to n90 I had the same issues around those nightly numbers, so I went all the way back to stock... (honeycomb) didn't fix it but I redid the whole install on a higher number and it seems to work itself out..... long story short try another maybe the 1.0 stable by them.
Click to expand...
Click to collapse
He has the STINGRAY not the WINGRAY Xoom.
N77 is the latest for the 4G version. The version he has.
Read the OP

EOS Nightlies hate my xoom, my Xoom wanted CM9 I guess
joshndroid said:
alright.... i have 2 suggestions these may not work and the second one is a pain in the butt to do but it got me out of a jam way back when i lost my softkeys no matter what i flashed
firstly.. in the sequence of your flashing throw in the 'format /system' see if that has any effect it is 'possible' the system is not being flashed correctly or it could be possible that it is getting corrupted and causing the bootloops (i always format system when full wiping)
second... and this is a pain.. but you can always try flashing back to STOCK... there could be other factors that aren't being flashed or fixed correctly causing ya problems... you can then go through the process and flash directly to the latest build... as i noted earlier this fixed a problem that nothing else could for me and has helped others but really this is a last last resort as it takes alot of time and screwing around
lastly... i have no idea sorry these are all i can input.. if possible can always try and use logcat while booting to see what is causing the crash if im not mistaken and upload a log and one of the devs may be able to have a look at it...
Click to expand...
Click to collapse
Thanks much for this. I had already attempted the formatting of everything except the SD card before.....but for sh*ts and giggles I tried it one more time. unfortunately that didn't work.
Using the second option, of reverting stock, I went through sleeplessnija's tutorial on reverting. It really didn't seem that bad, taking me longer to setup my work machine than it did to send the fastboot commands. I was able to get it to boot stock (of course I didn't re-lock it) just fine, and it was quick....so it seems like my hardware is fine.
I used fastboot to put the replacement tiamat recovery, and formatted everything in the mounts menu again. I also mounted my SD card as USB storage and used the full format for it under windows. Then i copied N77 and GAPPS back to it, and re-installed them. It got to the second boot logo (first was the shaking team eos, the second is the square thing with rounded corners that moves). It hung for about 10 minutes, and I shut it off. annoyed.
So I went back into recovery, mounted my SD for USB access from my desktop, and copied the unofficial (which I think is now official) CM9 distro from Team Rogue (Steady's Rom I believe?). I formatted everything, and wiped everything (except the SD) again, and installed CM9 and gapps. Booted fine. Configured account, downloaded 90 apps, rebooted, no problems. Played with it for a while, rebooted....no problems.
I like that my xoom is back up and running......however it seemed that Steadies rom is just a little less fully featured than Team EOS. THAT IS NOT A KNOCK AGAINST TEAM ROGUE OR CM9.....my Xoom is working again (so far) thanks to him (them), and I run CM9 on my AT&T GSII. I just really like Team EOS on my Xoom, and have been with them since the beginning. I would love to know why my xoom suddenly hates the latest nightlies (everything since 74).
Edit: I forgot to ask, Joshndroid.....you mentioned running logcat to see what going on. If it can't boot past the dual core logo or the second boot logo from Team EOS....how do I get the logs? I am not familiar with android's logging.....even though I am a flash-a-holic. I am just thinking that if this is happening to me, maybe I can help out the devs (and myself, and maybe someone else) with the log output.
Edit 2: And Josh.....I forgot to tell you .....good call on the revert to stock answer. I didn't think about that before and thought I was screwed!
Thanks!!

[Q] Rebooting Defy (in a whole new level)

Hi, I've searched my problem but came up only with "regular" reboot answers. Let me explain:
I was using the newest CM10 builds by Quarx as they were coming, and once in a while my phone rebooted/freezed. I was using nightlies so I was ok with that kinda of thing. But after flashing the last nightly (07/03), my phone was rebooting whenever I pushed him harder than opening the app drawer.
After wiping data, cache and everything else without any results, I've decided to flash an official SBF - Then the phone rebooted in the middle of the RSD flash process. I've started it again and it went ok... but now my phone is rebooting at the Moto logo, when I try to wipe the cache or factory reset through bootloader. I can't do anything with him.
Can someone give me any expectation? Something new to try? Or, hell, even a confirmation that my Defy is dead and there's nothing I can do?

SBF
Hi,
draw the battery,
wait a time,
put the battery inside,
start the steps to flash sbf,
after the flashing is finish make a factory reset in stock recovery,
install 2ndint ( i wrote something on the beginning like: After install 2ndinit restart, deactivat usb debug,and restart again),
Then install one of the beautiful CMs here.

cardosy said:
Hi, I've searched my problem but came up only with "regular" reboot answers. Let me explain:
I was using the newest CM10 builds by Quarx as they were coming, and once in a while my phone rebooted/freezed. I was using nightlies so I was ok with that kinda of thing. But after flashing the last nightly (07/03), my phone was rebooting whenever I pushed him harder than opening the app drawer.
After wiping data, cache and everything else without any results, I've decided to flash an official SBF - Then the phone rebooted in the middle of the RSD flash process. I've started it again and it went ok... but now my phone is rebooting at the Moto logo, when I try to wipe the cache or factory reset through bootloader. I can't do anything with him.
Can someone give me any expectation? Something new to try? Or, hell, even a confirmation that my Defy is dead and there's nothing I can do?
Click to expand...
Click to collapse
You just have to flash another rom using RSD lite, It will work.
Or just flash the official ROM which u had before installing the CM 10

Thanks for the attention, but I have tried flashing both his original SBF (Retail 2.3.7 from Brazil) and the Chinese one, both causing reboots when I try to wipe data/cache in recovery. If I let it turn on normally it reboots in the first steps (wifi and account configuration), so I can't even install 2ndinit or wipe data through the system. Any other ideas?

Phone in a freeze+reboot loop on CM14.1, started after turning phone off for a min.

About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.

johnnyrichter said:
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
Click to expand...
Click to collapse
you are on a Beta, it is expected, if you need stability flash CM13

GeTex said:
you are on a Beta, it is expected, if you need stability flash CM13
Click to expand...
Click to collapse
I didn't think it was the rom since I reflashed a previously working version, tried the latest version, performed several full wipes, etc. I'm fetching the latest 13.0 and will get the latest opengapps mini for it and see if that helps.

GeTex said:
you are on a Beta, it is expected, if you need stability flash CM13
Click to expand...
Click to collapse
Rebooted to recovery, wiped everything but externalsd and usbstorage, installed "cm-13.0-20161013-SNAPSHOT-ZNH5YAO21M-kltevzw.zip" and "open_gapps-arm-6.0-micro-20170121.zip", rebooted, went through preparing apps which I don't think it did on the repeated 14.1 installs earlier, now I'm going through my usual setup and app installs with no freezes. Seems like it was a 14.1 issue.
Thanks GeTex.

johnnyrichter said:
Rebooted to recovery, wiped everything but externalsd and usbstorage, installed "cm-13.0-20161013-SNAPSHOT-ZNH5YAO21M-kltevzw.zip" and "open_gapps-arm-6.0-micro-20170121.zip", rebooted, went through preparing apps which I don't think it did on the repeated 14.1 installs earlier, now I'm going through my usual setup and app installs with no freezes. Seems like it was a 14.1 issue.
Thanks GeTex.
Click to expand...
Click to collapse
I figured

If you don't mind answering one more for me...
I'm on OK3. Is there any path to upgrade to a newer firmware while maintaining unlocked bootloader and root, or is it advised that I stick to OK3 and use only the DEV ABOOT roms like I have been?

johnnyrichter said:
About an hour ago I turned the phone off while it was plugged in to my PC charging. I was on CM14.1 20161208 nightly and whatever the newest opengapps ARM 7.1 mini was at the time of that nightly. After 5-10 minutes I turned the phone back on and ever since then it will boot up and I can do stuff or just let it idle for maybe 15 seconds before it freezes and reboots itself. I never had any problems with it prior to this, other than auto-rotate not wanting to work in some cases.
I have tried battery pulls, dalvik/cache wipes, a reflash of that nightly, a full wipe of everything by SDCARD/USB Storage and install of latest 20161225 nightly and latest opengapps ARM 7.1 mini(tried this 3 times so far). Nothing has fixed it.
It's obviously rooted, did the dev aboot bootloader unlock method last year, is on the bok3 firmware.
Not sure what to do at this point. Is the phone trashed?
ETA: It seems the problem goes away if I do a full wipe and install of my rom, but do not install opengapps. Makes no sense, I had no problems with the phone or opengapps before turning the phone off earlier today.
ETA2: After letting it sit for a while, and configuring some settings, I decided to reboot in to recovery and try the latest opengapps arm 7.1 pico to see if that made any difference. After boot it took about 15 seconds for the phone to freeze. Why am I suddenly not able to run opengapps on my phone at all?
ETA3: Fulled wiped and installed rom again. Worked fine until I google-searched for the play store apk, viewed a thread here, clicked on the apk link, and once it should have started downloading the phone froze and rebooted. Working fine now, but it for whatever reason that download trigged the freeze/reboot. Could really use help with this before I'm forced to go out and buy a new phone before I go back to work on Tuesday.
Click to expand...
Click to collapse
i have the same problem and no matter witch custom rom that is 7.1.1 it does the same thing (turns on for 15 seconds, freezes, then reboots, and repeat)

N0rth3rnl1ght said:
i have the same problem and no matter witch custom rom that is 7.1.1 it does the same thing (turns on for 15 seconds, freezes, then reboots, and repeat)
Click to expand...
Click to collapse
My phone ran fine on CM14.1(7.1.1) for at least a month and a half. Not sure why turning the phone off made it stop working with that version. CM13.1 is stable, have you tried that?

Been having the same issues with a 7.1.1 rom Mokee. For the time I've reverted to my S4....
Exact same steps i took. Flashing, wiping, and everything minus external SD.
There is a bootloader update which I did. There is a full update bootloader (I updated and now on PL1) which takes you to Safestrap then back yo TWRP. Others have reported just flashing a PL1 firmware in Odin under AP runs stable.
At this point I'll drop to 6.0 roms, my issues is holding cell service. I can't get any clean flashed rom to give me full data and call service.

I'd like to update firmware/radios if it's possible and won't break my unlock/root and still allow TWRP. Just not sure how to do it properly, starting with my unlocked/rooted BOK3 firmware.