I'd like to ask those wishing help with troubleshooting to please help us to help you.
When reporting a problem it is useful to get as much information as possible, the more information we have, the easier it is to help.
Is it running from SD or Nand.
What radio version.
What build are you having the problem with.
What kernel/nbh are you using.
If you can, try to post any error messages.
Please try to post your questions in the thread for the build you are having issues with, it's more likely to get noticed there, and other users of that build may have the solution you need.
All this information saves a lot of time, and helps cut down on confusion, especially the SD/Nand part.
I have trouble with signal, it's weak than WM, when I used WM my radio is 1.65, I'm up to 1.71.09.01 and flash Android (NAND menthod) and the signal so weak
So Android support radio 1.65??? I want to back 1.65
I'm using TYTN 2 Kaiser _ WarmDonut version
Another Qs:
Q.How can I use my fone like a modem? I see in Menu have Modem but I don't know how to connect with my PC as a modem
Q.How can I connect to my PC via Wifi ad-hoc? (if available, please guide step by step- because I'm... chicken )
Q.GPS so slow and weak (in Vietnam)
Q.It so hard to power off (It's hang)
Best regard
I had issues with 1.71.xx radios too, and went back to 1.65.21.14 and my signal was good once more.
To change radio, download the radio you wish to use from this thread http://forum.xda-developers.com/showthread.php?t=393182, post 3 has the download links you need.
Once you have it downloaded, rename the ruu_signed.nbh to kaisimg.nbh and copy to SD card, flash using the power+camera method you used to flash the nand nbh, you will not have to reinstall Android when you do this.
The modem in question refers to the gprs modem used for data, it should be possible to use the phone as a modem, but as far as I know this is not working properly yet.
Not sure if you can do this either, I know wifi works for data transmission, but accessing the computer this way with android may not be possible, yet.
Gps problems may depend on which nbh you have installed, some of the more recent nbh's perform better than older ones. I'd recommend Kallt_Kaffes NBH's as I know these are quite good for gps, for me at least. http://forum.xda-developers.com/showthread.php?t=660158, you will need to load the nbh into the editor and set the correct panel type, keyboard, and 3d type, ( donut in your case), then save as kaisimg.nbh and copy to SD and flash using power+camera, again this will not affect your android install.
Power off issues may be nbh related also, however this can still happen anyway, usually pulling out the battery will sort out the reboot issues.
many thank for quick reply, I love Android on my phone
thank you again
I was wondering what steps to take when the android loader gets stuck in a loop, when I install andriod right after install it boots fine but when I try to boot second time, after andriod appears on the bottom of the screen it will go into some kind of loop. I have tried different radios and a different version of hardspl, and a few nbh panels as well as reinstalling the system, any help would greatly appreciated.
Phone: AT&T Branded TILT
OS: Nand w/Incubus Super Froyo Installed
Radio: 1.70.18.02
NBH: kaisimg-panel2-320-tilt-froyo-07-07-10
HardSPL: v3.34.hard
Everything looks fine, although I haven't used that particular build, however bootloops are commonly build or kernel related.
Have you tried other builds? Or is it just this build that does this?
Generally panel type only affects the display on the screen itself, or sometimes problems with sleep mode.
Since you have a froyo kernel installed, maybe you could install this build to see if it helps? http://forum.xda-developers.com/showthread.php?t=724821
Yeah I have tried other Froyo builds and they worked, but I just like the way Super Froyo build is put together. But if it is the build then its is the build. Oh well maybe next release. Ok thank you for your time, guess I will give the GZO build or the one you suggested a try.
Installed the kernel you suggested, it works. It boot looped once, then I cleared the dalvik cache and it booted again after install. I don't know if that is what it is used for, but it worked after that.
It is a awesome build, battery life works correctly, signal is good with radio, and wi-fi works good. But I had one more questions.
1. What is up with live wallpapers, on some builds I have used some work on one build but not the other, I have looked through the forums, but can find no solution for this. Is it because of the amount of RAM in the TILT as I saw somewhere or is there a fix. Even in this build when I try to load a live wallpaper on a couple of them is just stays on wallpaper loading and stay black screen.
I would like to take a minute to thank the people that make this awesome stuff, now my TILT has more current software than my BACKFLIP, so my older phone is now newer than my new phone, and I would also like to thank the people who help others out on this forum, I don't think a lot of people like myself would get anywhere without your help.
Forgot to mention dalvik cache. oops, ah well, you found it anyway
It's another of those occasionally useful things, like fix permissions, I have used it before to fix unusual behaviour, but not tried it on a bootloop.
Live wallpapers are usually pretty buggy at best, it's complicated, memory is one problem, cpu speed another, and 3d handling yet another, some wallpapers work ok, but slow, others just won't, ever. I just delete them before install, along with a few other minor customisations such as deleting a few ringtones and notification sounds, changing boot animations, nothing that affects the core of the build, just personalising a bit
I'm using:
1)incubus's Super Eclair 6.1, with the downgraded settings.apk which enables wifi (another member offered the settings.apk from a previous version (3, I think) as an androidupdate.tar)
2) Currently radio 1.71.09.01 (thinking of switching to 1.65.21.18 to improve reception)
3.) Currently using the latest Dzo kernel for eclair (07-02-2010, I think)
My problem is that my data connection doesn't work (and this has been an issue on just about every release, save for one Froyo install where the data autostarted once, and then I never saw a 2g/3g notification and mobile internet didn't work).
I'm currently in India, and I've used the correct APN settings (they have worked on other phones including Nokias, iPhone, and a USB modem). I've tried asking the question in the SuperEclair vogue thread, but alas, no love. I'd really appreciate if you could help me on this, or at least guide me in the right direction, because android (especially eclair) is too awesome to abandon for this single issue.
By the way, everything else works, Wifi (with the mentioned update), GPS, Voice, and SuperEclair is the fastest that I've found so far.
I have seen a number of issues with data such as this, and i'm afraid none have had a truly satisfying resolution.
However I would try:
Downgrade the radio as planned, this may help, and certainly won't hurt.
Boot to installer, and run fix permissions and clear dalvik cache, this has been known to fix various issues, not certain why yet.
Double check the apn settings, especially the MCC and MCN settings, a lot of online guides seem to miss these two, but they are important.
Not sure where to point you after this, apart from a long trawl through the thread here, however if you do get it resolved please post back, and if not, try another post on it in the build thread, along with the steps you have taken to resolve it, it may convince someone to have a closer look at this issue.
data connection
I too have had this problem after installing a recent froyo build to nand....I had checked no.start data when flashing dzo's latest kernel using nbh editor and had to reset my apn settings. Remember to open your modem utility and press connect twice....this actually starts the connection......Radio type could also be an issue..Ive had good luck with the 165's with 2 different froyo builds....Hope this helps.....
Thanks for the replies! I'm going to try this out (need to recharge the data service on my prepaid) but one thing I did notice was that the MNC/MMC were different that those listed on my providers website. Hopefully this will help.
I have tried to switch on the data using the modem utility, and the utility itself says that data is connected, but it never really worked. In settings, there is an on/off switch for mobile internet, and a mobile internet settings. When I click the on/off switch, then mobile internet just goes gray and does nothing. I'll try to post back to the Super Eclair vogue board, but I think that Incubus might have moved on...
I'll update once I get my gprs service paid up. Again, thanks for the help!
The process com.android.phone has stopped
Those are my first Android experiences, so I`ve got problems .
Phone : Kaiser (TyTN II)
OS : Win Mo 6 Profess (original-not flashed)
Radio : 1.27.15.32
I`m trying to install Android on the SD card, without additional partitioning. I`m currently trying this Android version : Eclair 2.1 for Kaiser/Vogue/Polaris -- polymod 2.1 gamma [Based on OpenEclair 1.2.2 (XDA thread)]
and using this too : How to run Polymod’s AWESOME 2.1 Eclare Build and Updates (the forum didn`t allow me to post links for the Android versions). I`ve tryed this too : VaniljEclair RLS7c - A fast and stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-07-02] - the same result
I`ve done everything according the instructions... Starting Haret.. Hit D-Pad, Install, clear data... etc. etc... It actually starts to install... and everything seems fine... At some point it brings me again the install menu, I`m hitting exit, and then come some errors ?!? I forgot to type them down... Something like that some files cannot be found... And after rolling errors for a while the Android actually boots ! But then come errors too... At the first time it brings me the dial pad to enter my pin-code... I entered it , but it says it is wrong...I wasn`t wrong ofc . For the next time I simply disabled my pin in Win Mobile and try again... After the Android booted it says : The process com.android.phone has stopped unexpectedly. Please try again. , and some button like "cancel" or something like that. I'm hitting it , the Android guy appears and a message " Hit the android to begin" with a hand pointing it. I`m hitting the android - nothing happened !
I`ll be greatfull if someone can help me , or at least give me some clues !
Thank you .
p.s. sorry for my english... not my native language ;-)
Your problems are mainly in the OS version, 6.0 is not recent enough to run Android, and the radio version will also give problems, my advice would be to update to the most recent stock version, which would enable you to run Android.
This would of course wipe your present installed OS and a more recent version may or may not exist for your language, ( with the wiki down I can't be more specific with which files would suit you best).
Thanks
zenity said:
Your problems are mainly in the OS version, 6.0 is not recent enough to run Android, and the radio version will also give problems, my advice would be to update to the most recent stock version, which would enable you to run Android.
This would of course wipe your present installed OS and a more recent version may or may not exist for your language, ( with the wiki down I can't be more specific with which files would suit you best).
Click to expand...
Click to collapse
Thank you for your fast response . But I`ve tryed (I`ve tryed again today) before to download an official WinMo 6.1 ROM from HTC_com , but according to my TyTN II`s serial number , they said : "Sorry, this software download is not suitable for your device". And I want an original ROM... I`m not sure that I can manage to flash a cooked one on my HTC . So I guess I`ll stay with the original WinMo 6.0 withut Android .
Thanks anyway
To flash a cooked rom you would need HardSPL, it is possible to do this for WM 6.0.
Regarding an upgrade to WM6.1, this too should be possible, I'd tend to disregard the warnings about upgrades being 'unsuitable'. The unavailability of certain upgrades is more to do with them being designed for certain providers or areas, rather than their actual unsuitability for the device itself.
If you have a need for a language specific rom this too is probably available from another source, if the wiki was available then there is a table of rom upgrades that would almost certainly contain just what you would need.
Note that the wiki links are all official HTC roms, and would not need HardSPL.
@Zenity - You had given me some advice on getting the gprs working on my eclair install (Eclair problems/Android problems thread). Well, I ended up ditching Super Eclair for polymod 2.1d, and mobile data started working out of the box (which is odd, because it wasn't really working before, but who am I to question?!). Now my only issue is that if I activate wifi without first deactivating mobile data, then wifi gets caught in a loop and won't connect (i.e "Connecting, obtaining address, unsuccessful, connecting, obtaining address, unsuccessful" and on on on...). Then if I try to deactivate data or wifi, both get grayed out and say turning off, but never do. I'm fairly positive this is some conflict between data and wifi, because I've connected to the same AP without any issues while the data connection is off. Regardless, this is the most fully functional implementation that I've found. Still playing around, now that I have the time I'm diving a little further into tweaking and hacking through these releases.
Thanks for the help man. I've been on xda-devs since I first got this Att Tilt, mainly reading and learning, but I've noticed that a fair number of people don't take the time to further explicate and help people through problems and troubleshooting. You and kallt_kafee are both awesome when it comes to responding to less knowledgable users, and I for one really appreciate it. So Cheers, bro!
Thanks matcha, the main reason I still find polymod 2.1D my build of choice is that of them all, it just works, all the other builds do to, but I have found less issues from users on Polymod than the other builds, perhaps it's age has something to do with it, it has less 'new' features than the others, so less to go wrong, and perhaps also that it has grown with the whole android on kaiser project.
Anyway, appreciate the vote of confidence, really I'm just trying to give back a small measure of what Xda-Developers has given me
I do believe that this is my first post on XDA after about two-months of non-stop searching through forums, mods, roms, and themes. So here is to breaking the ice.
This is my first, smartphone, android OS ever so I am completely new to the whole experience to include: Flashing ROMS, nand backups, and updating things like services.jar.
I started out on Freshh rom and loved its performance increases and then got more bold and started experimenting with new kernels.
I now know how little I know about the whole thing after reading what flipz had to say about using TI Backup and adding themes over Roms.
I think that there has to be a checklist out there somewhere that people use to test a ROM that they have just flashed to ensure its functionality but have yet to be able to find one. If there is then could someone point me in the right direction because I must not know how to use the Search button.
However if there isn't then I'm hoping that this can be the thread to create a checklist after flashing ROMS, Kernels, Themes, etc. So that when you start adding programs and experiencing problems you can identify them quickly without hassling a Dev over something you did.
Thanks ahead of time.
DJZager said:
I do believe that this is my first post on XDA after about two-months of non-stop searching through forums, mods, roms, and themes. So here is to breaking the ice.
This is my first, smartphone, android OS ever so I am completely new to the whole experience to include: Flashing ROMS, nand backups, and updating things like services.jar.
I started out on Freshh rom and loved its performance increases and then got more bold and started experimenting with new kernels.
I now know how little I know about the whole thing after reading what flipz had to say about using TI Backup and adding themes over Roms.
I think that there has to be a checklist out there somewhere that people use to test a ROM that they have just flashed to ensure its functionality but have yet to be able to find one. If there is then could someone point me in the right direction because I must not know how to use the Search button.
However if there isn't then I'm hoping that this can be the thread to create a checklist after flashing ROMS, Kernels, Themes, etc. So that when you start adding programs and experiencing problems you can identify them quickly without hassling a Dev over something you did.
Thanks ahead of time.
Click to expand...
Click to collapse
How do you add a theme over a ROM? I've figured out how to root ,nandroid backup, wipe everything, install ROMs, change kernels, and still can't figure out how to install a simple theme!
I've found that most themes come in the form of [theme].zip and with that you just transfer it to the root of your phone's SD Card. Go into recovery, do a nand backup, then flash .zip from sdcard.
I tried that with a .zip file...maybe I downloaded the wrong file.
Hello!
My issue is that every so often (once every 20-30 minutes or so) my cell service just completely drops to absolute nothing, the drawer saying "NO SERVICE" at the bottom. Then about 20-30 seconds later, the connection is re-established and everything works fine again. Rinse and repeat. This has been going on for weeks now.
It seems very similar to an issue I noticed some other forum members had when d2att ROM builds were unified into d2lte. The fix was to Odin back to the stock 4.3 TW firmware and then start the custom ROM install process over again. However, I've already done this a few times and nothing has worked for me yet. CM, PA, Omni, Nameless, etc., I tried them all with no luck. The issue even happens on stock TW after I get through the Odin flashing process.
I recently upgraded to the newest UCUFNE4 bootloader/modem combo, thinking that a modem upgrade would do the trick. No dice. And now it sucks because I can't go back to 4.3 without bricking my phone (unless there's a 4.4 stock firmware for Odin floating around somewhere?).
My carrier is AT&T (well, it's actually an MVNO called StraightTalk), and I've contacted StraightTalk multiple times asking what might be going on. They seem to think it's a local cell tower malfunctioning. But I've waited and waited and am now assuming they simply don't know.
So I'm basically out of ideas. Help me, XDA. You're my only hope. Movie reference aside.
Is there perhaps a log I can provide or tool/app I can run that shows what I'm experiencing in more detail?
Thanks!
i have seen some custom rom OP instructions mention if having wifi issues to flash a custom kernel. dont know if that would help. BUT remember to double check compatibility and do a backup.
err on the side of kindness
Thanks for the reply.
The Wi-Fi is running great. It's only the cell radio that's causing problems.
Also, I'm usually running BMS kernel, but I've tried many variations and they all experience the same problem.
reflash ne4 modem? double check apn settings?
err on the side of kindness
Re-flashed NE4 modem.
APN settings look good, and I /do/ get LTE coverage. When the connection isn't cut out, of course.
Still no luck.
If its happening on every rom including every stock build youve tried its most likely hardware or the carrier. Ive heard of similar issues recently where we narrowed it down to those two as well. Im starting to think it may be straight talk.... No good way of knowing that im aware of though.
thank you mr huckleberry. my thimble of ideas was o-u-t. :thumbup:
err on the side of kindness
Thanks guys.
I might as well ask: is there any way to Odin back to the stock 4.4 firmware? I'm pretty sure only OTA is officially available, but has anyone perhaps made an unofficial .tar.md5? Seeing as how I can't go back to 4.3...
enewman17 has a stock 4.4.2(NE4) thread. maybe that?
http://forum.xda-developers.com/showthread.php?t=2788357
err on the side of kindness
I saw that thread/post earlier. But they look like recovery zips to me, not Odin .tar/.tar.md5.
my bad. yup, zips. will keep searching
err on the side of kindness
---------- Post added at 09:09 AM ---------- Previous post was at 08:55 AM ----------
what about... http://sammobile.com/firmwares
err on the side of kindness
I did find this post:
http://forum.xda-developers.com/showthread.php?p=53756950
But I'm not trusting an arbitrary post I found when I haven't seen anything similar from DocHoliday or anyone else working on the 4.4 release.
EDIT: The SamMobile site only has old firmwares available.
crap.:banghead:
err on the side of kindness
JJohnson1988 said:
I did find this post:
http://forum.xda-developers.com/showthread.php?p=53756950
But I'm not trusting an arbitrary post I found when I haven't seen anything similar from DocHoliday or anyone else working on the 4.4 release.
EDIT: The SamMobile site only has old firmwares available.
Click to expand...
Click to collapse
I must have missed that. No idea if itll work though. I did try to make an Odin package a while back but couldnt get it to work. Ive got a couple more ideas to try when ive got the time to focus on it, but i know that doesn't help now.
Its not for Odin, but i do have the firmware in a recovery flashable zip. Combined with enewman17's rom, it would almost accomplish the same thing. I think he has the stock recovery in that thread too which would be the last piece needed to get full stock.
Both threads are in the development section.
Well. Good news, guys. I finally solved the problem, mere hours after I became frustrated enough to start a post on XDA.
I ended up flashing to stock 4.4 via the recovery method, hoping to see a difference. Start using the phone for a few minutes, then the cell radio drops out as always. Wonderful.
So then I started thinking about what's common between all the ROM installs I've done. Was there something being left behind that wasn't being cleared properly? That's when I developed a crazy idea.
I remember reading about how there's a special area that's normally inaccessible where information like the phone's IMEI is stored. This is the /efs partition. Now, my IMEI was listed correctly in the phone information, but I decided to tinker around with some things as I was pretty desperate. I eventually got to the debug service menu by dialing *#27663368378# (I looked at a big list of codes online) and looked at what options I had.
The solution? Apparently an NV rebuild! I found this option in the service menu under UMTS >> COMMON >> NV REBUILD. I thought it was a long shot, but the longstanding problem I've had instantly fixed itself after a reboot!
So now my question is: HOW did the /efs partition become "corrupted" in the first place? And how was the phone actually able to make calls correctly and get working LTE data with the downside of service dropouts every so often? Shouldn't it... you know, either work or not work at all?
Anyways, thanks for the help guys. Looks like I don't need to send a nasty letter to StraightTalk after all (awww!).
glad to here you got it fixed. i wouldnt have a clue how it got corrupted, although docholiday77 might know (a WHOLE bunch smarter about this stuff than me), anyway :victory:
might want to hit doc's 'thank button'
err on the side of kindness
It may not have been the EFS partition that was the problem. Not much network related data is stored there. Much is on other partitions such as modemst1 and modemst2.
No one knows why flashing roms has the ability to mess up the NV Data. I suspect that when the system boots for the first time (after a rom flash, for example) it writes something to the NV Data and this is when things can get hosed. Thats just a theory though. Many have had problems with losing their IMEI because of this.
My theory on the IMEI is that after the new flash and boot something gets corrupted. These devices check for corruption during boot and will attempt to automatically restore from an on-device backup. The problem is the backup was never created, and it ends up restoring a null or blank value, causing the IMEI to become 0.
Something similar, but a little different may have happened here. Some data that is used by the carriers network to authenticate your device may have become corrupt or lost.
It wasnt an all or nothing type scenario because the device isnt constantly sending this info, probably only at certain times or intervals. But when it does, the network would not be able to authenticate your device and then block access, which would explain why it would happen every 20-30 minutes. Again, this is purely a theory.
The method you used to solve the problem has actually been around for a couple of years now, believe it or not! But its usually used to fix issues with GPS not being able to establish a lock. Whatever is used to authenticate for GPS, must be similar to what is used for the network in that it uses device specific info (such as the imei or s/n) to create a hash value that is then used in this process. When you chose NV Rebuild, it probably recreated these, thus fixing any issues due to the corruption of those values.
I hope all of that made sense! I am not positive that what i just wrote is 100% accurate, but it does make sense to me.
Now, i am guessing you never created the on-device backup i referred to, so this is how....super easy to do!
You do need to be running rooted stock.
Install and open Terminal Emulator and enter the following:
Code:
su
reboot nvbackup
Thats it! The device will reboot and create its backup. (Youll see blue text flash at the top, similar to when you boot recovery)
The backup is written across several partitions that are never touched by flashing, making it permanent. Flash all you want and itll remain intact unless you deliberately do something you shouldnt, or flash something not for your device.
As i stated before, every time the device boots up, it checks the NV Data for any corruption, and if detected it will auto restore from the backup. Youll never even notice anything was wrong!
Afaik, no one who has done this backup has ever lot their IMEI which is proof enough to me that it works!
SSL! Im glad you figured out a fix for your problem btw! Good work on that!
thank you mr huckleberry. never new how to backup this. guess i should read up on 'terminal emulator commands for newbs'
on it now.!:thumbup:
err on the side of kindness
You wont find the reboot nvbackup command. Its a Samsung specific one. But by all means learn more about the terminal if you can. It can help when writing scripts and troubleshooting all sorts of things!
samsung galaxy s3 i747 ?
err on the side of kindness