Bootloop, starting apps is making me mad - Samsung Galaxy Nexus

My Samsung nexus got a problem. I have TWRP installed as recovery and I tried to install new Cyanogen ROM. I did it clean but it get stuck in "Starting App" for long likely for 2 hrs then I restarted the system just to stuck in boot loop. I did fresh install wiping data and cache as well dalvik cache but the same problem. Before the phone was working fine except the camera. Camera has stopped working issue. Is this the problem for this?
Moreover, I tried to connect to ODIN but my phone is not read by Odin. What is the solution?
The worst thing is I don't have any backup.

Related

[Q] Bricked my phone..

So everything was normal with my phone until suddenly randomly my phone began to reboot itself. Thinking it was an issue with the rom which was a custom ICS rom I went into recovery, wipe my data/cache, and all that and restored my previous backup. After that the issue continued. So I boot into recovery again and started fresh with a clean install of a rom I had on my sd card. Same issue keep occurring but now only worse.
Out of a desperate attempt to fix my phone I tried to unroot using this method:
galaxys2root .com/t-mobile-galaxy- s2/how-to-unrootunbrick-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
It all worked expect now when I boot and get to the setup page it says:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly"
And it makes me force close then the phone turns of and the haptic feedback just keeps going off with the phone being off.
And idea as to why this is happening and how I could possible fix this?
Any help would be appreciated!
If you can get into Clockwork, go wipe cache and then go wipe davic cache and it'll clear up.
My phone is now unrooted and still has the same issue so I can't boot into recovery.
Before unrooting it I tried that several times and didn't work.
flash ODIN and try it again.
Your phone isn't bricked until it is dead.
Wipe everything, load a fresh ROM and see where you're at. If the problem continues go back to stock everything and if it persists there you have a hardware failure and should get it repaired or replaced.

[Q] help please. possibly corrupted efs?

ok so heres what happened. this morning my phone started behaving weirdly. then it restarted and got stuck in a boot loop. I was running the newest aokp release. after the boot loop i restarted to recovery, i was using the team win one. i wiped cache and dalvik and restarted...still only to boot loop. next i tried factory wiping and reinstalling rom. still same thing, only then i couldnt clear the cache. if i tried it would just reboot.
on lunch break i figured id just odin back to stock. after playing with it a few times i got it to flash the stock back. after it rebooted the first time it went into recovery to clear the caches like it should but there was a red message saying cant locate efs or something. there was about 4 lines in red saying pretty much the same thing. and it said manual mode at the bottom.
ive tried wiping caches and restarting a number of times. I fallowed both the guides from the development section and from the general section. so i currently have the stock ics odined on the phone. it will boot to the rom and start. made it through the upgrading android part then once it gets to the home screen it will sit for a minute then reboot again and just boot loop. i can clear cache and make it boot back up but it just restarts after a few secondds.
please anyone know what to do? this is my second gs2.

Have to full wipe after every reboot?

I have been running jedi master x2 on my devise since i got it a few months back. I had a few issues with apps having unfortunately (random app) has stopped errors so I decided to re flash with full wipe and completely clean install. Now after I reboot it gets stuck on the Samsung note2 splash screen and I have to do a full wipe and fix root in order to get it to boot again, only to have to do the same after a reboot? Does anyone have any suggestions?

Factory Reset Problems after Unresponsive Device

Guys,
Need a little help:
My OP3 worked fine for over a month (with 3.2.2, Rooted and with latest TWRP only) and then suddenly went unresponsive i.e., screen frozen. When I restarted the device, it stuck on boot animation. I tried to restored a week old nandroid backup and it stuck at restoring system partition and then... ERROR 7. I tried the factory reset and got the same result... ERROR 7. I tried flashing the from the scratch as well as formatting all partition, still no luck and ERROR 7 persisted.
I switched to OP3 recovery and wiped data and cache and the wiping worked but... when i tried to push the rom, it didn't work and it was stuck. i flashed twrp again and tried sideload, still no luck, it got stuck at 4%. I did a wipe again and tried to restore the old backup and the restore simply got stuck (no error - i waited for 30 mins).
So, my question is two part (before i send the device back to OnePlus): any idea what is going on and how can i fix it? and is there any other way i can try to do an absolutely clean install of rom and try if that works?
Thanks,
Answering my own question: device sent to OnePlus and the issue was identified as faulty motherboard.

Razer Phone stuck in bootloop

I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Have you tried booting to TWRP and booting The other [email protected]
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
mikeandjaimie said:
How long did you wait on the Razer logo.. When I reset my phone after relocking it.. It took 10+min for first boot. I was scared it wasn't gonna work but I just left it alone and it eventually booted itself up
Click to expand...
Click to collapse
Thanks. I'll try that and see if it works. But I let it sit for 5 or so minutes.
Edit: I'll go ahead and add it was stuck at the Razer logo. It never got to the actual boot animation.
Edit 2: I let it sit for 20+ minutes and it wouldn't boot or get past the Razer logo.
RUNNERX said:
Have you tried booting to TWRP and booting The other [email protected]
Click to expand...
Click to collapse
Yes I've tried switching slots and it didn't work.
Any luck with the stuck at logo screen? I followed instructions from Razer and fkashall and now it won't boot to recovery download or system . It just hangs at the logo screen for better part of 2 hours now so it's not a waiting game .. any luck in fixing yours?
hi there, same here after flashing google pixel experience on razer phone1. seems to be a general problem for many users. Any hints?
Best regards
Michael
I have the same problem, but I wasn't updating or installed any new app. I was just ordering food from an app and then all of a sudden my phone restared and got stuck in a bootloop.
I reflashed the stock rom, over and over, slot a or slot b, hoping that would fix it somehow... it's just stuck there now. I could go into download mode and recovery mode. but, it's only until there.
now it's bootloop until it gets into download mode...
ThatGuy94 said:
I tried to update to the latest update to the Razer Phone and was able to install it successfully, but when I went to install Magisk on the new update, it caused the Wifi to stop working. For that reason, I tried to restore my old TWRP backup I made prior to updating which everything was working before updating. I wiped cache, dalvik, data and system and restored my old backup. Now when I try to boot, it gets stuck at the Razer logo and doesn't get past that. I also tried wiping data and restoring the system image only to no avail and it didn't do anything.
Click to expand...
Click to collapse
I could fix it. After flashing (even Android Pi) you have to do a factory reset.
IMPORTANT: THE FACTORY RESET IN TWRP DOES NOT WORK. So you have to flash the boot-sector in your system partition with the stock boot.img and reset to STOCK RECOVERY by typing "fastboot reboot" and pressing the vol-up button. Once in stock recovery, do a factory reset and return to bootloader. Now you can flash the boot.partition with twrp boot.img, install in recovery the stock boot.img, install the twrp-installer.zip and reboot to system. The bootlogo will not stuck anymore.
I hope, I could help you. Do not forget to backup before trying.
Best regards
Mellus
sry for my bad english

Categories

Resources