Database Info

Infuse stuck in boot logo loop

My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?

Did you have any undervolt settings applied?

The phone is not underclocked, it is not overclocked. It was rooted, I unrooted it. its currently unrooted absolutely factory stock and still doing that. What can I do to fix this?
warranty is over as of 3 months ago

Forgot to mention the most important thing!!!
When I am on the phone with someone, it works perfectly forever, as soon as i hang up, it ends the call. this key thing might help someone find the solution!!

himalaya333 said:
My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Click to expand...
Click to collapse
Don't panic just yet... I doubt your phone is dead.
You say you've "wiped data and cache". Are you also making sure to wipe /system and Dalvik Cache?
Try flashing Zeus again.
Boot to CWM, Wipe EVERYTHING (/data, /cache, /system, Dalvik Cache). (Alternatively, get "Clean Wipe" from Qkster's Scripts and flash with CWM to easily wipe everything.)
Flash Zeus and go.
If you're still having problems, perhaps try a different rom?

okay, I read everything you guys wrote.. This is where I am, I am open to suggestions
I am on the stock rom and unrooted. Phone still boot loops. What should I do now? Step by step instructions would be great. Im unrooted, so should i root again? even though im having this problem?

bump! really need help with this guys!

Have you tried going back to stock?
If it keeps looping while on download mode then I would say you are dealing with a hardware issue.
Sent from my sweet & buttery Infuse

It just came to me that it doesn't loop in download mode. It does loop in clockwork, I flashed the stock kernel using ODIN and went completely stock through ODIN.
How do i fix this? i'm pissed that i had it for a year and three months and right after the warranty ended, the phone stopped working! Samsung never again unless this issue is fixed

I'm a newbie to flashing, so take it with a grain of salt. At least two more things seem worth trying to me:
1 - Try factory data reset (assuming you already tried the wipe Davlick and wipe cache). I'm not positive what this does, but I think you may lose some of your data if it's not backed up.
2 - If that doesn't work, try qkster's Heimdall UCLB3 stock (since you can get into download mode...shouldn't be a problem). This is complete back to stock so should be able to clear any software problem I'd think. I know you may think it's redundant since you are already back to stock, but worth trying imo since some things just take more than one try, and you may have had a bad flash the first time around.

Why zeus? try latest ones with jelly bean
Hey,
Try other roms based out of jelly bean. They are pretty stable. CM10 with 09/14 build is the latest
Here are the standard steps if you have CWM enabled.
1. Factory re-set (only when switching between different roms).
2. Cache partition wipe
3. Dalvik Cache wipe
4. Install the zip file
5. Re-start and wait until it re-starts. Initially it will take some time.
I have tried various roms and versions as well. Best would be the CM10 Jelly bean.
Thanks Kran.

[Q] Phone stuck when turning on

Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.

SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.

bweN diorD said:
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
Click to expand...
Click to collapse
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?

SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
In all likelihood, this is not a LiquidSmooth issue. I would suggest a clean install as the previous posters suggested. The latest stable version of LS is now at v2.10 for Android 4.3
LS 2.10 must be installed as follows, according to the devs:
New Flashing Instructions
wipe data/factory reset
wipe cache partition
wipe dalvik cache
format /system
Install ROM, NOT GAPPS YET!!
Reboot system, first boot may take a few minutes, don't panic ;-D
Setup your phones settings, anything that isn't Google related
or let your phone sit for 5 minutes
reboot back into recovery
wipe cache and dalvik
then flash gapps
reboot and enjoy
Click to expand...
Click to collapse
For the xt926, the download page for LS 2.10 is here: http://d-h.st/users/jsnweitzel/?fld_id=15202#files
gapps 8/13 or newer are supposed to be used with this ROM. dl from here: http://d-h.st/users/jsnweitzel/?fld_id=21058#files
The official ROM page is over at G+ https://plus.google.com/u/0/communities/117452480298315341829, if you have any additional questions.
Give it a whirl, and let us know what happens. Good luck.

SELind01 said:
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
Click to expand...
Click to collapse
you are wiping very well, i was just confirming you wipe everything possible short of the external sd.
the wipe im talking about in twrp is wiped when you wipe "data", the one where you have to type "yes" before it will wipe. in cwm, in the formatting section (i forget what its called), there is an option that specifically says "data-media /internal sd" or something close to that.
as for the latest recoveries, here is a tool by Tucstwo that i have been updating lately http://www.mediafire.com/download/2o061zcmzlaycb5/Razr_HD_Recovery_Flasher_V8.rar
also, twrp 2.5 doesnt have all the selinux bugs worked out, you need 2.6.3.0, which is in the above utility.

Major breakage: phone hangs at unlocked bootloader after first reboot of custom rom

Soooo. The photon i've been using since june lost it's identity (IMEI, ESN, MEID, etc. all GONE and DFS tool kept throwing nasty errors every time it tried to read or write to the phone) so i swapped the board out of my other photon with a broken screen into the pristine chassis of the amnesiac phone.
now the fun starts: i RSD back to stock to activate the phone, all's good while i'm on stock. but if i flash a rom like skrillax's CM 10.2, the phone will boot fine the first time, then upon reboot will hang at the unlocked bootloader warning screen. restoring a backup of stock fixes this issue, but i'd really love to have my CM back
Any ideas?

Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.

angahith said:
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
Click to expand...
Click to collapse
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!

solitarywarrior1 said:
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
Click to expand...
Click to collapse
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.

solitarywarrior1 said:
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
Click to expand...
Click to collapse
I just ran into this issue too, after flashing CM10.2.
I can't boot any ROM right now. The phone always shows the unlocked bootloader screen and returns (without button press) to the recovery..
I will try flashing the stock FW with RSD Lite.

I have just been searching for a reason for this issue also.
I was running stock jelly bean, unlocked, twrp. Flashed CM 10.2, and it runs fine right until I reboot the device then it hangs at the red Motorola symbol. I have to hold the power button until it starts vibrating to shut it off. If I boot into recovery and do a factory reset it will then boot again.
I have tried updating to the latest version of TWRP (from 2.5), and tried both Milestone and Nightly versions of CM. I have flashed this phone at least 20 times today. Issue persists with or without Gapps.
I REALLY don't want to go back to stock after all this time I've spent, any ideas on what is causing this?

i had a similar problem monthes ago. i was able to boot but its not a fix more a workaround.
go to bootloader menu (Power+Vol-Up+Vol-Down)
and try the first option it called "normal powerup"
if it not work go again to bootloader menu and try "BP Tool"

same problem here...
after flashing cyanogenmod 10.2 and the first reboot the phone hangs
i restored original moto 4.1.2 from nandroid and now phone runs without problems. is there a problem with cm 10.2 ?
i used last night 20131127 gsm and swapped bootloaderimage.

Know this is an old thread, but after Motorola recently announced that they won't be bringing KitKat to the Photon Q, I finally decided to root and flash mine.
Can't begin to say how disappointed I am at Motorola on this one - the MSM8960 is well supported by KitKat and there are no technical reasons not to... at least Motorola is tactily admitting this is a penny-pinching business decision.
Anyways, I'm stuck at the same hang. Tried flashing known-good Photon Q builds and using the latest TWRP.
It took three flashes just to get the latest stable TWRP for it to take. I suspect the "JBBL" (Motorola Jelly Bean-era Boot Loader) is at fault here. CM just committed some patches to (in the near future) resume issuing builds for JBBL devices, but that won't fix the underlying problems.
And, since Motorola is abandoning the device, it looks like those won't get fixed either.
My next step is to restore via RSDLite, update PRL, Firmware, and Profile in stock ROM, and then start over. Disturbing that's needed, but now Motorola is Lenovo's problem I guess.

How long did you let it boot? Out of five XT897's I've owned, one woul ALWAYS take 15-60 minutes after an initial flash. I guess something was wrong with the memory. After an RSD-return-to-stock and back to CM it would take at least an hour to boot (repair process in the back during bootloader-logo). A wipe (internal too) and CM and it would take 10-15 minutes to get past bootloader logo.
Yesterday I restored a nandroid, wouldn't boot. Installed via zip and 15 minutes later it did boot again.
So just maybe you also have one of those special Photon's . It's worth a try.
I used TWRP 2.7.1.1 and M8 Snapshot in case you were wondering.

Stuck in a loop, need help

Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden

Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app

I know I should, but I didnt. Is it still fixable ?

*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.

Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app

Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden

Lenovo K4 Note (A7010). Won't power up. How to recover?

Ok so, I flashed a CM13 rom on a K4 Note (16GB internal and 3GB ram version). I pretty much followed all the steps required for flashing - unlocked bootloader - installed TWRP - wiped (factory reset) - flashed the Rom. Now, the phone booted up alright and worked for a day. The phone doesn't belong to me, and the owner decided that he wanted to factory reset it one more time. Since I also wamted to show him how TWRP functions, I booted into recovery via the advanced boot option in Cyanogen (Did not use the key combination). So this phone turns off and decides not to start. I waited for some time and decided to manually power it up. It won't. I held down the key for about 5 minutes and yet, to no avail. Not even a vibration. No response at all.
So, I would like to understand what happened with the phone, since as far as I can tell, TWRP was working fine. I used the key combo method to boot into TWRP thrice the night before - to flash CM, to flash gapps and to flash thr xposed installer. I can say CM was working fine since I used it for a night to get a hold of any bugs. Nothing went wrong at that time.
So, what can I do now? Since the phone is completely unresponsive and is not being detected upon being connected to the PC, I suppose it's hard bricked. But what cause the brick in the first place? Any possibe way to recover the phone? Is it even hard bricked though?

What about battery charging % frist chik battery I think battery fult
Sent from my GT-I9505 using Tapatalk

Nah, it doesn't charge either. I tried plugging it in and turning it on. It still won't.
It's just sitting there. Doing nothing.