Hi,
This update.zip is for Cm7 users having the problem, that if the screen goes off the phone reboots/goes off. Jerpelea has included a baseband folder into his updates and mentioned that the rom only works with this modded baseband correct, but if you use this fix please also flash the following ftf bundle with flashtool.
Requirements:
Cm7 by Jerpelea
Files:
435FW+bb52_from_bb-collection.ftf
Cm7_when_screen_off_fix.zip
Installation:
Flash the ftf bundle with flashtool
boot into recovery and flash the when_screen_off_fix.zip
boot into rom
Info:
Before saying: "After flashing this my phone only WLODs or FC's", please try a clean install first!:
Flash the ftf bundle using flashtool
Go to recovery
Flash the newest Cm7 rom
Flash right after the rom the fix
reboot
here you are
I AM NOT RESPONSABLE IF YOU BREAK YOUR DEVICE OR DROP YOUR COFEE !
Cheers,
L
good idea...
yea, i wrote a long reply in my other thread. With this solution i haven't to make always a new update.
@9Lucas5
Hey buddy, good idea on the thread, it will be easier to follow as this does not confuse the busybox issue for wifi fix.
Anyway, how about a instruction of use for the op also clearing up questions like do we have to flash them everytime a new cm7 release is out, what sequence do we flash these ie before/after flashing the rom.
Lastly Doomlord has been trying for weeks to find the cause of this issue, at my request, J & Z have given there thoughts, we all appreciate everybodies help with the fixes and input, i read your post and explaination and respect what give to our forum, i think doomlord was confused about the busybox issue and probally thought you knew more about the system bin/xbin, we will find a solution working together, thanks for all your hardwork.
The problem just started for me, I think it is because my batery went bellow 20% is this fix also for that or only for when it happens always ?
depulle87 said:
The problem just started for me, I think it is because my batery went bellow 20% is this fix also for that or only for when it happens always ?
Click to expand...
Click to collapse
I only know that my fix fixes the reboots appearing right after turning off the screen. I don't think that it fixes also this, but try it.
tried it and you are right it didn't fix it, I'm wrong here cause it just happened when screen on so it is the low bat issue not the screen off issue.
however your method did not break anything and for the first time my phone said it was booting into custom kernel
does this fix random wlod and reboots ?
ok, I'll repeat again. I don't know what this maybe is fixing too, but i think it's nothing, cause there aren't many files in it. There are only the miniloader and the splboot.ko in the update.zip. I only know and say, that it fixes the screen off = reboot problem. Other things, please simply try. If it fixes anything else you can post it.
Shouldn't be getting WLOD on This version!
I take it your using the loader that came with the main update.zip?
superleeds27 said:
Shouldn't be getting WLOD on This version!
I take it your using the loader that came with the main update.zip?
Click to expand...
Click to collapse
I'm using the loader came with z's incall volume fix kernel
Battery below 25% reboot.
depulle87 said:
The problem just started for me, I think it is because my batery went bellow 20% is this fix also for that or only for when it happens always ?
Click to expand...
Click to collapse
The below 25% battery issues got fixed for me when i reset the battery stats on the xrecovery. this got really fixed just doing that right after fully charging the battery. I think this most likely is the battery issue, because it one of the only variables between phones. The battery stats reset should always be done when the battery is totally full or very near that.
this patch saved my fathers phone - and so saved my evening!
thanks a lot! there actually ARE people out there with that screen off reboot issue.
i wonder why the xperia community seems to have less team spirit than i am used to (from other phone communities i participated in) - i would at least expect that this issue is mentioned and this thread linked on the first post of cm7 - i also dont understand, why various hardware issues are solved on various roms, but not overall...
like i said - this community is "different" to me anyways, thanks for solving this issue, giving my dad latest stable cm7 (including my personal work and taking care of this device anyways
regards
Download links no longer working so thread closed...
Related
My phone started rebooting several times. At first I thought it was the custom ROM, but it started happening in ALL roms I tested, specially when I try to test GPS: it just NEVER works. And that also happended with completely different basebands (Tested .49, .52, .54 and .58), 2.1, 2.2 and 2.3 ROMs.
My last attempt was to a clean Froyo FreeX10 beta install. Bb .54, Full wipe, etc etc.. For a few hours everything was normal but when I tried GPS (Google app) it restarted and ended up in a boot loop. Removed battery but it continues into loop.
Should I flash SE original ROM again (using SEUS?) to see if works? I'm out of ideas right now, please help!
Arrrgh! It's even worst than I thought. I tried flash Generic version 2.1update1 build 2.1.A.0.435 and the random reboots persists.
Also I noticed some weird things using Wifi, downloads on Marked just doesn't start, get paused like forever... HELP!!!!
I suppose force a repair with seus.and if that doesn't fix it then it might be some hardware issue :/
Sent from my Delorean using a flux capacitor!
Thanks. I even formatted my SD Card but still with problems, I'm thinking about buy a bigger/faster one and maybe another battery, but if it's the phone itself the problem then I'm in trouble.
PS: I tried SEUS but no go :S
sounds like the same problem i and other users have faced, tell me when the phone reboots take the battery out and give the phone a smell, does it smell like burning? mobo has gone
I say remove the GPS app using adb. Then flash a new ROM from scratch. Then install another GPS app.
lolman2810 said:
sounds like the same problem i and other users have faced, tell me when the phone reboots take the battery out and give the phone a smell, does it smell like burning? mobo has gone
Click to expand...
Click to collapse
Ouuuuch! It does! I thought it was the battery dying but in this case should I flash back to stock and use my warranty?
kozxmartt said:
I say remove the GPS app using adb. Then flash a new ROM from scratch. Then install another GPS app.
Click to expand...
Click to collapse
Thanks, didn't even know it was possible, will give it a try but now I think its the mobo
what is moboo?
mobo = mother board
Just FYI, my phone is on technical assistance right now and they informed it will take long because many X10 are having the same issue, it will probably be escalated to SE and I will probably receive a new one
Now let's wait, will report back later.
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
psychoticdemon said:
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
Click to expand...
Click to collapse
The kernel is incompatible with your phone.
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
psychoticdemon said:
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
Click to expand...
Click to collapse
kernel is for mango??unofficial port right...can you provide the rom link once.....??
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
psychoticdemon said:
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
Click to expand...
Click to collapse
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Dark Wraith said:
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Click to expand...
Click to collapse
Thanks a lot for pointing it out, mate! Usually the roms I tried didn't require such a thing, but this might be it. I'll provide feedback if the steps works.
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
psychoticdemon said:
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
Click to expand...
Click to collapse
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Dark Wraith said:
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Click to expand...
Click to collapse
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
psychoticdemon said:
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
Click to expand...
Click to collapse
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Dark Wraith said:
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Click to expand...
Click to collapse
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
psychoticdemon said:
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
Click to expand...
Click to collapse
Yeah.....waiting for other roms wont work.....cz they are all based on 3.4.x kernel.......Umm can you check your baseband after flashing full ftf...baseband should be : 8x55A-AAABQOAZM-203028G-77..every other rom based on 3.4.x kernel works right???...btw if you want to see how it looks just download a kitkat launcher from playstore....
Yes, the baseband is .77 after flashing the ICS 4.1.0.B.587. I used 3.4.x kernel with CM10.1, but never really tried CM10.2 to that extent. Maybe I'll try downloading that and see if it works... or even the EOL CM10.1.
And sure, the launcher would give in the feel, but I want the full experience possible really.
Hi
I was using the previous version of Iced Bean and liked it a lot. However after only one month it became slow. Seeing that a new version was available, I flashed 4.0 on my Xperia Ray with a stock kernal. The ROM has several new features and I liked it a lot. But there were a few bugs that I would like to report here for the developer and in case anyone knows an easy fix for them.
The telephone icon disappears regularly. Fancy features are fine, but easily using the device as a phone is a must
The ROM became very laggy almost immediately after installing my favorite apps. Rebooting did not help and there is pleanty of free space on the phone and on the SD
The internet browser crashes a lot. This was also a problem in the previous version.
I can not turn off 180 degree rotation of the screen. For me, this alone is almost a deal-breaker.
I hope this message will be found by the appropriate people. :fingers-crossed:
r4tty said:
Hi
I was using the previous version of Iced Bean and liked it a lot. However after only one month it became slow. Seeing that a new version was available, I flashed 4.0 on my Xperia Ray with a stock kernal. The ROM has several new features and I liked it a lot. But there were a few bugs that I would like to report here for the developer and in case anyone knows an easy fix for them.
The telephone icon disappears regularly. Fancy features are fine, but easily using the device as a phone is a must
The ROM became very laggy almost immediately after installing my favorite apps. Rebooting did not help and there is pleanty of free space on the phone and on the SD
The internet browser crashes a lot. This was also a problem in the previous version.
I can not turn off 180 degree rotation of the screen. For me, this alone is almost a deal-breaker.
I hope this message will be found by the appropriate people. :fingers-crossed:
Click to expand...
Click to collapse
Seeing as you are under the number of required posts to post in the Development section, here are some steps/suggestions that may help:
Re-flash the firmware (FTF)
Install a recommended (if there is) kernel
Enter the recovery menu
Wipe cache and dalvik-cache
Install ROM
Waiting for a few minutes for the ROM to settle. There usually won't be any issues if you have performed the procedure mentioned above.
sinstratos said:
Seeing as you are under the number of required posts to post in the Development section, here are some steps/suggestions that may help:
Re-flash the firmware (FTF)
Install a recommended (if there is) kernel
Enter the recovery menu
Wipe cache and dalvik-cache
Install ROM
Waiting for a few minutes for the ROM to settle. There usually won't be any issues if you have performed the procedure mentioned above.
Click to expand...
Click to collapse
Thanks for the reply. I tried these steps already and have moved on to another ROM.
Perhaps there was an issue with my phone in particular or a problem with compatibility with one of the apps I like.
Cheers, XDA colleagues
In first place, I want to apologize in advance for English mistakes, because I have only a basic knowledge in that language and I'm typing it all at the end of the night, here. So, I'm somewhat oblitered by the sleepless time I spent diagnosing and trying to fix some problems I had while flashing CM11 to my Xperia M device.
Well, due to some mistakes when installing GApps (I didn't want to be all-connected to Google), I have formated and reinstalled the system at least four times. Now, at the fourth time, I had everything more ou less setted up the way I wanted. Had some commonplace apps -- like WhatsApp -- installed, some UI features customized. At this point, I tought "Uff... Now it's all done".
However, it wasn't. Actually, I'm running into a bizarre problem with sleep mode, a few time after being locked. When my phone enters it, it won't exit. To make things a bit more clear: it dies, and in a way that's necessary remove battery and put it back on to turn it on again.
I'd check syslog and dmesg, but I don't know where are them at the Android filesystem (in fact, I haven't used *nix in a couple of years). So, I'm relying to my dear colleagues of these forums, if they have a clue on what's going on.
I'm using FXP330 ROM (http://forum.xda-developers.com/showthread.php?t=2584956).
Thank you very much!
Att.,
P. Pinheiro
Bumping it up.
system files are very delicate. what exactly did u modify because this means u re gonna need to reflash the whole rom
Ambychy said:
system files are very delicate. what exactly did u modify because this means u re gonna need to reflash the whole rom
Click to expand...
Click to collapse
Hi, Ambychy, thanks for the reply!
Yeah, it's actually what I ended up doing. Now it's working with no interruptions. Shame I'll need to reflash it because it had no GSM signal, and to make it work it's necessary reflash stock 4.3, and have 4.3 baseband flashed. So, for all effects, the subject of this thread were solved.
But it's what CyanogemMod about: it's a geek way and you'll run into some problems, but in the end everything got be working fine and in highly costumizable way.
Cheers
No problem mate we all gotta help each other
Hello.
I was able to fix the random reboots i had with flashing prerooted zip via TWRP, this apply also on the new 26.1.A.3.111, only tested on E2306.
1. Must backup your data. You are gonna wipe it
2. Use flashtool and downgrade to a rootkitXperia rootable firmware. I used 26.1.A.1.112 but other rootable should be the same. (wipe data may not be necesary in this step but i did it just in case)
3. When flashing done, root the device with rootkit, and install TWRP
4. Use xperifirm to download the 3.111 FW then create the prerooted with its system.ext4 and kernel.elf
5. Flash the zip via TWRP, wipe dalvik, then start the phone and check that you have superuser, and go about phone to make sure everything went well and your in 3.111 with its kernel also.
6. Use flashtool again to flash 26.1.A.3.111 but you this time you must EXCLUDE SYSTEM and KERNEL to keep the root, in other words your gonna flash everything but kernel and system so be sure you ticked them, also should wipe data so you can start fresh and avoid possible incompatible things.
7. Let the phone starts, mine took around 10 - 15 min. You should now be in 26.1.A.3.111 with root and no random reboots. So far im using it since 12 days and no reboots nor system hangs, ive updated all apps via playstore, and even downloaded several 500Mb+ games and its working really fine
Click to expand...
Click to collapse
Sorry for this guide that isnt noob friendly, im doing it quite hurry because im too busy with work but i wanted to share what worked for me with everyone. If this works for you too and someone wants to do a better noob friendly guide with links and such go ahead it is ok.
[NOTE]Random reboots seems to happen when there are diferent modem versions. Special thanks to @sergioslk who discovered this.
Of course, all credits to the respective developers who worked really hard on this tools for us. Thanks devs.
Hey, thanks. I had 26.1.A.2.167 rooted, so I just installed 3.111 with data wipe through prerooted zip on top of 2.167, and then reflashed everything except for kernel and system (also data wipe here) like you wrote in your post. So far so good - almost 30h without reboot, which is far better than before.
Hm, didn't work for me also with 3.111 I reflashed (using stock 3.111 from xperifirm) excluded kern and system but it is still randomly rebooting when installing gapps.
fpghost84 said:
Hm, didn't work for me also with 3.111 I reflashed (using stock 3.111 from xperifirm) excluded kern and system but it is still randomly rebooting when installing gapps.
Click to expand...
Click to collapse
Did you first flashed via TWRP the prerooted zip you created with system.ext4 and kernel.elf extracted from 3.111 FW? did you wiped data after completing flash? which version of FW you had just before flash 3.111?
Yeah, I did as you say. My phone orig had 2.167, but it upgraded itself recently to 3.111, then I downgraded to 1.128 to root, before using the prerooted TWRP zip (with system.ext4 and kernel.elf extracted from 3.111 ftf) to upgrade back to 3.111.
EDIT: I think something went wrong when I created the ftf bundle from the files downloaded from xperifirm. I repeated the whole process and now I'm not seeing the random reboots (at least for an hour with quite a few apps installed and updated) ....So yeah in summary many thanks for this ...It would be nice if it was mentioned on the main how to thread.
thewailer said:
Hello.
I was able to fix the random reboots i had with flashing prerooted zip via TWRP, this apply also on the new 26.1.A.3.111, only tested on E2306.
Click to expand...
Click to collapse
Thanks so much for posting this. I had thought of doing this myself but quickly ruled it out because I thought it was a dumb idea (no offense) and wouldn't work, but after hearing of your success I thought I'd give it a try anyways and I've been powering through a ton of app installs/updates and haven't had a single reboot so far. It sounds to me like this is the key.
I'll post an edit after a few days to let you guys know how it holds to my personal test of time.
Thanks again!
Update:
Well, it's been nearly a week now and I've yet to experience a random reboot. This is definitely the fix we've all been waiting for! I hope this knowledge can be spread to all who have been plagued with this issue!
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
sergioslk said:
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
Click to expand...
Click to collapse
Hey @sergioslk,
Thanks so much for your contribution. I found your post about this problem but it was kind of hard to read whereas the original poster here went into a bit more detail. Sometimes that's all people need, is a little more information. I'm sure you've made other contributions to the community that have been extremely valuable.
To reitterate, this is definitely the fix to the problem we've all been facing when it comes to using the pre-rooted zip to get root on the latest version. I had suspected this to be the problem awhile ago but couldn't really figure out how to fix it.
Thanks everyone for all your hard work!
sergioslk said:
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
Click to expand...
Click to collapse
Oh dude many thanks for this contribution, i havent readed your post before, but now i can say theres a know reason why the random reboots occurs. Im not an expert in android, i just tried this as a last hope, ive tried everithing, no google account, no wifi, no moibile data, no sdcard, deleting all bloatware, untouching bloatware, a lot of wipes..... and this last one for some reason worked but i wasnt sure why untill now. Thanks again!