Database Users

Phone hangs on Dual core logo, need help

I had CM7 installed on my phone, and then i proceeded to update to the beta 2. I downloaded the file, then unpacked it on my phone sdcard then proceeded to reboot in recovery mode and cleared cache , dalvik, factory settings and then updated the zip file. then clear everything again and reboot. Get stuck on dual core logo.
I can still access recovery and mount usb to add files. can anyone tell me how to fix this?

did you make a backup before installing the beta?

It seems like you've never installed a ROM before, so I would advise you to read before you try again.
Try and restore it from the 1.8.3 SBF or restore from the CM7 pre-beta2.zip.
Don't unpack the zip file.
Oh and I feel obligated to ask, but did you install romracer's recovery?

I have Tenfar's recovery. Does it matter?
When you say restore, do you mean going in recovery mode and then apply the beta-update2.zip?
I also beleive my recovery got updated to Clockwork's when I had CM7 beta installed?
I have read another post on here that suggest I should RSD flash the 1.8.3 SDF and just start anew.
Should I do that? I was on 1.8.3 prior to installing CM7 beta

I understand I probably come across as a complete noob, but I did read before I did anything.
And now this happened and I just need help fixing it, you can just say. Yes flash back to 1.8.3 with RSD, I don't need a dot point instruction on how to do that.
Now my recovery is "ClockworkMod Recovery v4.0.1.4" even tough i originally flashed Tenfar's
and my phone is unlocked.
I have tried many times to clear all caches and update the beta zip again and it does not work, I just get stuck on dual core logo again.
Thanks in advance for any help.

Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.

quicklyspent said:
Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.
Click to expand...
Click to collapse
Legend, thanks a lot now I can go back to sleep.
I installed romancer's recovery (unlike tenfar's it took like 5 times longer to clear cache and install the rom) but it did work.
thanks for taking the time man.

I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk

Rayan said:
I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk
Click to expand...
Click to collapse
No I had wiped dalvik and cache prior and after update.
Either beta 2 doesn't like tenfars recovery or it was an issue with the download . Since I installed romancers recovery before I tried the new download we will never know
Sent from my MB860 using XDA Premium App

Why use tenfar's recovery when you can use CWM real recovery now.
That might help a lot...

im having the same problem but i used romracers recovery in the first place. ive tried everything and i tried to restore my alien backup but the recovery cant find it... did prebeta1 change the directory? im lost.

Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk

Magnetox said:
Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Click to expand...
Click to collapse
i tried that before and it didnt work.
edit- i found how to mount phone as usb in recovery. going to try the whole process again. i think my file was corrupt.
edit-- still cant get it to work even after redownloading teh file...

Flashing Rom always ends in boot loop?

I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.

By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app

redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm

could that be the problem? that my cwm is just outdated already?

No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium

CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.

Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7

am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?

crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.

simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?

I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?

spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?

Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.

dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?

If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2

Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!

Liquidsmooth (can't turn on now)

I was use a nexus4tookit v1.3.0 to root my nexus 4 , however I was download a Liquidsmooth and install from sdcard , but now the mobile cannot open , just load in liquid-smooth logo screen, what can I do now? My nexus 4 is JOP40D , Thanks a lot.

You may have a bad download. Check the md5 sum or re download it and try flashing it again.
Sent from my Nexus 4 using Tapatalk 2

Restore the backup you should have made in recovery before you flashed anything.
Hold down power for ten seconds to reboot, then hold volume down to enter boot loader. You can get to recovery from there.

First off. You shouldn't be using a toolkit, they get you from Point A to Point B. But now you are trying to backtrack because your phone won't boot. This is why people shouldn't use toolkits, you are getting to Point B without knowing what you're doing.
Is it stuck at the bootanimation screen? Did you wipe factory settings when flashing the ROM?

estallings15 said:
Restore the backup you should have made in recovery before you flashed anything.
Hold down power for ten seconds to reboot, then hold volume down to enter boot loader. You can get to recovery from there.
Click to expand...
Click to collapse
I already unlock the bootloader ， but I can't enter to boot loader now , just can enter to recovery mode or restart boot loader ,power off or start.:crying:

cf017 said:
I already unlock the bootloader ， but I can't enter to boot loader now , just can enter to recovery mode or restart boot loader ,power off or start.:crying:
Click to expand...
Click to collapse
If you can get into recovery, you're fine. Is this your first Android phone? Your first step after rooting is always to make a backup.
Anyway, flash Franco's kernel. It plays well with liquid smooth. That should fix you up. You will figure out how if you STOP PANICKING and try.

estallings15 said:
If you can get into recovery, you're fine. Is this your first Android phone? Your first step after rooting is always to make a backup.
Anyway, flash Franco's kernel. It plays well with liquid smooth. That should fix you up. You will figure out how if you STOP PANICKING and try.
Click to expand...
Click to collapse
and not use toolkits! take the 15-25 minutes to read whats going on and not click one button to do it all for you
that's why OP is panicing because he didnt manually do it, a toolkit did it for him.

Post sent in error apologies

bash156 said:
Hi I hope you don't mind me messaging you I just noticed your last post that we should use toolkits for our phone can you please tell me what is the best way to do it I apologise for asking this is my first android phone and I'm realising that battery life is crap and I've been reading about people making changes to make their battery life live longer
Regards
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
We should use toolkits? I never said a thing about using them. The best way is to NOT use them. If this is your first android phone, it is IMPERATIVE to know simple ADB and Fastboot methods so you won't fall into the common errors when people use toolkits getting them into things they don't understand.
http://forum.xda-developers.com/showthread.php?t=1972508 is a guide to get started after you boot up, you can then proceed to go into the Original and Android dev forums to select your ROM / Kernel that you desire. I'd recommend CM10.1 (jellybro) + Franco Kernel R20. --- so after unlocking bootloader. Put the ROM, Gapps, Kernel on your phone storage using USB cable.
Use computer --- ADB... "adb reboot bootloader"
fastboot flash recovery <nameofrecovery>.img (download TWRP or CWR and put it in same folder as fastboot /platform-tools/ most likely)
boot into recovery (use volume up/down to navigate then power to enter)
wipe factory settings,dalvik,cache
flash rom then gapps then kernel (gapps and kernel can be reversed up to you)
then reboot.
done.

Apologies I meant that we should not be using tool kits my bad
Sent from my Nexus 4 using xda app-developers app

bash156 said:
Apologies I meant that we should not be using tool kits my bad
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
He answered your question with great detail. Hit the thanks button.

bash156 said:
Apologies I meant that we should not be using tool kits my bad
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No problem. Just read what I said above, if u have any questions, feel free to ask. It's a very straight forward guide on how to unlock your bootloader. The stuff thats not included in there would be:
- Download ROM, Gapps (optional depending what rom you use. the rom says whether its included or not, if it doesnt say assume its in there), kernel (optional but recommended u switch --- upon flashing a new version u will need to reflash the kernel)
- Flashing Custom Recovery while in Bootloader Mode (which I said in my post on how to do.. basically download TWRP or CWR [you choose, i recommend twrp] and put the .img folder in the same folder as fastboot.exe)
- Use vol up / down to go to recovery in bootloader mode (it says the text on the phone)
- Wipe factory
- Flash ROM, Gapps, Kernel (gapps and kernel order doesnt matter. ROM goes first)
- Reboot to system
..... done.
edit: yeah what estallings said thanks given.

Thank you very much for your help I'm going to try and unlock the bootloader now I'll let you know how I get on to back everything that's on my phone already can I just sync to my Google account
Sent from my Nexus 4 using xda app-developers app

sorry to bother you again thanks to you I have now unlocked bootloader but im finding it confusing on what to do next I havent managed to find the cm 10.1 and franco kernal you talked about is there a link somewhere for them

bash156 said:
sorry to bother you again thanks to you I have now unlocked bootloader but im finding it confusing on what to do next I havent managed to find the cm 10.1 and franco kernal you talked about is there a link somewhere for them
Click to expand...
Click to collapse
Original development.

bash156 said:
sorry to bother you again thanks to you I have now unlocked bootloader but im finding it confusing on what to do next I havent managed to find the cm 10.1 and franco kernal you talked about is there a link somewhere for them
Click to expand...
Click to collapse
CM10.1 Jellybro: http://forum.xda-developers.com/showthread.php?goto=newpost&t=2015081
Franco Kernel: http://forum.xda-developers.com/showthread.php?t=2002782
Download CM10.1 Jellybro + Gapps + Kernel R20.

zephiK said:
CM10.1 Jellybro: http://forum.xda-developers.com/showthread.php?goto=newpost&t=2015081
Franco Kernel: http://forum.xda-developers.com/showthread.php?t=2002782
Download CM10.1 Jellybro + Gapps + Kernel R20.
Click to expand...
Click to collapse
Hi I did everything you said I flashed the cm10 gapps and kernel now its stuck on the cynogenmod logo I went back to recovery wiped everything and tried to flash cm10 and the rest again and still stuck on the cynogen mod logo have I done something wrong because I dont have anything backed up

bash156 said:
Hi I did everything you said I flashed the cm10 gapps and kernel now its stuck on the cynogenmod logo I went back to recovery wiped everything and tried to flash cm10 and the rest again and still stuck on the cynogen mod logo have I done something wrong because I dont have anything backed up
Click to expand...
Click to collapse
When you mean wipe everything... just factory settings, dalvik, cache right?
- Wipe Factory, Dalvik, Cache
- Flash CM10
- Flash Gapps
- Flash Kernel
- Reboot.

zephiK said:
When you mean wipe everything... just factory settings, dalvik, cache right?
- Wipe Factory, Dalvik, Cache
- Flash CM10
- Flash Gapps
- Flash Kernel
- Reboot.
Click to expand...
Click to collapse
I always wipe system as well. I used to not do that, but I found less phantom issues appeared if I wiped system.

estallings15 said:
I always wipe system as well. I used to not do that, but I found less phantom issues appeared if I wiped system.
Click to expand...
Click to collapse
Interesting. First time I've heard this, I will have to try that sometime although for the last year I've been pretty content with CM + Franco set up. Maybe when a new version of Android comes out, I swap over to that AOSP ROM for a little while but once CM is set, im moving.

AOKP rom

So i got my nexus 4 yesterday and Ive always wanted to root an android phone and install a custom rom. So i unlocked the bootloader and rooted it pretty easy. I want to flash AOKP rom. i downloaded the rom file and google apps from their website on the phone. I went into CWM recovery and installed those files from the sd card, and it says its complete. I reboot the device and it just sits on the nexus logo screen. I dont know what i did wrong. Anybody got any ideas

It's normal for it to sit on that screen for about a minute or so.. How long did you give it?
Sent from my Nexus 4 using Tapatalk 2

capcanuck said:
It's normal for it to sit on that screen for about a minute or so.. How long did you give it?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
3-4 minutes

make sure you have the correct files for your N4 or "Mako" device and that you did the steps properly.
wipe data/factory reset in recovery
flash ROM
flash Gapps
reboot

thatguyzx said:
make sure you have the correct files for your N4 or "Mako" device and that you did the steps properly.
wipe data/factory reset in recovery
flash ROM
flash Gapps
reboot
Click to expand...
Click to collapse
yeah im pretty sure i did that all correctly, but ill try again. Also for some reason when i try to boot into recovery sometimes, instead of going into CWM, it shows the android robot open with an exclamation mark on him. Any idea what that is

^
I believe that the stock recovery...
When you first boot cmw, it does not stay permanently afterwards...
You can flash it again by downloading ROM manager??
Or somthing else..

Maybe use adb+fastboot to flash ROM..
Just to try if the files aren't broken.
Sent from my Nexus 4 using xda app-developers app

MarcPlusTwo said:
Maybe use adb+fastboot to flash ROM..
Just to try if the files aren't broken.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can't flash a ROM in fastboot, you can only flash images.
You can flash the recovery image through fastboot.
I would let it sit for more than just 3-4 minutes as well.

thatguyzx said:
make sure you have the correct files for your N4 or "Mako" device and that you did the steps properly.
wipe data/factory reset in recovery
flash ROM
flash Gapps
reboot
Click to expand...
Click to collapse
Maybe I'm wrong, but I think you have to format /system and format /boot when switching from another rom, otherwise it bootlops.

trillo69 said:
Maybe I'm wrong, but I think you have to format /system and format /boot when switching from another rom, otherwise it bootlops.
Click to expand...
Click to collapse
Unnecessary.

Surprised no one has suggested this already. This happened to me before, go back into recovery and wipe davlik cache
Sent from my Nexus 4 using xda app-developers app

Curious about failed ROM flash

So I decided to flash slim 4.4 on my d800 and it failed using twrp 2.6.3.2(?). I had the options for home, reboot system and something else. I elected to reflash the ROM that I'd been using, as I was hesitant to reboot system knowing that a flash had just failed. My question is, if I had chosen to just reboot system, would it have rebooted to the ROM I had been using prior to attempting to flash? Noob question for sure, but this was my first failed attempt at flashing. Thanks.
Sent from my LG-D800 using Tapatalk

thestrangebrew said:
So I decided to flash slim 4.4 on my d800 and it failed using twrp 2.6.3.2(?). I had the options for home, reboot system and something else. I elected to reflash the ROM that I'd been using, as I was hesitant to reboot system knowing that a flash had just failed. My question is, if I had chosen to just reboot system, would it have rebooted to the ROM I had been using prior to attempting to flash? Noob question for sure, but this was my first failed attempt at flashing. Thanks.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
No
Thanks Devs. From my VZW G2.

You'll be stuck at LG logo or at rom bootscreen forever

Best thing to always do in that situation is to just restore your BU and try redownloading the ROM. Or wipe and flash something else(working obv lol). Sounds like a bad DL to me
Sent from LG-LS980

bearsblack said:
Best thing to always do in that situation is to just restore your BU and try redownloading the ROM. Or wipe and flash something else(working obv lol). Sounds like a bad DL to me
Sent from LG-LS980
Click to expand...
Click to collapse
That.
Or if you dont have BKP >
choose boot into recovery.
WIPE EVERYTHING (factory + sys + dalvik + cache)
install rom
WIPE EVERYTHING (factory + sys + dalvik + cache)
reinstall ROM
install gapps
boot

OK cool thanks everyone. Glad I didn't mess anything up last night lol
Sent from my LG-D800 using Tapatalk