Related
I am a T-Mobile client using their ROM. I upgraded on KIES suggestion the Kernel to the most recent version:
PDA KF1
Phone KG2
CSC KF3
I am running in Android 2.3.3.
Phone is rooted.
I used busy box 1.17.2 and 1.19. Currently, it is 1.18.4
Everything runs fine, however, shortly after SMS usages (Messages) or telephone calls the phone either goes in a loop of MEssage - FritzBox App - Firefox. I can close the last apps while the first stays alive. No usage of anything else is possible before reboot. Sometimes telephone calls are terminated and phone shuts down.
I hope I could explain a little bit what happens. I tried to look for an error log to be more specific.
My question now is:
What causes these problems, my best guess is that the kernel is the source as it it happens only after "Communications". Is this a known issue or is there more wrong to the phone? Too many apps or a specific app?
Teddybear2 said:
I am a T-Mobile client using their ROM. I upgraded on KIES suggestion the Kernel to the most recent version:
PDA KF1
Phone KG2
CSC KF3
I am running in Android 2.3.3.
Phone is rooted.
I used busy box 1.17.2 and 1.19. Currently, it is 1.18.4
Everything runs fine, however, shortly after SMS usages (Messages) or telephone calls the phone either goes in a loop of MEssage - FritzBox App - Firefox. I can close the last apps while the first stays alive. No usage of anything else is possible before reboot. Sometimes telephone calls are terminated and phone shuts down.
I hope I could explain a little bit what happens. I tried to look for an error log to be more specific.
My question now is:
What causes these problems, my best guess is that the kernel is the source as it it happens only after "Communications". Is this a known issue or is there more wrong to the phone? Too many apps or a specific app?
Click to expand...
Click to collapse
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?
0semaj0 said:
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?[/QUOTE
Root Kernel is KG1 from Odia. Happened before with the other Kernel as well. I already cleared cache. There is no insecure KG2 for T-Mobile available. Any idea how to make the Kernel rootable/ insecure. I suspect it must have something to do with the Kernel. For rooting, I try always to get the insecure version of the branded one. Different kernels (insecure/ secure) that do not completely match could cause this?
Maybe I have done something wrong which is the solution. Let's start from scratch how I rooted the phone.
I had original Kernel on the phone. From this one, I upgraded straight to the insecure, rooted and than just put one the most recent one.
Is this causing the problems? So better upgrade to the next official one, than use the insecure to root and than put the official one back on. All done via ODIN? Would this be the solution?
Click to expand...
Click to collapse
I used KIES to get the orginal KERNEL on the phone. So far no problems there. I want to test it over a couple of days and then root it again. Hope this fixed it.
2 Hours later
Okay, after roughly 2 hours I came back in this loop with Internet/ Messages. I cleaned the RAM and now it works fine. Why does this happen? Never had this before. Is this an App causing or just the Kernel. I could use ODIN to get back to the first Kernel that was preinstalled. Phone is currently not rooted. However, when I use ANDROID system Info (App), under BuidlINfo I see Type: USer and USer: Root. Should I probably unroot first as the system is confused and thus these errors appear?
Hope some could help here to clarify.
Need help and advice to fix problem!!!!!
Is this what I did wrong?
I had Kernel KF3 on the phone and put straight the insecure Kernel KG1 via Odin to the phone, rooted and then had original KG2 on it. This was the time when things got worse. Had the problem with KF3 already altough I first went to KF3 via KIES and then ODIN/ SuperOneclick/ ODIN for original firmware.
Does someone have an idea how to fix it? Going back to the first firmware and upgrade then to the most recent one? Anything to check in ODIN apart from the ususal ticks in F.Reset and AutoReboot?
Please help as it is get really annoying to reboot every now and then during the day.
0semaj0 said:
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?
Click to expand...
Click to collapse
I always thought power on/off is similar to Reboot. I was proven wrong. I just rebooted with volume up+home+power. Since then phone is stable. Sometimes TWLauncher crashes and reloads.
Thanks for the support. I think this has been fixed....hopefully.
Teddybear2 said:
Is this what I did wrong?
I had Kernel KF3 on the phone and put straight the insecure Kernel KG1 via Odin to the phone, rooted and then had original KG2 on it. This was the time when things got worse. Had the problem with KF3 already altough I first went to KF3 via KIES and then ODIN/ SuperOneclick/ ODIN for original firmware.
Does someone have an idea how to fix it? Going back to the first firmware and upgrade then to the most recent one? Anything to check in ODIN apart from the ususal ticks in F.Reset and AutoReboot?
Please help as it is get really annoying to reboot every now and then during the day.
Click to expand...
Click to collapse
KF3 and KG1 is very different...since the F and G is well, obviously different. Usually if you matched a KF4 with KF3, it should be ok but KG1 is quite different. As with anything at this point in time for you is to flash to a stable ROM currently released, which is KG5 since there are root kernel available for KG5. It is the most recent Kies official release. KH3 is newer but not official Kies. If you update to KH3, you may not be able to gain update through Kies, therefore stick with KG5. Both are Android 2.3.4 for you information, hope that solves the issue and remember to clear all Cache and Dalvik in your case since you already have issues...
0semaj0 said:
KF3 and KG1 is very different...since the F and G is well, obviously different. Usually if you matched a KF4 with KF3, it should be ok but KG1 is quite different. As with anything at this point in time for you is to flash to a stable ROM currently released, which is KG5 since there are root kernel available for KG5. It is the most recent Kies official release. KH3 is newer but not official Kies. If you update to KH3, you may not be able to gain update through Kies, therefore stick with KG5. Both are Android 2.3.4 for you information, hope that solves the issue and remember to clear all Cache and Dalvik in your case since you already have issues...
Click to expand...
Click to collapse
Problem was that a system file for synchronisation (syncmldstmo.apk) was deleted. I do not know how, but I could restore it with Titanium. Since then, all my problems seem to have vanished.
My Apps does not work. I do not see any downloaded app. Seems to be a Google problem since I stumbled over several threads.....no solution so far. I asked them directly. No solution.
Hi. I have the Canadian SGS2 from Virgin Mobile.
I want to update the firmware on the phone but Im unsure as to which one to use. Right now the latest firmware for this specific phone is UGKG2. My model number is GT-19100M. Im just wondering which firmware would be the best to update to. Ive been having a few issues with my phone and apparently updating the firmware is suppose to fix it (like the Wifi sharing garbage that starts every time you tun wifi on, but doesnt go away when you turn it off)
Anyway - which firmware would be best to update to, or if it would be best to just update to the latest which I think is XKH2.
Help is appreciated. Thanks!
Yeah sounds like you are on an older firmware which a lot of us battled back in May with the wifi-sharing battery drain. You'd be safe flashing any ROM really. Not sure if you prefer stock firmware only or not as some of the custom roms are great. I'd suggest KH3 as many bugs have been fixed that are evident still in your ROM. But you may want to check to see if anyone has a backup of your current rom in case you need to take it in for warranty. I have an i9000 but friends who are using i9000m Bell model are able to flash any i9000 rom without issue as there really is no difference from what I know. If you do flash, keep in mind that your boot logo will say i9000 and not i9000M, which is why you may want to look into backing up your current rom (by rooting and flashing a custom kernel to make a backup) just in case you need to flash back for warranty repair.
I use Batista Rom and really like it but I always tend to prefer custom roms. I think you'd be better on any newer rom, stock or custom to get rid of the bugs you got in that firmware you're on
so to be clear - I can download KH3 and use Odin to flash without issue, Even though Im on the stock I9100m Virgin Phone? And KH3 is a single TAR file that needs to be placed under PDA correct? I basically just want my phone to be the exact same as it is now except with the firmware updated.
Will anything be different or will it all seem the same as if I were to do a factory reset right now?
Also where KH3 is 2.3.4 and my phone is currently 2.3.3 - this wont lead to issues when using Odin?
Thanks for the replies.
Ryne said:
so to be clear - I can download KH3 and use Odin to flash without issue, Even though Im on the stock I9100m Virgin Phone? And KH3 is a single TAR file that needs to be placed under PDA correct? I basically just want my phone to be the exact same as it is now except with the firmware updated.
Will anything be different or will it all seem the same as if I were to do a factory reset right now?
Also where KH3 is 2.3.4 and my phone is currently 2.3.3 - this wont lead to issues when using Odin?
Thanks for the replies.
Click to expand...
Click to collapse
Yes you can flash KH3 using Odin under the PDA section. Depending on where you downloaded the KH3 firmware it probably wont wipe your phone so I normally do a factory reset after just to make sure it's a clean install. Make sure you back up anything you don't want to loose. Also take note that the KH3 package includes files that will change your boot up image from I9100M to I9100. If you want to keep things as close to stock as possible you can remove these files from the package since you don't really need it: boot.bin/sbl.bin/param.lfs. All you need to do is use winzip or 7zip, double click on the .tar file and delete.
Haha. Thanks for the replies.
I'm happy to say that everything went without a hitch - and all of my problems have been solved. One funny thing, was the camera shutter sound - which from what I read is suppose to be hardware related - was actually fixed as well - no more sound when opening the camera app.
Battery Improved
Wifi Sharing bug = gone
Shutter Sound = gone
Random restarts while listening to music = gone
And I got list view
Thanks guys!
im in the same boat. i just got a galaxy s2 a couple days ago. I just want to flash my phone to 2.3.4. Which firmware do i download? Where did you find KH3? thanks
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
I installed VillainROM 2.4.2 (ninphetamine-2.0.4 kernel) on my Bell Galaxy S2 phone a really long time ago and have been satisfied with it so I never bothered updating or anything. Now I'm a little bored with it and have been thinking about trying out ICS via CM9 nightlies. I just have a few questions before I give this a go since I'm out of the loop when it comes to modding:
1) To install CM9, do I just put it on my SD card and flash with CWM after doing a factory reset and clearing the cache? Or does jumping from a GB kernel/ROM to an ICS kernel/ROM require an extra step?
2) My version of CWM is probably old, so will I run into any problems trying to install CM9? I don't remember what the version is, but it's whatever version that came with the ninphetamine-2.0.4 kernel. If I need a more current version of CWM, how would I go about installing it?
I think that's all.. Thank you for reading.
As long as you follow the instructions, it doesn't matter what you're coming from. See full instructions here http://forum.xda-developers.com/showthread.php?t=1419102
Notice that for the CWM method, the third instruction is to flash a particular CWM recovery to avoid potential problems. There are instructions on how to flash on the link to it.
n125 said:
I installed VillainROM 2.4.2 (ninphetamine-2.0.4 kernel) on my Bell Galaxy S2 phone a really long time ago and have been satisfied with it so I never bothered updating or anything. Now I'm a little bored with it and have been thinking about trying out ICS via CM9 nightlies. I just have a few questions before I give this a go since I'm out of the loop when it comes to modding:
1) To install CM9, do I just put it on my SD card and flash with CWM after doing a factory reset and clearing the cache? Or does jumping from a GB kernel/ROM to an ICS kernel/ROM require an extra step?
2) My version of CWM is probably old, so will I run into any problems trying to install CM9? I don't remember what the version is, but it's whatever version that came with the ninphetamine-2.0.4 kernel. If I need a more current version of CWM, how would I go about installing it?
I think that's all.. Thank you for reading.
Click to expand...
Click to collapse
Easy enough upgrade path
If you are worried about doing this, flash the ODIN "resurrector" CM9 package - it should sort out wiping and everything else for you.
If you want to do it via zip, put the zip file on the SD, do a nandroid backup, wipe data and cache, then flash the zip and latest ICS gapps.
I don't think you'll have any issues with installing CM9 using that CWM. If you do, ODIN flash latest Siyah Kernel. Go to recovery and flash CM from there and you'll be fine
Thanks for the help guys. I went with the CM9 Odin Resurrection method and then updated to the latest nightly (20120511) with CWM.
I'm very impressed with what I see so far. I'll have to keep an eye on it, but I am a little worried about the battery life. (Though considering that I am on a nightly build, less than optimal battery life might be expected..)
Also, my signal strength seems to be fluctuating a bit, usually between 3 and 4 bars, although sometimes it will go down to 2 bars. The modem that came with this build is XXLPQ. Is there a better modem that I can try, or is it just a matter of going through all of them? I was on MUGKG2 previously and it was quite stable for me.
I think LPQ must be your earlier Modem which is retained after instlling CM9, if I am not wrong CM9 doesnt contain a modem.
try KE7 modem, I have got a very nice experience with KE7 on ICS roms
So I've rooted my phone less than a month ago, and I get this bug where the phone just freezes for 10-60 seconds, pressing the power button does nothing, I just have to wait until it sorts itself out. It happens quite often, and it's really annoying. One guy mentioned the same bug in the HTCDev unlock/root thread, but he was lucky enough to have the AT&T version, so he was able to get back to stock with the ruu.
I've already performed a factory reset twice, but it didn't help.
Does anyone know what my course of action should be? Should I download one of the back-ups, which one and so on. Also, how to get back to stock recovery, because TWRP doesn't let me do OTA upgrades.
I bought the device in Croatia, if that means anything, because I've seen dozens of different twrp backups so far.
Thanks in advance guys
HTC Desire 610 AT&T and EU is not 100% same phone, firmware also have pretty different version numbers: latest AT&T is 1.53.502.1* EU 1.31.401.3(Croatia).
So you cannot expect that everything will go without any problems.
Sorry I replied before I fully read your question.
You're on the stock Rom and kernel?
Stock rom, JMZ's kernel.
JMZ probably took source code from HTCDEV for US(AT&T) version of phone, some people with EU/International version of phone have similar problems like you (member DulinDuskhawk) with JMZ Kernel.
Please go to thread "Jmz A3UL Kernel v1" and ask someone for stock EU kernel or send message to member DulinDuskhawk, maybe he found a solution.
TomoBero said:
JMZ probably took source code from HTCDEV for US(AT&T) version of phone, some people with EU/International version of phone have similar problems like you (member DulinDuskhawk) with JMZ Kernel.
Please go to thread "Jmz A3UL Kernel v1" and ask someone for stock EU kernel or send message to member DulinDuskhawk, maybe he found a solution.
Click to expand...
Click to collapse
Hi TomoBero, I'm not 100% sure but I think jmz's kernel is made from 1.30..... international htc sorces (I'll check soon for exact version) as there where no at&t sources available at the time he did it. I think most problems with flashing other kernels is the fact that HTC built kernels are configured to only be able to load modules that were compiled specifically for that kernel. This is definately what has caused wifi to stop working for many people who have flashed other peoples backups or at&t rom(withut backing up atleast the own /system/lib/modules from their origianal rom as when gong back to their original kernel the modules no longer match the kernel). I have a build environment set up for compiling the kernel and have local sources for 1.29.... asia ,1.31...... EU_international, and 1.30.....US at&t. I can (and have) compiled these kernels as stock with just the flag changed to allow loading of modules that don't match version. If you let me know the software version number you (or others) are running I can supply a kernel update.zip and seperate /system/lib/modules.zip that matches software version and you to return to stock and experiment with modules if still having promlems. I havn't merged jmz's insecure /system code into these sorces so apart from allowing the kernel to load non-matching modules they are comletely stock.
MiniBlu
Hi MiniBlu, it's 1.31.401.2
Do you by any chance know how I could return my device to stock recovery, so i can install OTAs?
Thank you so much dude
I'm in the same boat. I'm trying to get back to stock, somehow.
I really need to go back to stock as soon as possible, the sim card locking mechanism doesn't work all of the sudden, and I've read it has happened to hundreds of 610s already. Because I'm unsure if my guarantee will work after root (although it's a hardware fail), i really need to get rid of the red disclaimer at boot (although I sadly think it can only be achieved with S-OFF). :c