Just installed new rom on phone.
Keeps rebooting every couple of minutes. Now I am not sure if it happened before I installed rom or not as I just went straight ahead and installed it as I have just received a replacement handset from a broken screen.
Any help?
Sense rom? Aosp rom? Rom name? Root? No root? More info man...
*Swaypovano sa Desire S BRE*
Saga3D v3.0 (Desire S official Sense 3.0) - [2.3.5] OTA 2.10.401.5
That rom. Installed the new hboot and orig stock kernal
Assume you have rebooted into recovery and wiped data, cache and dalvik cache, then tried to reboot?
Yes, I have done that a couple of times. I left it on connected with cable overnight and it doesnt seem to have rebooted. Seems to point to a battery problem??
It does boot properly. But after a minute it just restarts.
Edit. A bit more testing and it doesnt reboot when using a game or app. As soon as it closes to main screen it seems to just reboot as the screen goes into standby.
Edit 2. I have changed setting to stop screen turning off and its not done a reboot for the whole 10 minutes.
Does anyone think its a warranty claim? Or any more things to try?
Warranty claim seems a bit drastic, I'd try installing the rom again, or try a different rom, Endymion is sense 3.5 and stable... I was toying with it today, or pre rooted stock or even cm7 which at least you know is also rock solid
Sent from my HTC Desire S using xda premium
Just tried cm7 and it does the exact same.
Edit.... tried 4 different roms now. Going to go to stock with s-on and test. Then back to the shop again
Edit 2. Just use RUU on it and it is the same. Looks like I need to return it yet again.
Any more tips before I take it back in?
I had the same problem after 2.3.5 update. Went back to old version and it's fine now.
Assuming that you are not OC or UV then continue, else adjust to stock settings and re-try.
I recall a couple of others having a similar problem that was caused by either
a) loose battery connection, resolved by placing a piece of folded paper on top of battery to ensure it sat solidly in the slot.
b) dodgy battery, suggest that you contact HTC support, explain that phone keeps rebooting you suspect battery and request that they post you a new battery - don't post old battery back until you are sure its the battery at fault.
Hi,
so here's my situation: I've previously installed CM7 by tj_style (http://forum.xda-developers.com/showthread.php?t=1167750) on my phone and everything was working fine.
About a week ago, I flashed an overclocked kernel by squadzone (http://forum.xda-developers.com/showthread.php?t=1344440) (I flashed the 782MHz kernel, but after that for a while and getting a lot of shut down, I turned the max frequency to 715, which stabilized the phone) and again, it worked well.
I downloaded an app called Cpu Tuner from the market (https://market.android.com/details?...SwxLDEsImNoLmFtYW5hLmFuZHJvaWQuY3B1dHVuZXIiXQ..) because I wanted to try a new cpu tool (Had Antutu's Cpu Master free edition before). I used the "Check phone's capabilities" option on the Cpu tuner, and all of a sudden the phone just reboots straight into recovery mode. I try rebooting the system, and it gets stuck at the CyanogenMod logo, starts looping it without ever actually booting into the system.
I've already tried wiping data and cache (a lot), going back to stock Gingerbread, which by the way, does the same thing, loops the Samsung logo, re-installing the CyanogenMod and just about everything that comes to mind..
Is there anyone with a similar problem or any idea on how I could fix this?
PS: sorry about all the links, thought it might make it easier if it was clear what I was talking about
Okay, so I managed to get the phone working after all. I was already pretty hopeless, I read a few threads about the Riff Box and was ready to send my phone to the service, but I wanted to take a few last shots at it.
I got it to work by first flashing back to froyo, a package S5570XXJL9 that had separate files instead of a one package, then Gingerbread S5570XXKPI again with separate files, then to clockwork and finally CyanogenMod 7
Hopefully this thread may be of use to anyone facing the same problems as I've faced
I've had my phone up and running on AOKP Milestone 1 and a custom kernel (can't remember the name now) for a few months now. I decided to replace the kernel with Lean Kernel since my phone's been crashing recently, and it was mentioned that the kernel could be the problem (this thread: http://forum.xda-developers.com/showthread.php?t=1842971&page=135).
After installing the kernel and wiping the cache/Dalvik cache, my phone rebooted but would not let me past the lockscreen. I then pulled the battery and attempted to reboot into recovery, but now my phone won't turn on at all. I'm currently charging my phone but no light is coming on, so kinda worried.
Any advice/solutions would be appreciated!
EDIT: I should also mention that if I pull the battery and put it back in, I get a "battery charging" symbol on the screen for a few seconds.
Download mode?
Sent from my SCH-I535 using Tapatalk 2
Did you install the proper LeanKernel? If you are on AOKP milestone 1 that is 4.1 based. The newest LeanKernel is 4.2 based. Could be the problem. There are also distinctions between AOSP and TouchWiz kernels. Do you know which version you flashed?
Regardless, if you can get into download mode like hank said, you should be ok.
Can't Boot into recovery with three button method?
Tried getting into download mode?
Well I feel dumb but after some searching around, people recommended just blowing on the battery contacts. This solved it, so case closed! Thanks for all of the advice though.
And yes, the lean kernel was for TouchWiz roms, which got me into this mess in the first place.
So after all these black screen issues, I want to try and find a connection for those getting it. So, please answer the poll and if you got the black screen post the following info (example shown)
Phone model and version: MB865 ATT
ROM before attempted install: Stock ICS
Ever used a previous version of CM10: No
things tried to fix: back to stock, old version fisrt, etc.
any thing else you think might be helpful
Phone model: MB865 international (Claro, Argentina)
Rom: Stock ICS HongKong/Taiwan
CM10 before: Yes
Tried to fix: No, it worked the first time
I can't read all the answers in the rom thread, but, if i flash the rom and the gapps at the same times, i'll get the black screen. And, if you flash the rom, start your phone, use it and then flash gapps from cm recovery, then it have to work. Maybe it was coincidence, but in several phones it worked.
Phone model - MB865 Asia retail
ROM before installation - Stock ICS
Used previous version of cm10 ( you mean cm10.1?) - Used cm10 before , and now 3 different versions of cm10.1. ( the one before kexec and 2 kexec versions)
Black screen issue - No issue at boot. Boots properly everytime. Gives me black screen at random times like after a call, or while charging. I got it around 2-3 times, pulled the battery and rebooted.
After using the ROM for some days ( it's been a week now), no black screen issue.
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
I haven't experienced the black screen problem but any how
Phone model and version: MB865 ATT
ROM before attempted install: CM10
Ever used a previous version of CM10: Yes,CM10
things tried to fix: Didn't have to try.Have rebooted atleast 10 times since and still haven't got the black screen.
brianmoyano said:
but, if i flash the rom and the gapps at the same times, i'll get the black screen. And, if you flash the rom, start your phone, use it and then flash gapps from cm recovery, then it have to work. Maybe it was coincidence, but in several phones it worked.
Click to expand...
Click to collapse
I flashed the ROM and the gapps together without rebooting and haven't experienced the black screen problem.
Sent from my MB865 using xda premium
deveshmanish said:
I flashed the ROM and the gapps together without rebooting and haven't experienced the black screen problem.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yea, me too. But, the guys who has the black screen problem, they solved it with that.
---------- Post added at 04:07 AM ---------- Previous post was at 04:06 AM ----------
PS: Did someone tried with another gapps?
Model : AT&T mb865
Rom before install : SCV7 leak#1 based
Previous CM :yes
Things i have tried to solve ; none
It black screened me right after coming out of deepsleep , like other posts before mine, i rebooted my phone several times without having to battery pull , this is my booting secuense : first is moto logo, then white screen (2 seconds) then black screen (2 seconds) then cm bootanimation idk if it might help at all
Sent from the gray stuff inside my skull
Phone model and version: MB865 ATT
ROM before attempted install: CM10 (original not CM10.1)
Ever used a previous version of CM10: Yes
things tried to fix: Tried flashing with last version (3/28 build) of kexec and the latest version (4/3 build). With Gapps and without Gapps. Tried installing the CM10 Rom, booting into this rom, and then flashing the Kexec. Tried different slots System 3 and System 6. Before you ask I have modified the Rom according to instructions provided for BMM. Nothing works. The only thing unusual maybe that this phone was a replacement for my original Atrix2 after the original phone was hard bricked. This version also is factory clocked at 1.0Ghz and 4 clock stages vs. the original 5. I am not sure if this is an indication of different hardware. I think it's definitely a hardware difference causing the black screen as some of the other posts indicate plenty of people having success booting Kexec version with ATT Atrix2/MB865.
Model: ATT MB865
Cm b4 : yes
Stock rom : ics
Flash process: I flash the rom and gappps together in bmm recovery.
I use the converted kexec thru bmm. I get 1st boot success and the subsequent boots as black screen, or at least that is what I thought. I have went and let it simmer and found out that it my take a minute but... Looky there it booted. I went and used the converted 4/2 version ti upgrade and hadto reboot 2 times to get it to fly. Gotta love the silky smooth feeling. I have a radio problem that acts up so that throws another kink in it.
Atrix 2/ ATT /Bmm
1. Stock 4.0.4
2. Miui
3. PA 3.1.5 4.2.2
4. CMPA 4.1.2
5. Kexec 4.2.2
My stock ICS clock speed is 1.2 gigahertz. I also require through the performance mod down to 1.0 gigahertz and it is booted every time that I have power down first. I have it installed in slot 6
Phone model and version: MB865 Retail
ROM before attempted install: Stock ICS, PA3+, cm10.1, miui (tried with all).
Ever used a previous version of CM10: Yes.
things tried to fix: back to stock, different devtrees (other devices', different region, the ones of ME versions, flashing different devtrees to device using fast boot and combinations, my own as well), different display drivers, and quite a lot more. None have helped (so far).
You may also want to include the stock ICS max clock speed, if it ever booted up (even once) if it did boot up, was it with bmm or stock CyanogenDefy.
Stock ICS max clock speed :1.2 GHz
Ever booted up: Yes about 6 times. Completely random. Booted up with both bmm and CyanogenDefy recovery.
UPDATE: AAAND out of nowhere it boots up again. No idea how or why this time. BTW, its a fresh install in bmm slot 3. Took logs of last_kmsg, kmsg and dmseg. Any one wants anything else before the phone reboots and this rom may or may not come up?
Sent from my MB865 using Tapatalk 2
Phone model: ME865 (HKTWN)
Rom: 4.0.4. ME HKTWN ICS (translated to Hungarian language + implement some battery saving scripts)
CM10 before: No
Tried to fix: No, it worked the first time
Everything works fine, but the HDMI not working . I flash backmy own rom which is based on the JB Leak 2 (transleted it too).
Phone model - MB865 Asia retail
ROM before installation - Stock ICS searet
Used previous version of cm10: No.
Black screen issue - No issue at boot. Boots properly everytime. Noticed black screen only one time when one of application I worked (do not remember exacrly what app it was) with became frozen and I received a call at the same moment. I am not sure about call, i haven't heard ringing and haven't seen any caller id, only icon of conversation in notification bar. I turned off screen and tried to turn it on but without success. It was only possible to light buttons. Hardware reboot solved the problem.
Hey guys just wanted to make one thing clear, the black screen issue being discussed here is something that occurs even before the boot animation. Just after the M logo. Whatever happens after the cyanogenmod boot animation is ROM related. You get a black screen implies you can't even get to the boot animation.
Sent from my MB865 using Tapatalk 2
Phone: MB865 ATT
ROM before: stock ICS
When I first installed the first kevec update I got the black screen couple of time then I read about undoing the default 1.2ghz oc so I went ahead and did that, set it to 1.0 GHz set it on boot and it fixed my problem. I updated my A2 to the last update doing a clean installation and I have not experience any black screen so far.
Sent from my MB865 using Tapatalk 2
Phone model and version: MB865 ATT
ROM before attempted install: PA 2.57.3
Ever used a previous version of CM10: Yes
Things tried to fix: None
Installed CM 10.1 like the instructions. Kept getting black screens, and pressed power+vol up+vol down to reboot, but continued to get the black screen. Got super annoyed so I restored the backup I made before installing CM 10.1.
Ravi did u try to reduce clock speed as well.
Atrix 2/ATT/BMM
1. STOCK 4.0.4
2. MIUI
3. PA 315 4.2.2
4. CMPA 4.1.2
6. KEXEC 4.2.2
amynjimmy said:
Ravi did u try to reduce clock speed as well.
Atrix 2/ATT/BMM
1. STOCK 4.0.4
2. MIUI
3. PA 315 4.2.2
4. CMPA 4.1.2
6. KEXEC 4.2.2
Click to expand...
Click to collapse
If you are talking about the contents 2 posts above, that dosent even make a difference. I mean, when you are on one rom, change max clock speed and set it on boot, its only for that rom. And the max clock speed changes after the phone boots up and the app like setcpu changes it. But all that happens after the phone boots up. If it is even related to max clock speed, the only way to do that is to make changes in kernel.
Sent from my MB865 using Tapatalk 2
If I mess up and reboot u will always get a black screen. If I battery pull after that, it will boot after an undermanned amount of time. I even got some weird blue screen at some point thus morning and my phone started heating up. Finally battery pulled and got back into kexec again. Any method I have tried to get past black screen without battery pull yields more black screen. Power off will boot every time. What changes are made when booting between the 2. It is weird that we all get different results. I cannot even reproduce the same 2 times in the row unless I power down first.
Atrix 2/ATT/BMM
1. STOCK 4.0.4
2. MIUI
3. PA 315 4.2.2
4. CMPA 4.1.2
6. KEXEC 4.2.2
Phone model and version: MB865 ATT
ROM before attempted install: MIUI for ATT
Ever used a previous version of CM10: Yes before MIUI
things tried to fix: Reflash and multiple battery pulls.
I've actually gotten pretty good at pulling and booting since I've done it so many times. On average it take me between 20-30min to get the phone back up after a black screen. I've had several random reboots at the worst times and without skipping a beat a get to pulling and booting (can't be good for the battery).
Phone model: MB865 Indian Atrix2
ROM: Was initially in JB leak. FXZ to ICS Asia Retail version 4.0.4 to flash CM10.1
Previously had CM 10 before moving to PA.
Tried a couple of battery pulls but it did not boot. I flashed back the ICS 4.0.4 Asia Retail version to restore to a working phone.
~
Sayantan
Well the black screen seeks to be only because of the display driver.. Nothing to do with kexec. I changed some drivers and some of the previous errors were no more..
Sent from my MB865 using Tapatalk 2
Hello, some of you might recognize me as the one who was having trouble installing PA last night.
Now I've got it installed, and it runs very smoothly.
Specs off the bat...
TF700T Infinity
VoltageControl Overclock system set at 370-1800
Very latest gaps, installed last night from g+
MaxKernel V4 Reloaded RC2
Installed and flashed through TWRP
ParanoidAndroid 3.15
Likely enough for myself, all of a sudden, a few hours into having the ROM, kernel and gapps freshly flashed, the screen starts giving random graphical flashes and blips here and there, and it's grown to a point where I can't use my tablet without a flash every three seconds.
To explain exactly what is happening, when I switch from app to app or UI section to another UI section or any of the mix, it will brightly flash what I am switching to/from while I do it. For example, I will be opening up PIE and it will flash the app screen in full for a split second if PIE is over it.
Anything that I am doing wrong? I have a restore from a few hours ago set up, will I have to use that?
If anyone has any advice/assistance, please let me know.
Thanks,
Neb
EDIT: I tried resetting the overclocking system to stock clock. No change whatsoever.
Also did a restore. No luck
Turn off the corresponding setting in the developer options.
Also Max's kernel is a stock based kernel. I'm surprised PA even boots off it. I'd switch to a PA compatible kernel of I were you.
Thank you for helping me out on this. I saw some posts stating that Max was a PA based kernel. My bad. Got it taken care of by reverting to PA stock kernel