I was on CM7 for sometime, but got into problems and thought about "restarting" the device.
So i flashed Argentinian 2.3.6 stock (4.5.2).
However I forgot to Wipe data and now it seems I'm in bootoop.
However I cannot boot into stock recovery. Using Power+R+M till M logo boots the OS and if I keep the button pushed for longer, it just... boot Android... however it takes longer to move from M logo to M bootanimation.
Any idea?
I know it's abandoned forum, but maybe there is someone here?
PS. Flashed it already few times.
Is there any other way to Wipe? ADB or Fastboot?
Related
Hello.
Just yesterday, I installed CM 7.1 on my Defy, which was on stock froyo. It started up normally, and was working perfectly, until I had to reboot it, in order to get the google apps, when it went into boot loop.
I've tried going into stock recovery and wiping the data/ factory reset and wiping the cache, but even then it's stuck on boot loop on the CM 7 logo. What should I do?
Ps. It's the Indian Defy, which is without Blur, if that makes any difference.
EDIT: Just got it to work, I flashed the stock Froyo SBF using RSD lite. I think my mistake was installing Clockworkmod on it, because it has it's own custom recovery. Can anyone tell me how to get into it?
Ya installing CWM on top of CM7 will screw up the pre-installed Custom recovery. While the phone is just starting to boot watch for a blue LED to flash at the top of the phone. Right when it flashes blue, press volume down. From here use your volume rocker to select recovery, use the power button to make your selection. Next choose custom recovery.
Thanks mate
Though sadly, after rebooting it, it keeps on showing the message - process com.android.phone has stopped working, and I get no network. What do I do?
Wipe data and install the zip again...
Sent from my MB525 using xda premium
Guys I know there are a ton of threads with this problem but no matter what I try, i'm still stuck on a boot loop.
So basically I had PA Rom 3.99 RC2 on my nexus and everything was fine. I then tried to flash PA AOSP kit kat build
but my phone would not boot so I went with a factory image occam 4.3 Phone booted and all was good. I was liking the
stock experience and then about 4 days later after a reboot, phone got stuck on the boot animation X. It would not get out of it
so I decided to flash PA Rom 3.99 rc2 again via ADB push zip. factory reset, installed the rom and gapps, wiped caches and thought i was good to go. Well the phone again would not get past the boot animation of PA.
i then decided to go with the Factory image occam 4.3 via fastboot and installed it and everything. Again stuck on the X. So then I tried PSX rom 4.3 again via adb push, did my factory reset and flashed the rom and gapps and superSu. Also got stuck on the boot animation. Left it for over 2 hours bootlooping and nothing.
Going crazy I went and fastboot the 4.2.2 JDQ39 img and downgraded bootloader, baseband. Installed it and again, stuck on the X animation. just hangs there.
Any help? i don't know what else to try, currently using my HD2 and it is sooo slow :cyclops:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
badboy47 said:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion but still nothing. Updated CWMR to 6.0.4.3 and tried the 4.3 stock image. Still hangs on bootup. android file transfer recognizes the device is plugged in via usb but just gives me the error "could not connect to device"
Oh man I don't know what's wrong with my nexus
bump bump
I'm having this same issue, and it happened just like you. I flashed CM 10.2 nightly 20131114 this morning and I tested it to make sure everything was working. I decided to reboot the phone, and after that I keep getting stuck at the boot animation no matter what I did. To no avail, I reflashed a working zip, restored a backup, restored another backup, flashed the 4.4 factory image (wiping the entire phone), the 4.3 factory image, and then I read that the 4.2 baseband can fix it, so I flashed the 4.2 factory image. That 4.2 image gets it to boot, but without baseband. Right now I'm trying different radios just to see if I can get service again. If it matters, I was running the hybrid 33/84 radio for T-Mobile's LTE when this happened. Very, very peculiar situation here. I've never had anything like this happen, and especially remain an issue after wiping the entire device. I'm hoping it's not a sudden hardware issue.
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Hmmy 4444 said:
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Click to expand...
Click to collapse
just re-flash 4.2, it'll work. I've been doing that since Monday. but I want kitkat too!!
my device is stuck on the boot animation too. is there a way to reinstall the default 4.3 recovery and just rerun the update or something basic like that? my device was almost at stock before running the update. the only two things: twrp and rooted via recovery. so i thought everything will work fine and now there is no backup...
badboy47 said:
Avoid using twrp recovery.
Click to expand...
Click to collapse
Why?
Just fastboot flash all the image files (boot.img,recovery.img....) from the factory image.
I recently installed Cyanogenmod 10.2 then wiped factory data and cahces the whole 9 and now when I restarted the rom it wont boot past the samsung logo I even tried restoring a nandroid backup of the original rom rooted and it still wont boot past the samsung logo, im unsure of what to do and its really frustrating any help would be much appreciated thank you
You should do the wipes before you flash the rom. You booted up without a system to boot to. Odin maybe your option at this point
Ok
i am at a loss I have my mates nexus 4 (vanilla no root locked bootloader) just OTA updated to 4.4.2 stuck on Android is upgrading Starting apps two hours on that screen powered down reboot and boot loop from there in
So thinking i could rescue with a little trickery i took it home ...so far i have these results
tried wipe cache and factory reset from Google standard recovery ... nothing
installed CWM wiped everything (cache dalvik system data) .. nothing
gave up flashed factory google image (4.4.2) from bootloader ... same "starting apps" freeze again, reboot to recovery wiped everything then boot looped on trying a reboot
"
flashed factory image 4.4 same results boots once locks on starting apps then bootloop every boot after then
flashed 4.1 factory image (earliest build) ... Success got it to load everything working .. yay
OTA update came through to i think 4.1.3 that worked
OTA for 4.2.2 just installed and back to Android is upgrading "starting apps" and frozen there now for half hour
this is a clean install every inch of the phone has been completely reset no apps other than factory google apps are installed can someone PLEASE give me some advice im at a loss.
thanks guys
Myxin
Myxin_n said:
Ok
i am at a loss I have my mates nexus 4 (vanilla no root locked bootloader) just OTA updated to 4.4.2 stuck on Android is upgrading Starting apps two hours on that screen powered down reboot and boot loop from there in
So thinking i could rescue with a little trickery i took it home ...so far i have these results
tried wipe cache and factory reset from Google standard recovery ... nothing
installed CWM wiped everything (cache dalvik system data) .. nothing
gave up flashed factory google image (4.4.2) from bootloader ... same "starting apps" freeze again, reboot to recovery wiped everything then boot looped on trying a reboot
"
flashed factory image 4.4 same results boots once locks on starting apps then bootloop every boot after then
flashed 4.1 factory image (earliest build) ... Success got it to load everything working .. yay
OTA update came through to i think 4.1.3 that worked
OTA for 4.2.2 just installed and back to Android is upgrading "starting apps" and frozen there now for half hour
this is a clean install every inch of the phone has been completely reset no apps other than factory google apps are installed can someone PLEASE give me some advice im at a loss.
thanks guys
Myxin
Click to expand...
Click to collapse
Hello, I have just about the same problem as you do/did I haven't figured a way to fiz it. Any ideas?
I've got the exact same problem. Used the factory image to flash lollipop on my friend's Nexus 4 and it worked flawlessly. Next day he comes to me and says it froze and he force restarted and it wouldn't boot. Tried flashing the factory image again, tried flashing a several custom roms through twrp, and nothing will fully boot it will either loop or get stuck on starting apps. The only thing that has booted so far is the 4.1 factory image. Any ideas?
Like the title says, my phone gets stuck at the boot logo (not bootloader) after I try to flash any custom ROM to which I solve by restoring to a stock rooted nandroid backup of 6.0.
Here's my flash process:
1. Reboot to TWRP
2. Do clean wipe
3. Flash ROM (DU for example)
4. Flash gapps
5. Reboot
TWRP flashes the ROMs and necessary gapps without any issues but no matter what it gets stuck at the boot logo after rebooting. This wasn't a problem in the past as I was using Orion, DU, AICP, etc. Would using the restore-to-stock tool help in this case? The only thing stopping me from using it is the fact that it would wipe my internal storage. Any help would be greatly appreciated. Thanks!
EDIT: I decided to restore to stock and wipe user data and I'm now finally able to get past the the boot logo
How long are you waiting? First boot can exceed 20 minutes just sitting there looking like it's not doing anything...
Sometimes first boot take.more than half an hour
Sorry to revive this but Im getting the same problem... Did u managed to install any rom after u flash the stock rom? Should I do that? How long should I wait on first boot?