So i am thinking this is hardware, But i wanted an opinion from you guys on this.
My friends Dinc randomly reboots. Sometimes even in a boot loop.
At first i thought it was his ROM as he was using a rooted ROM then did an OTA update. So we just reflashed his ROM with Anthem Sense 3.0 And it's still does it from time to time.
Only has been two hours and one random reboot, But my phone i've never had a random reboot ever.
Is it hardware? Or software?
Hard to say. A lot of things can cause a random reboot, your kernel, your rom, apps you use, battery issue, etc. Does it do this on all roms, or the stock rom? I would flash a stock rom, with the stock htc kernel, and dont install any apps. Go for a day and see if it still reboots, or reboots less frequently.
I'll have him try that, and so far it's any rom, He had Stock Plus for a while with tiny's kernel and then the stock plus custom one. it also did it before i even rooted it.
Any chance he didn't wipe everything while flashing? I see that as a solution to reboots all over the net.
Sent from my ADR6300 using Tapatalk 2
I wiped it personally.
Wipe data/Factory reset (i think thats what it's called. third or fourth option down in recovery)
wipe delvik, format system, format boot.
Related
so im trying to get MIUI on my evo, but when i flash it it sticks at the sprint bootloader. i got the rom from MIUI. anyone help?
Did you wipe everything before flashing? Have you tried other kernels?
i have wiped data and cache. and im sorry but im new at this, what is a kernel
first of all, try also wiping data ( i kno its hard, just back up with titanium backup), system, boot, and battery stats. that should boot right up.
Did you wipe dalvik? You need to wipe data/cache/dalvik when switching ROMs.
If you don't know what a kernel is then I HIGHLY suggest you spend a little time reading up on all this because that is Android 101. You should have known what a kernel is before attempting to flash anything. A kernel is basically the interface between the software and hardware of your phone. It has all the drivers and instructions that tell your hardware what to do. They are flashed the same way ROMs are flashed and can affect performance dramatically. Different kernels perform differently on different EVOs so you need to find one that works well for your device. Sometimes the kernels that come packaged with ROMs don't work well on some EVOs and can cause booting and performance problems.
Mas wipey before flashy! Wipe all data, save for sd card, twice before flashing this rom. The savaged kernel that comes with the rom is just fine. Also, I would avoid titanium backup like the plague, especially if you are going to use MIUI.
Swyped from my CM7 EvO
So I have Droid incredible #1. Rooted s-off. I have before been able to flash custom roms. But I haven't tried for a while, and now I can't do any without it getting caught in a boot loop after it installs and reboots. I've tried cm7, miui, bugless beast, and probably 4 more tonight. All do it, but all let me remove battery and restore back to a backup I have. one possibility is its been so long since I've flashed a ROM, I may be on a custom ROM right now but thinking it's stock. Does it make a difference if I flash a ROM while already in another ROM? I'm not too techy but I have an idea of some stuff. It's not a big deal the phone works fine the way it is its just disappointing not being able to flash one I want. Thank you guys!
When flashing a new ROM, make sure, in recovery, you wipe data/factory reset, wipe system, and wipe boot. Then flash the ROM.
I tried to flash HONO Full Throttle V2, cleared cache, dalvik cache.
Now my phone keeps rebotting loopping. I tried to access ROM manager but it reboots before it can do it. I tried accessing CWM recovery Power+Vdown and it only shows the master reset screen...
Do i have to unbrick?
Any help is appreciated, thank you
When that happened to me, with a different ROM, I went ahead and pressed power again at that screen and it continued to CWM, didn't wipe/reset my phone.
neuty said:
I tried accessing CWM recovery Power+Vdown and it only shows the master reset screen...
Click to expand...
Click to collapse
That is what you are supposed to see. Press power button twice to "accept" the factory reset. It won't actually reset anything -- instead it will boot directly to CWM.
Oh, okay thanks so much RealyPssd and Drumist! Got a bit scared for a second there. Was able to flash back
Edit: I might have found the problem:
I tried installing HONO's P930 CM9 Kernel V5 and it did the same thing but worse, it didnt even let me past the CM boot guy.
Went through the same thing
I tried flashing HO!NO!'s CM9 Full Throttle this morning and went through the same thing. Sometimes it would boot into the OS, other times it wouldn't get past the CM9 guy, and even sometimes it wouldn't get past the HO!NO! logo. I even had a hard time getting into CWM via the factory hard reset method (I kept getting just a blank screen, but the phone was still on. I pressed the volume down button and that seemed to get it into CWM, although it could have just been a coincidence).
I tried re-flashing the ROM but still no change. So I then flashed CM9 RC-1 and haven't had an problems since.
From what I've read in the Full Throttle thread, the HO!NO!'s ROM already comes with HO!NO!'s kernel. I've also read that the instability is due to the undervolting that's taking place in the ROM (and I'd have to agree based on my experiences with overclocking).
If you really want CM9 go with the RC-1 (or even the nightly). I find it to be incredibly fast so far. Maybe HO!NO! can make a ROM compiled with the linaro toolchain that has a slightly less aggressive undervolting settings
To make thing clear for everyone
first kernel i make was for gingerbread and yes i was using undervolting and overclocking.
For CM9 i only use overclocking since CyanogenMod team all ready use the same undervolting i was using with GB.
It as to be something else causing you that kind of problem.
did you try a fresh install? wipe data,cache,dalvik Without anything esle like script or backup, like it was the first time you got the phone. nothing only the rom.
Wiped everything but had a backup
HO!NO! said:
To make thing clear for everyone
first kernel i make was for gingerbread and yes i was using undervolting and overclocking.
For CM9 i only use overclocking since CyanogenMod team all ready use the same undervolting i was using with GB.
It as to be something else causing you that kind of problem.
did you try a fresh install? wipe data,cache,dalvik Without anything esle like script or backup, like it was the first time you got the phone. nothing only the rom.
Click to expand...
Click to collapse
I was coming from a stock ROM that I had rooted with SuperOneClick, and installed CWM using Rom Manager from the market. When I went to install your ROM I first made a backup of the current ROM (i wanted to having something to fall back to). I did a wipe data/factory reset, wipe cache, wipe dalvik, then flashed your ROM. I also flashed gapps as well (could that have caused a problem?)
Does it sound like anything is off? I would really like to be running your Full Throttle ROM (it's the only reason why I tried to flash my phone in the first place)
Ok rooted my DHD about week ago with AAHK have now try 3 diffrence roms. the newest rom (icecold sandwish) is doing so weird things once in allpications settings phone was showing only like every 3th letter or so and some where was only some mess reboot fixed this. also have got some random crushes but had some with original 2.3.5. Also had some weird battery problems used battery to 0% loaded up to 100% and when started phone it says was still 0% and switching off stucked on screen replug battery fixed this.
batween on 1 and 2 rom didint clear cache did only factory reset between 2-3 (current) did full clear so wondering is my phone now bit mess cos didint do the cache and dalvik cache between 1 and 2 or is it normal to do some little bugs?
just wondering as i have now custom rom can i have back my original android what was in before root if it havent been backuped?
and last when you press power and - volum at start screen is hboot recovery and factory reset what will it do actually the same as in recovery or will it reset the devise to same state as it was when i 1st got it ?
Ty All!
Do not do the factory reset - it will only make things really bad.
When in recovery, before flashing a rom:
Wipe data/factory reset
Wipe dalvik
Format all partitions (except sd card)
That will make sure a good install of whatever rom you choose.
All ics roms are buggy. The devs are still working on them.
Suggestion: flash a gb rom.
You should be able to find a stock rooted rom if thats what you want.
Sent from a dream.
One you need to full wipe and then flash rom. On ice cold the messed up letters no need to reboot its the launcher so go into launcher setting and restart launcher should fix issue. If your on ice cold see if you have the cfs kernel or bfs kernel cfs is known to cause reboots. As for hboot you can enter recovery that way do not wipe factoey reset there without a rom on sd to flash. It erases everything and if you don't have a rom to flash after your will regret it and be back here asking why phone won't turn on.
Welcome and enjoy the reading and learning.
Sent from my Desire HD using xda premium
Been a bit confused on this. When I initially got this phone i317 (rogers), I rooted no problem, got TWRP running no problem and first thing did a nandroid. Flashed the older stable version of paranoid android 2.54 (i believe) which is based on 4.1.2. No issue what so ever.
As well before i go on, I've been rooting phones a while. Never bricked anything and definitely know the concept of the search button.
After running PA for a day or so and not seeing too many people having issues flashing roms on this phone i flashed another ROM (unfortunately I cant remember which one, but it was one of the popular ones on xda) TWRP had no issues flashing.
When the rom booted and android itself loaded i then had three FC errors and android rebooted. Ok thought it was a bit odd. Said screw it and recovered a backup. However any backup i flashed the error continued. Tried flashing the original PA rom again, the issue continued. Eventually had to reflash in odin the original rooted stock rom.
As you have read this issue has been resolved. My question is what happened? Is this a common problem with this device? Is it perhaps an issue going between 4.1.2 and 4.1.1? Is this just an issue with the devices internal memory? I have yet to read anyone having similar issues, however am not on xda as much as i used to be.
I am really just making sure that i am not missing something obvious or if this was simply an isolated issue before i sample some other ROMS floating around this site.
Any input is appreciated.
Sent from my SGH-I317 using Tapatalk
Did you happen to wipe data before you flashed the new Rom? I have never experienced any force closes while flashing roms.
This is what I usually do when going in between roms.
1. Wipe data/cache twice
2. Flash rom
3. Usually start to hate the Rom after the first minute.
4. GO into recovery
5. Wipe data twice
6. Restore from CWM recovery.
7. Fix permissions (just in case there was a mixup (usually helps resolve force closes)
Hope this helps. If you do happen to wipe data then I am as lost as you are . Maybe try fixing permissions? I am fairly new to android but I have been picking up modding it pretty quick.
______________________________________
Phones: iPhone 4 - > iPhone 5 - > Note 2 (Always on AT&T)
ROM: International N7105XXDMA6 by miscom
LINK: http://forum.xda-developers.com/showthread.php?t=2016575
Kernal: Perseus alpha32.1
A lot of bloatware removed.
Screen on time after normal charge: 7-8 hours always.
I don't think this is a process thing.
I always full wipe before a new rom, clear dalvic and such. This was something different.
Have been stuck in many a bootloop, but never one that caused rebooting when a recovery is flashed or a different rom for that matter.
Sent from my SGH-I317 using Tapatalk 2
Some ROMs require a factory reset wipe on top of the cache and dalvik wipe. I've used PA, and when I did the standard cache and dalvik wipe to PA from JellyBeer, I had repeated FCs, which namely was System UI. Even a nandroid restore after a cache and dalvik wipe had no effect. I was still getting the same FCs. I ended up using all four wipes with TWRP and a clean flash of JellyBeer, then a nandroid restore, to get rid of the FCs. Of course, several of my settings got wiped, including DPIs. Some ROMs just don't play well with other ROMs without a factory reset after the cache and dalvik wipe, which gets rid of your settings for a clean flash.
The other possibility is you're going between 4.1 and 4.2 ROMs. 4.2 ROMs create a new directory that puts all your files into due to multi-user login capabilities. Switching to a 4.1 ROM would certainly cause confusion within the phone without transfer the files back outside of the new directory.
Thank you. That was exactly what I needed to know. Was a scary issue the day after I purchased this phone outright lol. Not an issue I've experienced before with any other device.
Cheers.
Sent from my GT-N7105 using Tapatalk 2