My phone unexpectly turned off and then it entered into a bootscreen loop.
I just tried to flash a stock rom, so I could just erease everything and make it like new.
The problem is that after any flash, or any new rom I install, it keeps into this bootscreen loop. I read that I need to go into the recovery mode and make a Wipe, o data factory reset, etc.
The problem here is that I can't get into the recovery mode in non of the roms i've used. I even tried the last Phils recovery (philz_touch_6.07.9-jflteusc.tar.md5 ) and it dindn't work either (Even unchecking auto reboot and trying to enter to recovery mode after flash)
I press Vol +, Home, and Power, and it shows me this:
Blue line: RECOVERY BOOTING...
Yellow line: Set Warranty Bit: recovery
THIS IS IN EVERY ROM I'VE TRIED.
Then it get full of different colors pixels, and then just restart, and all the looping starts again.
I can't show you the photos I made because I'm a new user in xda forums.
Please help me!
Related
So I was using a cooked MCR ROM, but wanted to factory reset to start fresh. I went into the bootloader and selected factory reset and now it loops the boot animation over and over.
I've tried different ROM's, I've re-partitioned the SD (at one point I was seeing errors about not being able to access Apps2SD) and each ROM will boot up, take a long while on the first animation and then loop itself afterwards.
This isn't a normal boot loop, it doesn't actually reboot, just loop the animation.
Any ideas?
well yes you will need to flash your rom again, can you actually access your clockwork recovery menu by holding down the volume key when the system boots up ?
(fYI, it may come up with the with fastboot screen first)
oooo sorry forgot to mention, youll need to go into the recovery menu and also format the following by selecting mounts and storage before you reflash
- Data
- Cache
- Boot
- System
then once you reflash you should have it sorted, some boot animations do loop on first start up, if it takes longer then say 10 mins then you know its done, unfortunately there is no sure way to tell.
Okay thanks, wasn't sure about formatting boot and system.
Hello and thank you for taking time to read this post.
I attempted to root my At&t Samsung Galaxy S3 today then install tha AOKP Rom, and it back fired due to poor instruction, and poor execution. At the moment my phone, whenever it turns on "inititing swager" (with a pink horse and gears) then gives me a pop-up saying "Unfortunatly the process com.google.process.gapps has been stopped." and "Unfortunately, Setup Wizard has stopped". Whenever I hit ok, the other shows up. I have access to the pull down menu, but can't open any of the links on it. I can also shut it off then get back to the root(hat menu) menu. From which I have tried the option "wipe data/Factory Reset" link, but that changes nothing when I reboot. At this point I am just looking for a way to get it back to factory settings or at least working!
How I got here:
1. Rooted the phone through my computer (successfully it seemed)
-Using this tutorial: /watch?v=bIUA1IxiJzo
2.Started puting AOPK on!
(with this: /watch?v=qzcR-G7EKSw
Look, I know none of you have to help me but any feedback will be greatly appreciated.
P.S. I hav looked through other forums about the gapps error, but the difference is mine is not running to the home screen so I can't go to application manager!
Two suggestions:
1) Put your phone in recovery mode (i.e. where you can do factory resets from), transfer a different ROM image over to the device (I'd use adb to do that from recovery mode), flash it, clear data/cache/etc., reboot the phone, and hope it works.
2) Put the phone in download mode (Vol Down + Home + Power; just like entering recovery, but Vol Down instead of Vol Up), and use Odin to flash a rooted stock image as detailed here; put CWM / TWRP / whatever recovery you want to use on the phone again, and get back to flashing ROM images from there.
In the future, try to be careful of what ROMs you flash... not everything works very well, as you've just discovered.
Thank you for responding so quickly! I am attempting the first method, however i am not sure how to transfer a different rom image(im assuming the adb stands for Android Debug Bridge). I was using the internal SD, but I can plug it the phone into my computer, and it says no drivers found for this device, where before it recognized the phone. Once I get that I can clear the other data and restart.
Your help is very appreciated!
smelenchuk said:
Two suggestions:
1) Put your phone in recovery mode (i.e. where you can do factory resets from), transfer a different ROM image over to the device (I'd use adb to do that from recovery mode), flash it, clear data/cache/etc., reboot the phone, and hope it works.
2) Put the phone in download mode (Vol Down + Home + Power; just like entering recovery, but Vol Down instead of Vol Up), and use Odin to flash a rooted stock image as detailed here; put CWM / TWRP / whatever recovery you want to use on the phone again, and get back to flashing ROM images from there.
In the future, try to be careful of what ROMs you flash... not everything works very well, as you've just discovered.
Click to expand...
Click to collapse
Gapps loop
How can I post a doubt in XDA forum?
What custom recovery is on your phone? I suggest installing Philz Touch via Odin if possible and then flash a new rom from an external SD card.
I'm trying to update the Beanstalk rom, I had a previous version installed before
So what I did was download the rom, download gapps, and go into recovery mode, clear cache and install the rom
But I got this error:
"symlink: some symlinks failed"
So I went back, unsure of what to do. So then I went into the reboot menu, just to check things out, it gave me a warning that it may unroot my phone, and before I could do anything, it automatically rebooted
Now i'm stuck on the boot logo, so I tried turning it off, and now i'm stuck with a picture of a drained battery
I redownloaded the rom onto my SD card, and I'm trying to get back into recovery mode with power buttom + volume up, but it won't work.
What do I do now?
Hello,
my Samsung Galaxy S4 mini with bliss ROM stated to turn off spontaneously and sometimes it didn't start again (the Samsung logo appeared and then the phone went dead, it was impossible to enter recovery mode, download mode shut down itself immediately). After several tries, it booted normally. This happened again - and I found out it was a bad power button, which I replaced. Now it is possible to enter both recovery mode and download mode with no problems. However the main OS doesn't boot up. So I tried to do a full wipe in recovery mode and CWM recovery rebooted the phone, when it was trying to format /data partition. So I tried to flash stock firmware with ODIN. It also didn't boot up, but at least the stock recovery gave me a hint what is wrong. When I perform full wipe, I get error: "E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata"
I tried to flash the phone again, this time with a PIT file and let ODIN to reformat the partitions. However, no change. How can I fix it?
Try twrp
So, what happened, I was almost finishing the flashing of the rom, I was in twrp, and selected reboot to boot loader mode, but I selected slot 2; then my screen never more get on. @majmoz Can you help me?
there should be a error screen after boot with slot2, coz i was tried before, i fixed with full flash with gpt / bootloader with full rom