Related
Hello!
I was on the HKTW build as of yesterday. I have Tenfar's recovery and CWM installed too.
I attempted to install Kennith Penn's Alien Rom V2 and it seems like its flashing no problem... However, I get stuck in a boot loop.
I tried restoring to a previous back up , and that loops now too
So, I attempted to flash 2.3.4 Fruit cakes ( http://www.multiupload.com/U1EOJVAKPO ) and it seems that it is flashing it properly, because I got back my stock "AT&T" boot logo (from the factory) but, that goes into a boot loop too...
Can anyone please help point me in the correct direction of getting my device to boot the rom/ image properly? Is there a setting I need to ensure is checked on CWM (like mounts or something?) ... at this point, I cant even boot into Tenfars recovery... just CWM...
This sucks!
Thanks in advance for any help!!!
ssmr2t said:
Hello!
I was on the HKTW build as of yesterday. I have Tenfar's recovery and CWM installed too.
I attempted to install Kennith Penn's Alien Rom V2 and it seems like its flashing no problem... However, I get stuck in a boot loop.
I tried restoring to a previous back up , and that loops now too
So, I attempted to flash 2.3.4 Fruit cakes ( http://www.multiupload.com/U1EOJVAKPO ) and it seems that it is flashing it properly, because I got back my stock "AT&T" boot logo (from the factory) but, that goes into a boot loop too...
Can anyone please help point me in the correct direction of getting my device to boot the rom/ image properly? Is there a setting I need to ensure is checked on CWM (like mounts or something?) ... at this point, I cant even boot into Tenfars recovery... just CWM...
This sucks!
Thanks in advance for any help!!!
Click to expand...
Click to collapse
Bootloops in 99.9% cases means that you need to wipe.
1. Go back into CWM, wipe data / factory reset, wipe cache, go to advanced and wipe dalvik cache.
2. Flash the desired rom.
3. Go into CWM again and do all the wipes again.
And you should boot no probs.
p.s. these 3 steps should your blue print to installing any rom btw. even you want to backup apps - use TB.
thank you for your help....ive actually dome all of that and still no go
ssmr2t said:
thank you for your help....ive actually dome all of that and still no go
Click to expand...
Click to collapse
Have you tried wiping via fastboot?
moto-fastboot -w
p.s. do you have the latest CWM recovery? there can be problems if you arent using the latest one.
xploited said:
Have you tried wiping via fastboot?
moto-fastboot -w
p.s. do you have the latest CWM recovery? there can be problems if you arent using the latest one.
Click to expand...
Click to collapse
+1. i was having the same problem not too long ago and that fixed my problem.
Not sure if this should be in general, so apoligies if I'm in the worng place... Anyway, I was running the first Cyanogenmod nightly and tried to update to the latest. After updating, the phone stuck at the M logo. I can't get into clockwork but can get into stock recovery.
I can sbf, reroot, reinstall gingerbread, and it works fine. whenever I apply the latest cyanogenmod nightly I get stuck on the M logo.
Each time, after sbf I'm doing factory rest and wiping cache at each step. Works right up to the CM part. I also tried sbf, then OTA update, then the CM nightly, same result.
Looking for suggestions on other things to try... I really want to get CM working on this phone again, because I can't stand the stock!!
If you install CM and it boots back up and gets stuck, try going to stock recovery and doing a wipe data and cache and it should boot into CM.
When you install the CM7, make sure the FIRST TIME you are about to boot into CM7 you do a full data/factory reset (with bootloader) not stock, because it will bootloot every time if it tries to boot with the gingerbread settings, and after the first try, i couldnt get factory resets to work from the stock recovery.
droid2master said:
When you install the CM7, make sure the FIRST TIME you are about to boot into CM7 you do a full data/factory reset (with bootloader) not stock, because it will bootloot every time if it tries to boot with the gingerbread settings, and after the first try, i couldnt get factory resets to work from the stock recovery.
Click to expand...
Click to collapse
This happened to me. I'm trying to do this for a friends phone and I am a little unfamiliar with Motorola because I have an EVO. Could you describe the steps for doing a full/data factory reset with bootloader?
The nightlies must be screwed up or something cause I'm having the exact same problem. I can SBF, flash the pre-rooted Gingerbread, and install the bootstrap Clockwork Recovery, but as soon as I flash one of the later nightlies, it's stuck at the Motorola logo with no where to go. Data wipe using stock recovery after words doesn't help at all.
Will be SBF'ing, and re-flashing, then will wipe data and cache while still in Clockwork Recovery and I will report back if this works.
my does the same, I flash back to stock 2.2, OTA to Gingerbread, root using droid 3, install the clockmod recovery, wipe, format, clear cache, install CM7, again wipe, format and clear cache, now it is stuck on M logo. factory recovery won't even give me the option of wipe and clear cache option. Looks like I am going back to stock again without CM7.
My mistake, I've downloaded the wrong kernel, you must get GB CM7 or it will loop.
sangweb said:
my does the same, I flash back to stock 2.2, OTA to Gingerbread, root using droid 3, install the clockmod recovery, wipe, format, clear cache, install CM7, again wipe, format and clear cache, now it is stuck on M logo. factory recovery won't even give me the option of wipe and clear cache option. Looks like I am going back to stock again without CM7. Avoid cm7 at all cost unless someone has a solution to fix this.
Click to expand...
Click to collapse
I'm assuming you guys are installing CM7 version for OTA GB. Simple mistake but I know it happens.
0vermind said:
The nightlies must be screwed up or something cause I'm having the exact same problem. I can SBF, flash the pre-rooted Gingerbread, and install the bootstrap Clockwork Recovery, but as soon as I flash one of the later nightlies, it's stuck at the Motorola logo with no where to go. Data wipe using stock recovery after words doesn't help at all.
Will be SBF'ing, and re-flashing, then will wipe data and cache while still in Clockwork Recovery and I will report back if this works.
Click to expand...
Click to collapse
This is true, dunno why CM Team is not updating the nightlies, I've tried everything, already SBFed to 2.2, updated to 2.3, rooted 2.3, wiped everything, flashed, no go, but boot loop.
I have managed to get earlier nightlies working b4 but it seems the latest nightlies are broken, can someone test them out???
Trust me, I've rooted enough phones to know what to do here (look at my sigs), these CM7.1 D2 nightlies DO NOT WORK!
The worst part about D2 is that you have to start from scratch once you end up in a boot loop, meaning you have to unroot back to 2.2 SBF, update to 2.3, then try flashing, a process that takes about 30 minutes. I've done it all day long yesterday and today, now trying to get some of the older nightlies to work.
i'm helping my co-worker put on CM for the first time and i got this same thing. i dont want to buy her a new phone. how do i fix this? im a long time htc user and so this is all new to me.
I used stock recovery, rebooted, still stuck. I'm having to sbf and I'm even having issues with that. Definitely gonna stick with Liberty until this gets sorted out now.
I Am Marino said:
I used stock recovery, rebooted, still stuck. I'm having to sbf and I'm even having issues with that. Definitely gonna stick with Liberty until this gets sorted out now.
Click to expand...
Click to collapse
I was having alot of issues from not reading and thinking that I had to be on the GB OTA.
I read somewhere that you are supposed to be on Verizon 2.3.20 with sbf then do a factory wipe. Afterwards you root with ADB. Then you use droid bootstrab 1.0.0.5 to install the nightly after factory wiping once more.
I kept thinking I had to be on the latest OTA and I would get stuck on the M every time. Then I ran into the cyanogenmod wiki for the droid2.. Now I am just stuck wondering about overclocking, but at least I have a working cm now
nadcicle said:
I was having alot of issues from not reading and thinking that I had to be on the GB OTA.
I read somewhere that you are supposed to be on Verizon 2.3.20 with sbf then do a factory wipe. Afterwards you root with ADB. Then you use droid bootstrab 1.0.0.5 to install the nightly after factory wiping once more.
I kept thinking I had to be on the latest OTA and I would get stuck on the M every time. Then I ran into the cyanogenmod wiki for the droid2.. Now I am just stuck wondering about overclocking, but at least I have a working cm now
Click to expand...
Click to collapse
After going with sbf nightmare after nightmare and having to buy a new battery, I finally got restored to stock and then rerooted, sticking with Liberty until I can easily flash CM like anything else without all the added steps.
Just recently rooted my s4, was working fine or so I thought, went to flash NamelessROM, I don't think the rom is the issue, I had my s2 rooted and flashed on a weekly basis so I know about wiping, data cache, and dalvik, I flashed Rom then Gapps, and it was stuck on boot up, of course I made a nandroid and restored, but now I'm stuck on the yellow sprint screen, did my research and found it it's called a Yellow Brick, or referred to as. Found out a possible fix was downloading the kernel so I've chosen the Rooted NoData kernel to download and flash via odin. Is this what I should do or is there a better fix out there?
Sounds like you wiped everything. Can you boot into recovery?
Beezer80 said:
Sounds like you wiped everything. Can you boot into recovery?
Click to expand...
Click to collapse
Yes I can, and I tried to restore back from my nandroid which is how I'm stuck on yellow sprint screen now versus stuck on the boot for NamelessROM.
Do a factory reset in recovery and see if it boots.
That will wipe your accounts and what not but you can't boot anyway.
If it won't boot then you'll need to flash a ROM to get running. Do you still have the ROM you wish to flash on your SD card or internal storage?
Beezer80 said:
Do a factory reset in recovery and see if it boots.
That will wipe your accounts and what not but you can't boot anyway.
If it won't boot then you'll need to flash a ROM to get running. Do you still have the ROM you wish to flash on your SD card or internal storage?
Click to expand...
Click to collapse
Just got me stuck on NamelessROM boot up so I'm restoring off nandroid again. I think that flashing the kernel will fix it.
I'd get the ROM booting then play with the kernel. That's just me though.
Beezer80 said:
I'd get the ROM booting then play with the kernel. That's just me though.
Click to expand...
Click to collapse
trying that right now
JosephBallin said:
trying that right now
Click to expand...
Click to collapse
I'm trying to push a kernel through odin, I could possible try to find a way to put a kernel on my extsd and try and flash it through twrp? Would I just have to wipe cache and dalvik and flash? because when I try through odin it fails.
EDIT: I found a fix it involves unrooting most likely, but if I do I'll be back at VPUAMDC (Android 4.2.2) so could I still root with SafeRoot? Or what would be the way to root from that version?
Which firmware version did you root from? If it was MJA or MK2 you have to use one of those, you can't downgrade to MDC easily.
Short Story: My phone works fine when its stock 4.4.4 , no root. If i root it and flash a custom recovery using WUG it gets stuck on starting ups.
Long Story: I was running the latest version of PA, rebooted my phone because of a franco kernel update, and it got stuck on the bootscreen. Tried everything, couldnt get it to boot, so I finally flashed stock using WUG, it worked. I then rooted and flashed custom recovery, and it got stuck on starting apps. Flashed stock again and it worked, repeated the root, and it got stuck on starting apps.
Anybody know whats going on?
wasa67 said:
Short Story: My phone works fine when its stock 4.4.4 , no root. If i root it and flash a custom recovery using WUG it gets stuck on starting ups.
Long Story: I was running the latest version of PA, rebooted my phone because of a franco kernel update, and it got stuck on the bootscreen. Tried everything, couldnt get it to boot, so I finally flashed stock using WUG, it worked. I then rooted and flashed custom recovery, and it got stuck on starting apps. Flashed stock again and it worked, repeated the root, and it got stuck on starting apps.
Anybody know whats going on?
Click to expand...
Click to collapse
You should do a CLEAN install, wipe dalvik / cache / System and Data, the last two ones are very important to wipe, otherwise you got stuck on boot.
It is best to flash your rom using recovery and forget the toolkit, just upload your rom on your N4, get to recovery => install => choose the rom, that's it.
blusydays said:
You should do a CLEAN install, wipe dalvik / cache / System and Data, the last two ones are very important to wipe, otherwise you got stuck on boot.
It is best to flash your rom using recovery and forget the toolkit, just upload your rom on your N4, get to recovery => install => choose the rom, that's it.
Click to expand...
Click to collapse
I did all that before, and it still didn't work.
I think your problems are related to flashing the recovery, did you try to revert back the the old one ?
My OP2 is currently 100% stock, never rooted, and is running Oxygen OS 2.2.1. I have tried OTAing, flashing dirty and clean but the phone itself keeps getting the boot loop logo (Powered by Android screen with the capacity buttons off). I have enabled google apps so I'm not sure what is causing the bootloop. A history of my phone is that on 2.1.0, I tried updating the phone via OTA and I would get "Installation failed" once the entire bar finishes in Recovery. The same thing happened for 2.2.0 > 2.2.1 so I had to dirty flash the phone, otherwise I would get "Installation failed".
I keep a spare file of 2.2.1 off of Oneplus' download site so whenever this boot loop occurs, I turn the phone off and go into recovery > install from downloads > and flash the 2.2.1.
Try this ? http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Djarenga said:
Try this ? http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Click to expand...
Click to collapse
My phone isn't bricked
bump
willy156 said:
My phone isn't bricked
Click to expand...
Click to collapse
Is it, if you can't boot it up.
serkka8 said:
Is it, if you can't boot it up.
Click to expand...
Click to collapse
Hi, my phone is on 2.2.1 fine. but every time i try to update (ota shows me 3.1.0) i get a boot loop
I just tried the 3.1.0 OTA and my phone got stuck on the Powered by android screen. I had to turn the phone off and go into recovery and flashed my 2.2.1 file to unbrick myphone.
try the full rom zip intead of the OTA.
NickRuler said:
try the full rom zip intead of the OTA.
Click to expand...
Click to collapse
with or without wiping data/cache first? I'll try the 3.1.0 full zip file flashing next. think ill try to factory reset after
willy156 said:
with or without wiping data/cache first? I'll try the 3.1.0 full zip file flashing next. think ill try to factory reset after
Click to expand...
Click to collapse
Try it without wiping first. If it works , you wont lose your data.
Edit: If you dont mind losing your data, I would suggest that you use this
http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
This will flash OxygenOS 3.0.2 and restore all partitions to stock.
This should also solve your OTA problems.