Ok so I'm still running into the same issue I had with kernels before. It seems like anything I want to flash onto my phone now causes a constant lock up at the red eye screen and then an infinite boot loop. I can't even get a different theme on there without running into this issue. I must have flashed my recovery image like 5 times today. I even just did a basic factory reset from the inside the regular settings menu and it caused this boot loop. Should I be worried at this point?
Ok so 51 views and not a single suggestion??? Come on XDA I'm sure someone knows something
You know I ran into something similar and just for the sake of not being frustrated I knew of one that liked me, liked my phone, liked my ROM. I just stuck with it. Plain ol' gave up trying the latest and greatest kernel. It will make your head blow up if you keep fighting it trust me. BTDT
Vicky
I wasn't even doing kernels though, these were just themes.
I've had that happen too. It maybe that the themes were designed for a specific rom version and that is the problem. I has some that were the correct Rom name just a different version. I was on 3.2 and it was for 3.1. Don't know why but some phones are just finicky.
ps. I meant different phones not as type or model, but your's vs. mine. Something I found out when I started rooting my phone.
Maybe u have a bad nandroid
Related
I got a question for anybody that has had this problem. I got a refurbish Inc. from Verizon, and first it does not run as fast as my first one. It can not be clock over 1300. My old Inc. could be over clock at 1500. 2nd with my new phone it would not let my flash certain Roms like (redemption,cm6, and so fourth). It would let me flash (Skyraider, ruby, Frankenrom) with know problems. I know all phones are not alike, but its bothering me with my old phone I could put any Rom and it would work. Any idea whats going on.
Ok i'm guessing you mean 1.15ghz and 1.113ghz, that a limitation of the phone, mine can only be stable up to 1.113.
Now with the rom flashing problem, what do you mean by you can not flash it? What is happening when you try to flash those roms that you mentioned?
Well it loads the Roms it goes thru it thing and when it comes to the splash it gets stuck their. I think when the Rom has a custom kernel, that's when I have the problem.
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
First...... Wrong subforum. Try Q and A.
Second, in all your rom flashing, did you maybe forget to wipe, and re-wipe before your rom install?
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Happened to me when trying to root my brothers Evo. (Already had mine rooted). I thought the phone was bricked because there was no recovery installed and all that worked was hboot. I tried several different versions of PC36IMG.zip until 1 finally worked.
Cheers
Yes! try updating with PCM36IMG.zip ROm that should help you out, ex "Sprint lovers". Good luck.
sidiasus said:
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Click to expand...
Click to collapse
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Mikedick said:
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Click to expand...
Click to collapse
No problem, I tried to write in a more humorous style than the other "HALP" threads, and my ability to clearly relate the important details suffered. Thanks for the good wishes!
Etiquette question: I've duplicated this thread in Q & A, should I just delete this one?
Also, thanks to all for the lightning fast responses, trying more PC36IMG'ses.
Nah, just let it die.
Found like you're radio fried, it's a well known defect on some evos and incredibles. Try to put it in the fridge while turned off and afterward it may run for long enough to turn s-on.
Sent from my PC36100 using XDA App
I've owned my DInc for around 8 months now and a week after I got the phone I had rooted it... The only thing I truly did was install a few custom ROM's on it to try out what I liked, when Froyo was in it's prime I used CM6 nearly every day, and now Gingerbread is around I've been running steady on OMGB6/7 for the past few months...
My problem is that last week my phone randomly rebooted and decided to get stuck on the white "HTC" boot logo... It stayed there for around 10 minutes before I finally decided to pull the battery, restart it, and the same thing occured.
Of course I have CWR installed with Nandroid backups, but when I used the backup for the current ROM I was on, it happened again getting stuck at the white screen. So I fired up CWR again and restored to a previous version of OMGB6 and that ran steady until today (in the middle of calculus of course) it rebooted after sending a text and got stuck at the white screen once more...
Now I CWR restored to my Stock HTC Sense ROM and I'm running that as we speak (and god, is it god-awful).
WTF is wrong with my Incredible? I'm guessing something got corrupted maybe in the /boot partition or something of the likes? Could someone please help me? I've never had this problem before... and never did any "customization" other than wiping my cache/data/dalvik/battery stats and installing different ROMs.
Thank you!
al2x said:
I've owned my DInc for around 8 months now and a week after I got the phone I had rooted it... The only thing I truly did was install a few custom ROM's on it to try out what I liked, when Froyo was in it's prime I used CM6 nearly every day, and now Gingerbread is around I've been running steady on OMGB6/7 for the past few months...
My problem is that last week my phone randomly rebooted and decided to get stuck on the white "HTC" boot logo... It stayed there for around 10 minutes before I finally decided to pull the battery, restart it, and the same thing occured.
Of course I have CWR installed with Nandroid backups, but when I used the backup for the current ROM I was on, it happened again getting stuck at the white screen. So I fired up CWR again and restored to a previous version of OMGB6 and that ran steady until today (in the middle of calculus of course) it rebooted after sending a text and got stuck at the white screen once more...
Now I CWR restored to my Stock HTC Sense ROM and I'm running that as we speak (and god, is it god-awful).
WTF is wrong with my Incredible? I'm guessing something got corrupted maybe in the /boot partition or something of the likes? Could someone please help me? I've never had this problem before... and never did any "customization" other than wiping my cache/data/dalvik/battery stats and installing different ROMs.
Thank you!
Click to expand...
Click to collapse
This used to happen with me on OMGB, its one of the reasons I switched to CM7. When I rebooted it used to get stuck on the splash screen. Mine, however, would work after a battery pull. I'm not sure, I'd try a fresh install, if that doesnt help, try out CM7, its a pretty stable.
Oh ok... so you're saying its probably just a ROM issue with OMGB? I'd switch to CM7 but the only thing I want is stock Gingerbread, I really hate the little customizations they put into CM7. Do they still have that CM7 Source project going on where it was pretty much stock gingerbread? Thanks again!
al2x said:
Oh ok... so you're saying its probably just a ROM issue with OMGB? I'd switch to CM7 but the only thing I want is stock Gingerbread, I really hate the little customizations they put into CM7. Do they still have that CM7 Source project going on where it was pretty much stock gingerbread? Thanks again!
Click to expand...
Click to collapse
I'm not saying thats 100% the case. I'm just saying that used to happen to me when I ran OMGB. I couldn't find a fix, so I just switched ROMs. I don't think CM7 has a just stock gingerbread look. But how can you not like all the features they packed into it?
AOSP + SD
Perhaps try flashing a Sense ROM and see if the issue persists.
Why?
AOSP ROMs interact quite a bit w/ the SD card. So, if there are issues w/ the SD card, the Sense ROM may not present as many funky issues.
After that test, I'd try another SD card and see if the issue persists.
If a different SD yields no wonky stuff, the answer was faulty SD card.
continual spontaneous reboots
I have the same issue. I was using CM6.1 I think and it's been fine for awhile and then it just started spontaneously rebooting. I can no longer get into Clockwork, all I can do is hold volume down and power to start it and from there, nothing will start the phone. I get the HTC spash and after about 3 seconds, it reboots and gets stuck in that cycle. Nothing has really changed and it rebooted on it's own to start the problem.
So, it's not like I installed something and rebooted. I'm interested in hearing if others are having the issues and what exactly their thoughts are.
Alright, so I am having this weird issue. I thought I found the fix for it several times, however, NO dice.
I've researched for a few hours now, I just don't know if I have over looked it or what. If it has been answered, I apologize.
I looked at the modified recoveries thread for newer s3 devices, but it doesn't seem to fit my area of error.
The Details:
I've been really curious to try some 4.3 roms. Of course, they are for D2SPR. I get them to flash correctly, after a full wipe. The issue happens right after I set everything up in the phone, and reboot. When I reboot I get hung at the splash screen. I have tried to reflash the rom muliple times only to fall flat on the splash screen again. Now, I don't have an SD Card in the phone, except, I left a TW rom in a folder. I use twrp, forgot to mention that. I rewiped the phone and installed that touchwiz rom, and still it wouldn't allow me to get past splash into that tw rom.
So the only way that I could think of to get out of this hole was to flash the rooted LJ7 tar file I have through ODIN. After getting the S3 into download mode, Odin successfully push LJ7 into my phone. Now again, I had an issue getting it to boot. I read somewhere that when this happens, I need to check the Erase NAND option in Odin. So I tried that out and forced LJ7 back on. After successfully flashing, it boots but gets stuck on the boot animation; the fix to that is booting into stock recovery and wiping once more. Then you are able to get into the OS.
I let the phone sit and take the OTAs till I get from LJ7 to MD4 so I re-root the phone using Odin and Chain Fire's root method. Now I am able to flash the recovery (TWRP) using OpenScript through Goo Manager.
I've only tried flashing Illusion and Carbon's 4.3 rom. The second time I used Carbon's rom. Same results. So I have no Idea what the heck is going on. Can anyone explain this to me better or point me into the direction that I need to go?
Thanks much!
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
bbrita said:
your not the only one that has this problem i have the same thing have tried everything and most of the 4.3 roms same thing. no one on xda seems to know at least i havent gotten any help or responses i have just given u on 4.3. good luck finding any ideas.
Click to expand...
Click to collapse
Well, it's good to know that I'm not the only one, however, it's horrible that it's happening to others. I appreciate you spreading the info!
edfunkycold said:
Set it up I'm sure you restored some apps and data which may no longer be compatible. Or data which is corrupting the 4.3 rom. Try just flashing the rom setting up your Google account and don't add any apps. See if it does it.
Either way this seems to be a common issue across different devices and 4.3 seems it's part of using roms built on leaks and ports. None are bug free. Very similar to all gb leaks back in the day that would go into bootlooping.
Have a great day!
Click to expand...
Click to collapse
When I go to set up, I just install about 15 apps, I don't restore. I just download them fresh. I had a habit of doing that and it just stuck. I don't restore anything with Titanium or and root backup/restore app. Could one of those apps not be updated then that causes the partitions to get locked up, or just corrupt /data in general? If that's whats happening.
I just find it extremely odd that I (maybe others), can't wipe, and then re flash another rom; actually I can, it just gets stuck at the splash and never goes forward, that is what had me confused most. If I had an sd card, and formatted data itself, would that fly?
thanks Ed i have tried this after the first 2 tries . i dont have any problems installing 4.3 its just after rebooting it gets stuck. Like you said there are always bugs Im fine with using other roms for now. Hopefully when an official 4.3 drops problems will go away
[Edit: this was an issue with cm11m8 problem resolved in update to m9]
When I try to power off phone and recharge the battery sign will pop up on screen and then phone will attempt to boot but freezes on the first screen. I can get out of this by going into download mode then exiting. Without going into download mode no mater how many times you try to restart it will at that point freeze at that screen. Screen will just sit there lit.
I am running cm11 the most recent stable on the att i747. Before install i wiped cache and davik. then wiped again after install. I was able to charge the phone while off on cm10. the only thing that has changed since then is that i updated from the jb firmware to the latest kitkat firmware the UFNE i think it is. after the baseband update i continued to run cm10 for about a week but cant recall if I tried to charge while powered off.
Does anyone have a fix for this or can lead me in the right direction?
if so thanks in advance. I did some searching here and all over the web but cant find anything phone specific or able to help.
oh also annother note.. i am running a different battery.. its the 7000 mah nolemon but i remember charging this battery while phone off when i got it so I don't think it is the battery or the phone. I could be wrong though. maybe its something different with cm11 or possibly the firmware
No one have this issue? Or no a fix?
Try a different kernel.
I just installed the snapshot. I'm newb with kernel. Which kernel?
there's many choices in the att s3 original development thread to choose from.
just make sure its the right one for your android version.
err on the side of kindness
I can't tell you about individual kernels. I don't use cm/aosp roms.
I do know the same thing happens with the sprint TW kernel though.
I'm not completely new to this. Done about 3 devices now I guess.. This s3 has been a pain compared to my nook HD.
Cyanogen is the only ROM I have ever used. And clockworkmod is the only recovery I have tried.
It seems to me from what I have seen on here most people are using the twrp ROMs... Where as on the other devices it seemed cm was the pick of choice?
Would I be better off ditching cm and using something else? I have just stuck with cm cause I am familiar with it. If I was going to go to a twrp ROM what would be the best option for kitkat. I really don't want nothing that's experimental. I want something tried and true and supported. I just don't have any experience with anything other than cm.
Back to the issue is there anyone out there running cm11 on ur i747 that's having same issues on the kk firmware also?
If someone just said "not having that issue" it would at least let me know the problem is not cm11 related and something else
might could read/ ask on the cm11 nightly thread. also some of the custom ROMs are based on cm anyway.
http://forum.xda-developers.com/showthread.php?t=2682905
err on the side of kindness
You should give one of the stock builds a fair chance. Kk ones are still under development, but there are some very good, completed roms based on 4.3 firmware.
Not a big fan of the stock att. I hate the interface and lack of options. Cm is fine and I could go back to 10.2.1 easy enough I just was wondering if anyone else has experienced this problem that I am having.
I was thinking someone a bit more knowledgeable with this could tell me why when phone is off it tries to boot when charger inserted. At least this is what it seems like its doing.. And then it freezes
Also when it freezes its before the spinning splash screen. Its on the screen that says Samsung galaxy s3 but has the lil cm android guy at the bottom. It won't make it to the spinning screen. Maybe my problem is with this screen and if there is a way to disable it I could test that
google???
err on the side of kindness
Are you saying I should Google instead of ask for the help....
Google can only get you so far on certain issues and rest assured I have googled the hell out of my issue.. This issue has prolly had at least 4 hours or more of "google" time...
If Google could answer all there would be no need in this section
hopefully as you posted earlier, someone with some sort of experience with this will chime in.
googling was just a suggestion as i did not know if you had searched yet.
no offense intended.
err on the side of kindness
Oh none taken sir
Thank you and the others for all the help provided
delete
err on the side of kindness
99.99999% chance it is not a problem with thr display. Never heard of one like that, but have seen your situation hundreds of times at least.
It seems to be with the kernel/bootloader combo... I had the issue with kt747 when using mjb but not any longer now that I'm on ne4. Mine didn't freeze but it wouldn't stay off when the charger was plugged in, and the recovery button combo wouldn't work with it charging either.
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
I am on the ne4 firmware, cm11 July snapshot, latest cwm recovery
What kernal would fix this?
I am having no other issues besides this. Did a wipe before and after baseband/ firmware update. I mean it
What you are describing is how it does the phone won't stay powered off when plugged in
Gets stuck on the boot logo that says galaxy s3 with the cm android guy at bottom. The one before the spinning splash.
How did you fix yours?
My situation is reversed as your problem started with ne4 and mine just went away with ne4, but I'm on a touchwiz 4.4.2 rom with kt747 tw kernel.
I can't speak for aosp kernels, but I've heard kt747 aosp doesn't currently work with wifi on latest cm builds. You may just have to try different kernels or wait till the kernels catch up with the firmware as downgrading from ne4 is NOT an option.
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Do you like the touchwiz ROM that you are on now?
How would u say it stacks up against cm?
Gimme the name of the ROM and I may try it with that kernel