Intro
I don't mean this to be a thread for any specific ROM or problem, but rather a general guide that essentially eliminates all doubt of machine or user error (we all make mistakes). This is generally geared towards the issues users are experiencing when flashing an AOSP ROM, but can also apply to Sense, and even other devices. This covers from downloading a ROM forward, and also making sure that everything gets properly installed with no corners cut, so that everybody can be on the same page when a problem arises. I'm not trying to say anybody's way of doing things is wrong, but I've see a lot of people asking different questions that end up getting solved with the same few answers. This isn't a "how to flash" thread, but rather how to ensure you're getting your device in a clean, fresh state so that everybody can be on the same page when it comes to bugs, otherwise nobody is going to want to help you if you don't try to help yourself first.
I know this is on the longer side, so key points are underlined, with a TL;DR at the bottom
Downloading
Checksums or hashes are a great way to make sure that the *.zip or any other file you're downloading is not only the right one, but that it hasn't been corrupted or tampered in transfer (uploads or downloads). You'll probably need to install something to work with chescksums- personally I like the open-source HashCheck for Windows. It adds a "Checksums" tab to the right-click > Properties dialog that automatically calculates MD5 (most common) and SHA-1 (more advanced) hashes. I encourage anyone posting a file to also post the MD5 with it, for everybody's sake, since it only takes a few extra seconds to eliminate all doubt of a bad upload or download. HashCheck even gives an option to create a *.MD5 file, just like the ones you might get from goo.im. If you're on Linux, Android, or presumably Mac you can check a file's md5 by opening terminal and simply typing "md5sum <filename>" without the quotes. If a file is posted without an MD5, you can download it twice and check it against itself, but just keep in mind you're going to be hitting somebody's server twice as hard, so only do it if necessary. Now that you're sure you have the right files...
Wiping/Flashing
Most people know dirty flashing is at your own risk, and if you have a problem, the first thing anybody's going to tell you is to do a clean flash. No really, just clean flash- that's what backups are for, but that's a whole different topic. Unfortunately, most people consider a clean flash to be just a factory reset, but that only wipes dalvik, cache, and data (except your sdcard), while leaving the system partition intact. To do a proper clean flash you want to go into advanced and make sure that system gets wiped in addition to dalvik, cache, and data. I can't say exactly what (sorry), but there's lots of miscellaneous things that can persist between flashes, especially when you're going to a different ROM. For us DNA owners, there's still a lot of activity in our CM device tree, meaning that even on the same ROM, some of our device files may change between versions which will necessitate a wipe of system. Maybe it's just me, but it seems things go out of line more often on 4.3 so I just always wipe system now.
If you're here, you probably know how to flash a ROM, but always double check the OP or first few posts and see what gapps/settings/etc are recommended. I'm also going to remind you that it takes just a few extra seconds to create a *.md5 file with HashCheck that you can push to your device along with the *.zip and TWRP (probably CWM too) will check the file against it's MD5 before flashing it. After using the Setup Wizard to log in to your Google account, make sure that you uncheck the box to restore settings and data to your phone, otherwise those can cause problems. Now you can be sure that whatever is on your device is clean as can be and as the developer intended, otherwise you're probably not going to get much help.
Narrowing down the problem
Now that you've got a brand spanking new and clean ROM is the best time to try and narrow down a problem, but before you post anything, try the golden rule of IT- "Have you tried rebooting it yet?" Also, you can try booting to recovery to clear just dalvik and cache and/or repair permissions. This is the first time you should consider making a post about your problem, but please, please, please don't make a post that just says something like "Settings FCs." Posts like that don't tell anybody anything- the best thing you can do is pull a log (more on that in a second), and create a post in the appropriate thread which you can determine as follows: Start by seeing if the problem occurs with nothing installed besides the ROM and recommended gapps- do not restore any backups, install any apps, or flash any kernels, even if the OP recommends it. If you're having problems with Settings or any Google app, there's likely a conflict with the gapps package that should go away if you reflash only the ROM, otherwise it's a bug in the ROM itself. Either way, if you can reproduce a problem at this point you should post in the ROM thread. If you want to flash a custom kernel, only do so after you've verified the problem isn't with the ROM or gapps. Flash only the kernel, and if there's any problems after that, post them in thread you got the kernel from, not the ROM thread.
If you're having a problem with an app, once you've completed the above steps, install only that app without restoring any data. If you can't replicate the problem, there's likely an incompatibility any corresponding data you may have restored, and sorry, but there's not really anything you can do about that. If the problem occurs with a freshly installed app, first check the Play Store to see if other users are experiencing the same problem- there may just be something wrong with the app. If it only seems to be you having this problem with a clean install, the ROM thread is the best place to post, although keep in mind other users may not be familiar with app.
Pulling and posting logs
Even now, nobody is obligated to help you (you flashed that ROM at your own risk, remember?), but once you're at this point, you'll have a better chance at getting help. Try to include as much information as possible like what else you were doing, what screen you were on, what button you tried to press, etc. and if you can, try to see if you can replicate it. Like I mentioned above, posting a log is the best way to get help, and they're really easy to get. Not everybody is going to understand every line, but if you know what you're looking for, occasionally the log can tell the developer exactly what the problem is, and bam- easy fix.
First make sure USB Debugging is enabled in Developer Options (if you don't see Developer Options, go into About Phone and tap on the Build Number line 7 times), and make sure that Root Access is set to both Apps and ADB. Now as far as gathering these logs, SysLog is by far one of the easiest ways- download it, open it, and press "Take Log." It pop up a toast message saying that your logs are in /sdcard/SysLog/<DATE_TIME>.zip and it'll even give you the option to share it via email, Dropbox, or anything else you might use. Post that and you'll have even better chances of getting help. For simplicity, I'm not going to details on manually pulling logs, however if you're stuck in a bootloop or something like that and can't run the app, use "adb pull /proc/last_kmsg" and post a link to that file.
TL;DR
Sh*t happens, learn to deal with it or go back to stock
Verify your download with an MD5 Checksum
Wipe system in addition to factory reset (dalvik, cache, & data)
Flash ROM and gapps without installing anything else or restoring any data
Pull a log, it's really easy
Now is the best time to make a post about your problem
Radio/Reception Problems on the DNA?
First things first- Double check your settings in Settings > More > Mobile networks. They should be as follows:
Data Enabled: Yes
Data Roaming: No (unless you're actually roaming)
National Data Roaming: Yes (otherwise you'll probably lose data; this won't get you any roaming fees)
Network Mode (Verizon): LTE/CDMA/EvDO (or Global, which is everything, I've never noticed any difference between the two)
Network Mode (GSM): GSM/WCDMA preferred (depending on the ROM, you may also need to flash the GSM patch courtesy of Flyhalf205 from the 2nd post in the original CM10.1 thread.)
System Select/CDMA Roaming: Automatic
CDMA Subscription: RUIM/SIM
GSM users may also need to manually enter APN settings for your carrier to get things like MMS functioning properly. I'm not going to compile a worldwide list, but if Google fails you, your carrier should have support documentation with these settings. Recently, I noticed this file in the android source lists tons of APNs, so try finding your carrier in there too.
Why do I have 0-1 bars? I got a lot more on Sense
Don't be alarmed if your reception looks low/non-existent. Sense "pads" the signal bar to get it to show bars more "accurately," but AOSP does not, so expect a drop in bars. To get an accurate assessment, you want to be looking at your actual signal in dB before trying to diagnose anything by going to Settings > Interface > Status Bar and changing Signal Status Style to Text, and your signal bars will be replaced with a negative number, therefore a value closer to zero indicates a stronger signal. If you don't like negative numbers, another way of thinking about this is as if the phone was telling you how far you are away from the nearest tower. What would normally be 5 bars on Sense equates to -70dB, and 1 bar equates to -115, but these are approximate values and depending on your location and environment, you might bee numbers outside this range.
I'm still having problems
Unfortunately, our phone is known to have problems with reading the SIM card. Some say it's purely software, some say its purely hardware, but I believe it can be either. I'd first suggest giving your SIM card a cleaning by popping it out and gently rubbing the contacts with a clean rubber eraser, another more risky option is a just drop of isopropyl alcohol on a cotton swab. If you have compressed air, you can give that a small blast into the SIM slot from a few inches away. If the phone is still having issues with reading the SIM after that, it might need to be replaced.
Another possibility is issues with the radio firmware. You can try updating the firmware by following the instructions in this post. Personally, I recommend the most recent version, 2.06.605.1. Some users, myself included, have reported that sometimes a full RUU back to 100% stock is necessary to restore proper radio function. Instructions for that can be found here, but be aware that this can be a lengthy, tedious process. You'll end up having to re-unlock and root your phone before you'll be able to flash anything else again, so I only recommend this as a last resort, but is nonetheless something to bear in mind.
Stickie this?
Sent from my HTC6435LVW using Tapatalk 4
I'm going to stick it for now, it's actually good basic info. But I am moving it to the Q&A forum.
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
pyroguysf said:
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
Click to expand...
Click to collapse
Yeah that makes sense, and I was hoping this would also cut down on unnecessary thread starts.
I think what I'll do is have this in both development forums as a sticky, hopefully this will help out some of the chefs.
If you edit one thread, be sure to edit the clone in the other forum.
I am going to let you clean this up as much as possible over the weekend, then maybe move it to the dev threads Monday as a polished product, see if you can get as much info as possible about GSM to include about the signal issues etc.
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
orangekid said:
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
Click to expand...
Click to collapse
I've noticed this, but I made this in hopes of giving people a place to link back to rather than having to waste time typing out the same things over and over, which is why I also put the link in my sig.
orangekid said:
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
Click to expand...
Click to collapse
Good ideas. I'll try to add a section for apps when I get a chance. I tried to briefly touch on the kernel situation by saying to read the OP for recommended settings, but I'll definitely expand on that.
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
pyroguysf said:
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
Click to expand...
Click to collapse
Sounds good.
Moved to dev forum.
If you want to go ahead and create the same thread and copy / paste the first 2 posts, I can sticky it.
Related
Hi all,
I am new to android. First time using it and really know nothing about it.
Bought the G tab at woot. I am knowledgeable with computers, so I hope that helps. Over 50, so need your help here.
I have spent a decent amount of time looking through these forums and there is so much information here, it is hard to discerne what is relevant for me.
I did the OTA update. I do not have an sd card, so all will be through the usb to my home computer.
I have played with the gtab a bit, but I figure, before I go and do a bunch of setup for the family and download apps that if I am going to root it, I may as well do it now. Those of you with experience using it don't like viewsonics version, so I assume that these ROM's must be so much better.
From this thread http://forum.xda-developers.com/showthread.php?t=842004
it reads that if I have stock gtab, I can simply install TnTLite 4.4 without clockworkmod. I assume then that without colckworkmod, I can't clear the cache or datafiles. Do I really need nvfLASH? I read it and it sounds a bit confusing.
I read that you should repartition the gtab. I looked and can't find out how to do this. Is this before or after you run the mod?
For the market fix, http://forum.xda-developers.com/showthread.php?t=845175
I follow the link to download the zip file. When I download apps from the computer, where on the gtab do they go to unzip them?
What does sideload mean? What do you mean when you say make sure that market is working with your google id? do i need a gmail account?
On a side note, the gtab will not load up my yahoo mail account? hmmm, is that correct? My wife has an old aol account that she uses and she said she can't respond to emails, that is true also?
Thanks in advance,
Kozmokrmr
Lots of questions... let's see what we can do here...
Yes, You can setup TnTLite 4.4 without ClockworkMod. However, CWM is included in the install as part of the 3588 Recovery Pack. You can actually switch it in and out as needed for the purposes of clearing caches and wiping data.
Repartitioning is one of the advanced functions of ClockworkMod. You will not likely find it necessary unless you're doing lots of modding (or are particularly anal about procedure, like I am...).
It doesn't really matter where you download or unzip files to as long as you know where they are. I leave them in the default download folder or create a folder for the particular project on one of the sdcards. Sideloading consists of downloading an app's .apk file to the tablet then installing it without using the market. Most file managers (including the one included on the gtab) do this with a click or two.
Yes you will need a gmail account to make the market work. When you start it the first time it will ask for your gmail credentials to log in.
There is a Yahoo mail (and IM) client/app. Not sure about AOL. But either can be accessed through the web browser.
All that being said... if you are planning on using the "Family" accounts setup that comes stock on the G Tablet you'll want to try that before loading any custom ROM. They all replace the contacts app which is required for that to work. I'm not sure if any of the custom ROM's supports any kind of multi user setup.
Thank you K J Rad
To enter clockworkmod, then just use the power and volume up to access clockworkmod from 3588 update? Then do the data and cache clearing? Is clockworkmod, just a tool to do a few system functions?
Ok, then I won't worry about repartitioning.
Hmm, alright, I guess I'll just give the sideloading a go and see what happens.
About NVFlash, should I worry about it or is it only for the guys who switch out roms and play around with it? I figure, once I install a mod, other than maybe updating the rom, I won't be yanking around with it like this anymore.
Ok, then we'll get a few gmail accounts. Thanks.
The internet on the gtab wouldn't access my yahoo. Possibly I need to upgrade yahoo to the paid version to get the pop account.
The AOL account could be read, but she couldn't reply to any emails. Possibly the same problem there.
No big deal about the family accounts, we don't need them. Its not an issue.
The people here I read that have issues (not booting up, stuck in a loop, etc.) have what? done a step wrong, played around a bit too much or just one of those odd software flukes that catches some guys?
So there really is a BIG difference in the stock rom and the modded roms's, yes?
Thanks again.
Power and Volume Up enter "Recovery Mode." If ClockworkMod is installed then that is what you will get. Otherwise you'll get the stock recovery. 3588 does not install CWM. There is a very good thread "Stickied" in the development section about installing Clockwork, ROMs, etc. Once you've got that installed the instructions for installing TnTLite 4.4 and switching between the two types of recovery are in the stickied TnTLite thread. I usually do a data wipe before and after installing a ROM (it works for me... YMMV).
Knowing how to nvflash could be the difference between nirvana and complete disgust. It may never come up but if it does then you will be thrilled that you know how.
Once you have the market installed and working download a better browser. I use Dolphin HD and it works with my Yahoo account just fine (after you tinker with it's settings a bit...). Probably work fine for AOL also. If not, try Opera Mobile.
Any number of things can cause the issues you'll see posted about here. I've suffered magic number mismatch, boot loop, FC's... the whole gamut. If you get comfortable with the tools then you'll be able to recover from anything. Good practices will also lead to greater success. For example, when I'm flashing to a new ROM I do the following:
1) Cache and Data wipe.
2) nvflash to Factory install.
3) Update to 1.1-3588 build.
4) Data wipe (probably not necessary but wth...)
5) Proceed with update.
For experimental builds I modify that to include repartitioning.
Following this procedure has reduced my occurances of unexpected issues to near zero (I don't always remember to do every step...).
Yes... the custom ROMs are "Better" but better is subjective. I like TwoTapsX for its speed and stability though it does suffer from a few video artifacts from time to time. TnTLite is a good solid daily driver for the average user. VEGAn is popular with a lot of power users. Each has its tradeoffs and even the stock ROM has some advantages (easy to use custom interface, decent basic set of integrated apps, settings optimized to reduce confusing options).
Welcome and enjoy.
So, everything was fine as I shut down last night after reading a few pages from a book. Tried to power up this evening and it just won't cooperate. It won't turn on unless I hold the power button down for nine seconds. It starts up "with tap n tap" screen, then the n logo shows, then the "with tap n tap" flashes and returns to black screen then shows the "with tap n tap" for a total of eight times then stays black. No rooting, totally stock, used very little, few apps, added some reader stuff, tried a barcode thing to no avail - nothing more. Please advise. Take pity on someone like your mother! Any ideas on how to fix this? Should I contact Viewsonic or Woot? (yes, it's fully charged - first thing I tried). I'm so disappointed : (
Thank you
I've seen this happen a few times with both stock and modded devices. I think it's caused by corruption in data files that are used by some of the system firmware but I'm not 100% certain of that. A data wipe could very well get you going again. Without being able to boot all the way you're options for doing that are somewhat limited. One would be to install and use ClockworkMod, a very minor and extremely common modification to the firmware. The other option that I have used successfully is a script I've written that will delete those system prefence files and clear the machines cache without modifying your firmware. Neither is terribly complicated to implement.
All that being said... it is really up to you as to how comfortable you would feel performing those options. I can say that you will find plenty of people here that will be willing to stay right with you until it's fixed and we have a very high success rate when it comes to recovering from this kind of issue. On the other hand, Woot has been very responsive to customers with problems so it's really your call.
This thread: http://forum.xda-developers.com/showthread.php?t=865245 has instructions for installing ClockworkMod. It has a lot of other information in it also but the important part would be installing CWM. It also has download links to the files. Once it is installed it is a fairly simple matter of booting the machine up while holding down the volume up key and you'll be presented with a menu of options that will include wiping data. Selecting that will clear out any apps you've downloaded and associated data along with the system data. Once done you simply reboot the machine from another menu option and you should be off and running.
My script is run very much like installing ClockworkMod but will simply do the deletion without any user intervention. When done it reboots automatically and in two or three minutes you should be back to the initial setup screen for the tablet.
All of this probably sounds a lot more difficult than it really is but I think if you take a look at that thread I listed above and do a little searching on terms like "ClockworkMod Data Wipe" you'll find there are lots of folks who have done this and plenty of help if you need it.
KJ and LynnyW,
Since he can't boot, he will either have to make a microSD with a CWM update.zip and recovery folder (with command file edited to point to SDCARD2 instead of SDCARD) and boot that into recovery with power/volume + .
Or, he will have to NVFlash the CWM by itself.
http://forum.xda-developers.com/showthread.php?t=1020747
http://forum.xda-developers.com/showthread.php?t=1030042
The two links above have most of the info.
If he can get CWM up by one method or the other, need to go to Advanced Menu and tell it to Partition (2048 and 0), Fix Permissions and Wipe Dalvik Cache -- and then return to Main Menu and Wipe Cache and Wipe/Reset Factory Data. Then reboot.
If the tablet comes up fine we're good to go. Otherwise may need to talk about a
stock rom flash.
Hope this helps.
Rev
I am running a stock system. Amazon market and a couple bird games are all that's really on it as I use it mostly to browse the web with. No flash no email, it's stock. So far I've limped through how to recover from the acore.process problem, then ended up learning how to use nvflash after what this user described happened twice so far. I am debating updating to a Dev rom if they are more stable as otherwise this is just a fragile toy that I can't take out of the house on trips.
wetzk said:
I am debating updating to a Dev rom if they are more stable as otherwise this is just a fragile toy that I can't take out of the house on trips.
Click to expand...
Click to collapse
Update. So much better it's unreal. Go with something stable like Caulkin, Vegantab, or TnT lite. Not only will you get the real Market, you'll be much happier all around. It can be much more than a fragile little toy.
butchconner said:
KJ and LynnyW,
Since he can boot, he will either have to make a microSD with a CWM update.zip and recovery folder (with command file edited to point to SDCARD2 instead of SDCARD) and boot that into recovery with power/volume + .
Or, he will have to NVFlash the CWM by itself.
http://forum.xda-developers.com/showthread.php?t=1020747
http://forum.xda-developers.com/showthread.php?t=1030042
The two links above have most of the info.
If he can get CWM up by one method or the other, need to go to Advanced Menu and tell it to Partition (2048 and 0), Fix Permissions and Wipe Dalvik Cache -- and then return to Main Menu and Wipe Cache and Wipe/Reset Factory Data. Then reboot.
If the tablet comes up fine we're good to go. Otherwise may need to talk about a
stock rom flash.
Hope this helps.
Rev
Click to expand...
Click to collapse
I think the decision needs to be made as to whether LynnyW actually wants to start mucking about before we go suggesting modifying the recovery and repartitioning the tablet. In this case I think all that's necessary is a data wipe and that can be done without starting down a path that LynnyW may not care to follow. I certainly wouldn't recommend anything as extreme as repartitioning when the question asked is whether or not a call should be made to the manufacturer and vendor.
KJ,
Take him where you want to go -- but if he can't boot up he's going to have to
get inside somehow. That's why I said I thought he would have to install CWM.
If you know some way to wipe or reset without CWM, go for it.
Rev
P. S. -- And I assume anyone that posts here wants to fix it unless that is not
possible -- and then they want us to tell them to go to VS or Woot or
whatever.
I meant no offense, Rev. She asked whether she should call woot or Viewsonic. I was just pointing that out. Not everyone is ready to jump into modding when they have the option of warranty return/replacement.
waiting for Viewsonic call
Thanks folks. I don't want to go mucking about until necessary. I guess I was hoping for an easy fix/reset. I prefer not to send the tab for repair unless replacement is necessary. Not yet willing to put my toe in water of this vast new world of acronyms I know nothing about. My brother's voice echos in my head "you know just enough to be dangerous" (re windows). I don't want to void the warranty. I called Viewsonic and had to leave my telephone number for a return call. I'm hoping they can e-mail a file which I can copy to a microSD, pop in, turn on, and resume - until I have the nerve to install something more stable. I will let you know what Viewsonic has to say. They no longer operate at the toll free number listed on the website. Directed to another number where they answer the phone "can I help you?". I wonder what service they are using for tech support.
Lynny
I have just such a file that might get you going. Posted it this morning here:
http://forum.xda-developers.com/showthread.php?t=1030915
Feel free to look that over and let me know if you have any questions. The main caveat is that it will delete any user apps that have been installed. That may include factory installed apps that are stored in the user app area. If that is a problem I can modify the script to preserve them but then we might not be clearing the problem file.
Viewsonic should hire you!
Well, I received a call from Viewsonic tech support. The moment I finished explaining what happens on the screen, the tech said "I never heard of this. Ship it back." Whoa, no attempt to troubleshoot? I asked was there not a bootable file I could be e-mailed? After rephrasing and getting nowhere, I was not happy to be told to send this to LA for an unknown amount of time at my expense. I was told I could call back later when the manager was back from lunch. This is a far cry from the claim on the Viewsonic website:
"Got a question? We have the answers right here: documentation, downloads, tech support, software updates, product warranty and registration. Get the assistance you need, when you need it – right now. Find out how we stand behind our product, all the way."
The lack of speculation regarding what the problem might be makes me feel that Viewsonic farmed this out to a fly-by-night call center and the folks there were told to have callers just send in the hardware.
Sorry, I had to rant.
KJ, Viewsonic should hire you and your xda brethren. The files to clear the data worked. Yes, it did wipe out factory and user apps, but it got the tab working in five minutes. It also gave me a little courage. I will, after all, start reading about modifying this thing. I don't want to set it all up only to have it faint on me again.
If you have any recommendations for the least-likely-to-brick-it route, please advise. I have read a number of threads but there is so much information, and although there are numerous step-by-step instructions, I have no idea what the different roms do. I don't know where to start reading and I don't want to become an annoyance here. I will do my homework before I ask too many newbie questions.
THANK YOU!
Lynny
We understand the need to rant from time to time. No problem ;-)
Glad it got you going. I do want to recommend that you do a factory reset from the system settings also just to make absolutely sure everything was cleaned properly. It's under "Security" in the System Settings.
As for modding... read, read read. Start with the "Stickied" items in the General and Developer sections. You'll find references to basic procedures and cautions but always make sure to follow the developers instructions attached to the specific ROM you choose. As for the "Least likely to brick it..." I may not be the best person to ask since I routinely run experimental ROMs. I do like the TnTLite path for its stability, reasonable speed and close association to the stock ROM. Read as much of the threads attached to each one and ask questions if you need to. That's why we're here.
ROOTING + UNROOTING INFORMATION + COMMON QUESTIONS + PROBLEMS w/ LINKS
DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR ANY DAMAGE THAT OCCURS TO YOUR PHONE. THIS IS A COLLECTION OF INFORMATION I FOUND TO BE USEFUL. I ONLY ORGANIZED IT HERE TO MAKE IT EASIER FOR PEOPLE TO FIND.
Don't forget to thank people who made the ROMs, Root Methods, etc. They put in a lot of work and take a lot of time helping people. All it takes is a click of a button. One for me too! It's a lot of work trying to keep everything updated. =P
This will and always will be a work in progress. If you feel something should be added, clarified, or corrected feel free to PM me. I'm not perfect and I can't read everything so any and all help is appreciated. (Yes of course I will credit you. Just no plagiarism!)
-----------------------------------------------------------------------------
Preface:
I made this guide to be a collection of information for the latest rooting methods as well as common questions and problems that arise from rooting/flashing/etc. Please read the entire guide if you are new to rooting. Also the common questions and problems are found in posts 2 and 3 of this thread. I hope you find this to be helpful. Happy and safe rooting.
----------------------------------------------------------------------------------------------------
Latest News:
-CM10 PREVIEW BUILDS READY FOR AT&T, TMOBILE, & SPRINT! Go to the Original Development forum for your carrier.
-You can now reset your flash counter! Check out "Triangle Away 1.70" in the Play Store. http://forum.xda-developers.com/showthread.php?t=1494114 HUGE THANKS TO CHAINFIRE!
-VERIZON GALAXY S3 ROOTED!!!!! http://forum.xda-developers.com/showthread.php?t=1756885
-Clear your Google Wallet data before you flash a ROM! Doing it in Titanium Backup does not work. Do so by opening Google Wallet, Menu > Settings > Reset Google Wallet.
-If you flashed an international ROM or root method and you were soft bricked, here is how to fix it: http://forum.xda-developers.com/showthread.php?t=1727443
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting Information
What is rooting and why should/shouldn't I do it?
Rooting is a way of gaining access to the root directory of your phone enabling you to change every aspect of your phones software that the manufacturer has locked. This enables you to do many things with your device that the manufacturer did not intend. Here are some reasons why people root and why people don't.
Reasons to root:
Get the latest versions of Android on your phone before anyone else.
Try faster and more optimized versions of your phone's software.
Overclocking and underclocking your phone.
Longer battery life.
Theme your phone a lot more.
FREE Wireless Tethering.
Remove unwanted Sprint software.
Reasons to NOT Root:
Not comfortable with troubleshooting your phone and phone problems.
Do not have the time to spend going through countless forums to find solutions to problems.
Possibility to break your phone permanently causing you to go back to Sprint (IF YOU HAVE INSURANCE) to get another one or buy another if you don't have insurance.
VOIDS YOUR WARRANTY. (Can be undone)
Very time consuming and addicting.
Do not know what a "driver" is for a computer.
Have no knowledge of DOS.
So how do I root?
Warnings:
-Don't use any method just because the guide says "ROOT METHOD". Make sure its the latest root method used for your situation. Even this guide will get outdated one day (I'll try my best to keep it up to date).
-Rooting will cause all your information to be lost if you did not properly back them up. You will lose anything saved on the phone, such as contacts (not synced to Google) and applications and settings. Anything on your SD card will still be there such as music and pictures and video.
Basic terminology:
If you are new to Android or not comfortable yet, learn the terminology first! Found a great link to almost all the terms you will run into. If you don't understand something, ask! Its better than turning your phone into a paperweight!
http://forum.xda-developers.com/showthread.php?t=1728824
The SAMSUNG GALAXY S3 QCOM TOOLKITis currently used to ROOT your device. Please read that thread carefully and follow all directions to get it started. Also before you flash ANYTHING, go to your Google Wallet app and clear data in Android. Clearing in Titanium Backup or any other app will not work. You must clear the data before flashing anything or it will not work! You have been warned!
Root Methods per Carrier (Windows)
AT&T:
http://forum.xda-developers.com/showthread.php?t=1746665
http://forum.xda-developers.com/showthread.php?t=1739426 - Does not trip flash counter
Sprint:
http://forum.xda-developers.com/showthread.php?t=1746680
http://forum.xda-developers.com/showthread.php?t=1774722 - Does not trip flash counter
T-Mobile
http://forum.xda-developers.com/showthread.php?t=1746682
http://forum.xda-developers.com/showthread.php?t=1771687 - Does not trip flash counter
Verizon:
GUIDE TO ROOTING: http://forum.xda-developers.com/showthread.php?t=1762709 (Thanks droidstyle)
This might be complicated for some users. Please follow all directions CAREFULLY!
http://forum.xda-developers.com/showthread.php?t=1756885
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What do these methods do?
They root your device and give you the option of installing a custom recovery which is used to flash custom software on your phone! If that was in another language, go up and read through the link on Basic Terminology.
How do I know if I am rooted?
You followed the above instructions and have Superuser in your App Drawer. You can also go to the Play Store and download a root checker.
I am rooted now. What can I do?
FIRST MAKE A NANDROID BACKUP! ALWAYS DO THIS BEFORE YOU FLASH SOMETHING. THESE ARE BIG FILES SO TRANSFER THEM TO YOUR COMPUTER TO SAVE SPACE ON YOUR SD!
A nandroid backup basically takes a snapshot of your phone which you can restore. While it will fix most problems, it is not a cure all. It will fix most if not all ROM flashing blunders.
How do I make a Nandroid Backup?
#1 - Go into recovery by powering off your phone first, then holding [Volume Up], [Home Key], and [Power Key] together till you see the Samsung logo flash. Use [Volume Up or Down] to navigate the menus and [Power Key] to select.
#2 - Go to "backup and restore" and hit the [Power Key]
#3 - If you have an SD card, I recommend placing the backup there as it is quite large.
#3a - If you have an SD card, select "backup"
#3b - If you do not have an SD card or don't want to save to your SD card, select "backup to internal sdcard"
#4 - Wait for a very long time till it finishes. Once it does it will bring you back to the menus.
#5 Select "+++++Go back+++++"
#6 Do your business in recovery or "reboot system now"
OK. I made my Nandroid Backup. What can I do now?
You can now flash custom ROMs, kernels, radios, themes, etc. Go to your specific carrier's Development section on the forums. You will find ROMs, radios, kernels, etc there.
For themes and Apps, go to the Themes and Apps section of the forum.
WARNING: For the time being, you MUST flash the ROMs found in your respective carrier's forums. DO NOT FLASH A ROM FOR ANOTHER CARRIERS OR THE INTERNATIONAL VERSIONS GALAXY S3!
AT&T
http://forum.xda-developers.com/forumdisplay.php?f=1633
Sprint
http://forum.xda-developers.com/forumdisplay.php?f=1639
T-Mobile
http://forum.xda-developers.com/forumdisplay.php?f=1645
Verizon
http://forum.xda-developers.com/forumdisplay.php?f=1672
Themes & Apps
http://forum.xda-developers.com/forumdisplay.php?f=1671
---------------------------------------------------------------------------------
How do I flash a ROM/Kernel/Theme/etc
#-1 - READ THE THREAD FIRST FOR THE INSTALL INSTRUCTIONS! They will usually be a summarized version of this!
#0 - MAKE SURE YOU HAVE AT LEAST 30% BATTERY! IF YOUR PHONE DIES, IT WILL STAY DEAD (most likely). YOU CAN NOT CHARGE WHILE DOING THIS!
#1 - Download the ROM of your choosing from your carrier's forums. It will be in a .zip file format. DO NOT UNZIP IT!
#2 - Save this file to your SD card or internal storage.
#3 - Power off your device.
#4 - Go into recovery by powering off your phone first, then holding [Volume Up], [Home Key], and [Power Key] together till you see the Samsung logo flash. Use [Volume Up or Down] to navigate the menus and [Power Key] to select.
#5 - IF YOU HAVE NOT MADE A NANDROID BACKUP, SEE ABOVE! IF YOU HAVE NOT RESET GOOGLE WALLET AND ARE ON SPRINT! STOP AND GO BACK AND RESET IT!
#6 - Use the volume keys to select "wipe data/factory reset" and hit the power key. Select "Yes -- delete all user data" and hit the power key.
#7 - In the main menu, select "advanced" and then select "Wipe Dalvik Cache" and then select yes.
#8 - Go back to the main menu and use the volume keys to select "install zip from sdcard" and hit the power key.
#9 - What you select next will be based on where you saved it.
#9a - If you saved in the SD card, select "choose zip from sdcard"
#9b - If you saved in the internal storage, select "choose zip from internal sdcard"
#10 - Use the volume keys to select the .zip file you downloaded and hit the power key.
#11 - WAIT FOR IT TO FINISH!
#12 - Congrats! You just performed your first flash. Go back to the main menu and reboot your device.
#13 - Enjoy.
How do I return to stock (unroot)?
AT&T
http://forum.xda-developers.com/showthread.php?t=1737848
Sprint
http://forum.xda-developers.com/showthread.php?t=1737859
T-Mobile
http://forum.xda-developers.com/showthread.php?t=1737855
Verizon
GUIDE TO UNROOTING: http://forum.xda-developers.com/showthread.php?t=1762709 (Thanks droidstyle)
http://forum.xda-developers.com/showthread.php?t=1755386
How do I backup my apps?
Use MyBackup. You can use this to backup and restore your apps without the need for rooting. (Thanks teh roxxorz)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Appbrain is good if you are using market only apps. However app data won't be saved.
Titanium Backup is also good if you are rooted.
Credits:
teh roxxorz, noobnl, cypher_zero, qbking77, appdroid, & droidstyle
Common Questions
I am getting an Over the Air (OTA) update from Sprint. Should I accept it if I am rooted?
IF YOU ARE ROOTED, DO NOT ACCEPT THIS OTA.
This means that your phone's software is not up to date and it is telling you to update. You must download a ROOTED version of the update and manually flash it. Accepting this will cause you to lose root and worst case, brick your phone. SO DON'T DO IT! lol
I rooted using ABC's method. Do I need to root again using XYZ's?
No. Once you are rooted, you are good to go.
I turned my phone into a paperweight/bricked it/"borked" it/its just not working no matter what I do. What can I do?:
No information yet!
If you have Sprint's Total Equipment Protection Program, you are in luck. They changed their policy on October 23rd. Here are the details of what it covers.
http://www.phonenews.com/sprint-tepsr-changes-next-week-13303/
If the phone is beyond repair, you will have to go through Asurion and pay the $100 deductible. TEP does not cover rooted phones. You have to go through Asurion.
If you don't have TEP, everything except water/fire damage and lost phone replacements cost $35 per incident as long as the phone is not beyond repair. If it is beyond repair, you will have to buy a new phone.
What is PRL?
PRL stands for Preferred Roaming List. Its a list of roaming towers in your area. Its best to keep this updated in crappy coverage areas.
What is PRI?
http://forum.xda-developers.com/showthread.php?t=751935&page=7 <- Debate on what it stands for. (REALLY?!)
In actuality it is called "Product Release Instructions" and is essentially a list of settings for the radio. It's the PRI which uses the PRL to enable data roaming by connecting it to towers/cell sites listed in the PRL and for other things such as to allow calls to interrupt an active data session (ring-through).
How do I update my PRL/PRI?
Go to Menu > Settings > System Updates > Update PRL + Update Profile.
I see "deodex" and "odex" ROMs. What are those?
Basically if you want to theme your ROM you want to use deodexed ROMs. Odexed ROM's are made to be streamlined. There is a performance difference. Deodexed ROM's will take longer to boot up because everything or almost everything is unpacked. Odexed ROM's will boot faster and be more responsive.
http://lmgtfy.com/?q=What+is+deodex
Google is your friend =P
FREE Wireless Tether:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=Evo
***Some builds don't work with certain ROM's. Trial and error or searching within your ROM's thread will let you know which build numbers will work for you. Also note if you enable WIFI Encryption, the password is CASE SENSITIVE! Make sure you know that as you are typing the password in due to certain keyboards auto capitalizing. ***
Launchers: (Will review once I get my phone)
ADW
LauncherPro
Apex Launcher
Nova Launcher
Widgets (Will review and add more once I get my phone)
Beautiful Widgets - Sense like clocks and weather. Make sure to download the animation package if you want animated weather.
OneSeven - A text based date widget
Tajm - A text based clock
----------------------------------------------------------------------------------------------------
Battery - Common Questions and Problems
What is the best ROM + Kernel combination for battery life?
There is no right answer for this. Battery life is affected by so many factors, the only thing you can do is trial and error. Here are most of the factors that can affect battery life:
-Phone Settings (Haptic feedback, screen on duration, auto sync, radios, etc)
-ROMs
-Kernels
-Overclocking + underclocking
-Apps
-Signal strength
-Roaming
-Battery type
-Battery stats
-Calibrating the battery
-PRI
-PRL
-The water you drank the other day
-The **** you took just before
So how do I improve battery life?
No information yet.
Common Problems:
I created a bug thread check that first!
http://forum.xda-developers.com/showthread.php?t=1722363
Standard Troubleshooting For Many Flashing Problems:
-Try Rebooting. Most problem will be solved this way.
-Was it fine before your Nandroid Backup? If so, restore your backup.
-If you flashed something and are having issues, did you wipe your data/cache/dalvik? If not then do it and reflash.
-If you are still getting problems, the file is most likely corrupt or outdated. Try redownloading and making sure the file is updated for your ROM + Version #
-If the file is updated and NOT corrupt, SEARCH FIRST IN THE FORUMS OR GOOGLE! You will be surprised on the answers you can find in 15 seconds of searching.
-Can't find any solution or workaround? Then make a post in that thread with details of your problems, as well as ROM, error messages, etc.
I am getting random Force Closes (FCs) after flashing ****.
Did you wipe your data/cache/dalvik? Also go to Mounts and format /system. If not do a Nandroid Restore to the backup you should have done before flashing and then wipe data/cache/dalvik and then reflash. See if you still get a FC. If you do, there might be a problem with whatever it is you flashed with the ROM you are using. Check on the thread you downloaded it from for support.
I am stuck in a boot loop.
If you flashed a new ROM and you are stuck in a bootloop, you probably didn't erase your data/cache/dalvik. Try that and reflash your ROM. This will fix most boot loop issues. If it was from something else, make a post in your respective threads or in Q+A.
I am stuck in a NAND Backup!
Pull your battery and restart the backup. You might also want to erase the NAND backup that failed by going to your respective NANDROID backup folder on your SD card.
I am a MAC user and I downloaded ____'s ROM and it doesn't work.
Macs will recompress the file. Use Firefox to download and make sure it doesn't recompress the file. It should work then. Either that or use a Windows based PC.
I tried to NANDROID BACKUP and I got an error message saying "Run 'nandroid-moble.sh' via adb!"
Your SD card is full.
I am having issues with Google Wallet saying it is no longer secure. What is wrong/how do I fix it?
http://forum.xda-developers.com/showthread.php?t=1730837
Custom ROM Reviews
This will be a section where I will do a thorough review of custom ROMs. These are based on my own usage and your mileage may vary depending on what apps/etc you use. I will take requests to do certain ROMs and I will post up a schedule to do reviews so you can send me questions ahead of time. Please also note, that I will only test Sprint ROMs because I only have a Sprint device. I will take reviews from other people on different carriers.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Each ROM will be broken down as follows:
ROM Name:
ROM URL:
Version/Build:
ROM Type: (AOSP/TW/AOKP/ETC)
Recommended for:
Stability:
Features:
Bugs/Issues:
Final Thoughts:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ROM Name: Sprint CM10 Preview Build
ROM URL: http://forum.xda-developers.com/showthread.php?t=1778266
Version/Build: 7/20 Preview Build
ROM Type: CM10 (AOSP)
Recommended for: Experienced flashaholics
Stability: This is a preview build just for the community to see what is in store for their phones on Jelly Bean with CM10. There are bugs expected with this. However for a preview build, this is surprisingly stable. This build came out today and while it is still too early to say it is fully stable, it is surprisingly smooth and as of this moment, it is stable for me. I did run into a very annoying com.android.phone FC loop in the previous build that wouldn't go away till you wipe and reflash the ROM. I'm waiting to see if it happens again on the 7/20 build.
Features: Jelly Bean and all its features. http://developer.android.com/about/versions/jelly-bean.html
It is an AOSP ROM so it has better integration with Google products like Google Voice and no bloat. It is a CyanogenMod ROM so it is made for performance. It is very snappy and will only get faster and smoother once they integrate Project Aurora. If you want to test Jelly Bean, you can flash this. However you are warned that it may crap out on you. If you need 100% stability, then don't flash it.
Bugs/Issues: The camera will take pictures but I did get a force close (FC) on the Gallery and it will freeze. The previous builds did have a green hue over the camera but that is fixed. The widget toggle buttons are being worked in but they are not working as of this build. Facebook integration with contacts isn't good. Contact images do not get linked/joined with existing Google contacts. Bluetooth music does not work. Audio over Bluetooth is not working either. Phone calls over Bluetooth work but it is a little distorted.
Final Thoughts:
The reason why I jumped to CM10 despite knowing it is buggy is to try out Google Now with the new speech engine and Project Butter and it did not disappoint. It took a day or so to get Google Now to learn my habits but it was pretty much on point! The new speech recognition engine is AMAZING! Very quick and the most accurate I've used to date and I've used a lot. Overall, I would recommend this for anyone who wants to test the latest and greatest Android flavor but can work though bugs and issues.
Reviewed on 7/20/12 @ 1:46PM EST.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you want to ask me any questions, feel free to PM me or add me on GTalk @ [email protected]
Rooted Application Reviews
This will be a section where I will do reviews of rooted applications. These are based on my own usage and your mileage may vary depending on what apps/etc you use and what you use it for. I will take requests to do certain applications and I will post up a schedule to do reviews so you can send me questions ahead of time. Please also note, that I am on a Sprint device. I have bought a few paid rooted applications and utilities but I can't buy them all. I hope that I can get some donations going so I can buy more of these applications to review. If you are an application developer and would like me to review your application, please PM me and I'll toss one up.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Each application will be broken down as follows:
Application Name:
Developer:
Developer's Site:
Version/Build:
Application Description:
Stability:
Features:
Bugs/Issues:
Final Thoughts:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Application Name: Titanium Backup
Developer: TITANIUM TRACK
Developer's Site: http://www.matrixrewriter.com/android/
Version/Build: 5.4.1.1
Play Store Link: https://play.google.com/store/apps/...xMiwiY29tLmtlcmFtaWRhcy5UaXRhbml1bUJhY2t1cCJd
Paid/Free? Both.
Price: $6.58 USD
Application Description: You can backup, restore, freeze (with Pro) your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card. You can do 0-click batch & scheduled backups. Backups will operate without closing any apps (with Pro). You can move any app (or app data) to/from the SD card. You can browse any app's data and even query the Market to see detailed information about the app.
Stability: Very stable. It works with all ROMs I've used across many devices.
Features: TOO MANY! Look in the Play Store for features
Bugs/Issues: Very little if any.
Final Thoughts:
Titanium Backup has been on all the phones I have used and it is VERY VERY VERY handy. I highly recommend everyone use this for backups. The pro version allows you to auto upload your backups to the cloud so you don't waste space on your device plus other features. It also helps you get rid of certain apps and freeze them which can be really handy. There are some quirks but not with the application. What I mean is if you restore the wrong application or an application that is not compatible with your ROM, it will cause FC errors. Same thing with deleting a system application.
Reviewed on 7/20/12 @ 1:46PM EST.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you want to ask me any questions, feel free to PM me or add me on GTalk @ [email protected]
sekigah84 said:
Hut!
Click to expand...
Click to collapse
1, hut 2 hut 3 hut, Ol' Dirty Bastard live and un-cut
Can anyone confirm that this method works and what bugs there are? In other words, is it safe!!?
wramos93 said:
Can anyone confirm that this method works and what bugs there are? In other words, is it safe!!?
Click to expand...
Click to collapse
Not as of yet. It's still fresh. I can't comment cause my phone isn't here yet =[
sekigah84 said:
Not as of yet. It's still fresh. I can't comment cause my phone isn't here yet =[
Click to expand...
Click to collapse
Its safe; I'm rooted and using TB like a boss, before this thread was updated.
Though I would like to say that at the end where you list the chmod permissions, you can alternatively just install busybox from the market, after you have installed cwm and flashed the super user zip in recovery.
And with that, my support for this thread too begins.
teh roxxorz said:
Its safe; I'm rooted and using TB like a boss, before this thread was updated.
Though I would like to say that at the end where you list the chmod permissions, you can alternatively just install busybox from the market, after you have installed cwm and flashed the super user zip in recovery.
And with that, my support for this thread too begins.
Click to expand...
Click to collapse
P.S. Your Delorean needs fueling.
sekigah84 said:
P.S. Your Delorean needs fueling.
Click to expand...
Click to collapse
It does, I'll be sure to do so. Also hit me up if you need anything.
teh roxxorz said:
It does, I'll be sure to do so. Also hit me up if you need anything.
Click to expand...
Click to collapse
Will do rox. Let me know about any quirks with the phone.
sekigah84 said:
Will do rox. Let me know about any quirks with the phone.
Click to expand...
Click to collapse
This thing handles like I handle noobs on halo and gears of war: like. a. boss.
Handles multitasking well, played super mario 64 like butter; so far I haven't had any issues at all.
teh roxxorz said:
This thing handles like I handle noobs on halo and gears of war: like. a. boss.
Handles multitasking well, played super mario 64 like butter; so far I haven't had any issues at all.
Click to expand...
Click to collapse
AHHH im jelly. SHIP MY 32GB SPRINT! ROARRRRRRR
I'm doing some self learning ATM to get devin. Hopefully I'll be getting a ROM out within the next few months lol
sekigah84 said:
I'm doing some self learning ATM to get devin. Hopefully I'll be getting a ROM out within the next few months lol
Click to expand...
Click to collapse
Hey power to ya man. You know where to find me.
Noticed people having trouble getting to recovery. For me, trick was NOT holding down power, rather pressing once while holding home and volume down.
Just wondering, does the process that flashes cwm recovery through Odin, then flashes the root through the recovery, does that manipulate the kernel at all? And if it does will I have to worry about signal issues or low bars? I want to keep my phone as stock as possible, but want to remove bloat, and possibly tether. But want to maintain the integrity of the kernel by not making drastic change to it. Can someone explain to me what this root method actually does to allow access? Thank you for your time.
I will update this to combine all information across carriers soon.
wpjessie said:
Noticed people having trouble getting to recovery. For me, trick was NOT holding down power, rather pressing once while holding home and volume down.
Click to expand...
Click to collapse
Basically hold down the power button, but when you see that blue flash that says recovery at the top of the screen, release the power button.
rogermhoffmanjr said:
Just wondering, does the process that flashes cwm recovery through Odin, then flashes the root through the recovery, does that manipulate the kernel at all? And if it does will I have to worry about signal issues or low bars? I want to keep my phone as stock as possible, but want to remove bloat, and possibly tether. But want to maintain the integrity of the kernel by not making drastic change to it. Can someone explain to me what this root method actually does to allow access? Thank you for your time.
Click to expand...
Click to collapse
Basically flashes the CWM recovery, install su, binaries, ect. The kernel is still stock, and you'll be able to remove bloatware and use rooted apps.
I have checked the other threads where people have posted this same error message, but found only a vauge reference to a "flashtool" and some comments about baseband versions. So, hopefully, if i make a greater description in detail here someone might have a few other tips or ideas.
I love the Motorola Defy. I have owned several and found it to be an excellent device. I have tested the ruggedized feature as thoroughly as one may ever imagine and only successfully killed one device (it fell into a hot tub and sat there kind of boiling for a while, ha!)
I currently have two Defy devices. One primary (we'll call this my A phone) and the secondary that i use for dev, testing new ROMs, tweaking, and as a backup (the backup phone's earpiece speaker died so that's why i still keep it around but only as a backup) which we'll call my B phone. Until recently, i was running CyanogenMod 7.1 on these phones.
A few days ago, my primary phone was having network problems. I was visiting rural Iowa, where a buddy of mine (who also has T-Mobile) used to live and he even prepared me by saying "get ready for some iWireless fun!"... indeed, once on the ground out there i constantly failed to have T-Mobile signal, and their roaming agreements with others seem to be a patchwork mess. I could go into...
System Settings > Wireless & Networks: More... > Mobile Networks > Network Operators
...and the "Available Networks" would occasionally show T-Mobile, it would always show AT&T, and sometimes another minor carrier (like iWireless, etc)
I successfully would "force" the A phone to select T-Mobile and it would be happy for a while, then after lots of rural driving it would seem to get lost again. When i flew home back to a proper city, all was well with the A phone again and it remained happy. Suddenly, however, just the other day it lost GSM signal. When i went back to the "Available Networks" screen i started getting the "Error while searching for networks" message. I've had this happen on other drvices before and it would often right itself after a few reboots and i never knew why.
Since i was planning on upgrading my ROM anyway, i took out my B phone (which i use for testing, etc) and fired it up. It was still running CM 7.1 and when i swapped my SIM card over, everything was fine. Just for fun, i made a nandroid backup from this phone (the working B phone) and pushed it onto the A phone. Still the same problem with the A phone... "Error while searching for networks"
I downloaded the latest nightly of CM10 (and i'm ever so distressed to see that CyanogenMod still does not have permission management replaced. How much money someone at Google paid them to take that out we'll never know) and installed it fresh on the B phone. I did a fresh install of CM10 on the B phone and really liked it. After some tweaking, installing basic apps, etc. i was pretty satisfied. I made a nandroid image of the B phone's new CM10 environment and pushed it to the A phone. Still the same problem... "Error while searching for networks"
Now i'm really stumped. These are both running with identical settings, etc...
Model MB525
Android 4.1.1
Baseband EPU93_U_00.60.03
Kernel 2.6.32.9-ga649a2e
CyanogenMod 10-20120924-NIGHTLY-mb525
... and as of just a day or so ago, the A phone had no problems with its radio. It wasn't dropped or otherwise subjected to anything funny. People have made reference in other threads to tweaking the baseband somehow (although this wouldn't seem to be an issue, since both devices show the same identical details when i check the About Phone status) but just in case, i updated my Baseband Switcher and tried to force the A phone to some other setting, then back to the USA setting. Still no joy.
Here's something weird, though... currently the IMEI shows as all zeros on the A phone (the phone with this problem). Is that normal, when the phone is not on a network? What could cause that? Is this perhaps just a fluke hardware problem that i've identified after trying everything else?
I also seem to see conflicting information (or unclear wording) in other threads about the kernel. Is it or is it not part of what gets backed up with a nandroid backup? I would try updating or fussing with the kernel, but as you can see from my text above... even the kernel version appears to be identical between both phones.
So, there you have it. Now i have two phones...
A phone - used to be my primary, until the radio nuttiness and permanent "Error while searching for networks" condition
B phone - used to be my secondary due to faulty earpiece speaker, now my primary so i just either make speakerphone calls or text for now
... and no matter what O/S i run on them (i've tried switching back with nandroid to CM 7.1, CM9, etc etc) they all manifest these same behaviors. Anything else i can try or do you think my A phone's radio is just shot somehow? (Frustrating because it was litterally fine merely days ago. Ah well, everything works until it doesn't.)
"Error while searching for networks" detailed discussion
If anyone out there has some really deep knowledge about what the Android system does when it interacts with the radio and searches for networks, etc... i'd love to know. It's always so disheartening when a non-specific error message appears and you have limited means of discerning exactly what is happening under the hood to cause it.
picked up another phone... same problem
on a whim i picked up another Motorola Defy because i utterly love these devices and they are starting to go away... the restore with clockworkmod was perfectly simple and straightforward... but the new phone has the same problem: "Error while searching for networks" and there is no way of connecting to any GSM tower.
this is incredibly frustrating, and i cannot for the life of me figure out what the difference between these phones can be. why would one phone be connecting just fine and the others totally and utterly failing to? they are all US T-Mobile Defys.
i'm going to borrow a buddy's SIM card and see if it will register on any network, maybe my SIM is just doing something loopy.
IMEI all zeros
on all of the phones that are experiencing the GSM problem, Android reports the IMEI to be all zeros under "About Phone"
this is also the case with the latest brand new phone that i just purchased. now, i'm fairly certain that this wasn't the case until i put the CyanogenMod 10 ROM on it. how the hell can a ROM foul up a radio so badly? (and how can it happen on just some phones but not others of identical model?)
a-ha, i may have discovered something non-symmetrical between these phones after all...
there are slight differences one phone's kernel version data. they are very slight, only pertaining to details after the version number. (which, for all i know is just a checksum or some other value specific to when the kernel was compiled)
Phone #1 (currently can connect to GSM networks)
Kernel version
2.6.32.9-ga649a2e
[email protected] #1
Thu Jan 20 07:50:55 CST 2011
Phone #2 (used to connect to GSM networks but no longer does)
Kernel version
2.6.32.9-ga649a2e
[email protected] #1
Thu Jan 20 07:50:55 CST 2011
Phone #3 (brand new and has never connected to any network under CM10)
Kernel version
2.6.32.9-ga28fcc4
[email protected] #1
Wed Apr 6 15:55:29 CST 2011
... so, that seems to raise more questions than it answers for me. two of them appear to be completely identical, yet they behave differently with the SIM card (Phone #1 sees networks, Phone #2 does not).
the last one, Phone #3, has slightly differing kernel version data but i don't know why. that phone also cannot see networks.
Deviant Ollam said:
that phone also cannot see networks.
Click to expand...
Click to collapse
read this http://forum.xda-developers.com/showthread.php?t=1857054 , If you have 0000 as your IMEI, you may have to correct it for it to be allowed to connect by some networks
i'm reading other forums and seeing repeated references to the files...
libril.so
librilswitch.so
... which appear to live in /system/lib
one user on a forum asserts that "These types of bugs are due to mismatched RIL and Radio" but does not offer any information on how one might go about checking this or addressing the problem.
i'm going to try copying those two above-mentioned files from the "working" phone and pushing them to one of my non-working phones. let's see how this goes.
(and, of course, anyone with real knowledge in this area is free to jump in at any time... but for now this is a sort of fun intellectual exercise, just seeing my own process play out in this thread that i alone am posting in. ah well, maybe it will help some future person someday.)
xsenman said:
read this http://forum.xda-developers.com/showthread.php?t=1857054 , If you have 0000 as your IMEI, you may have to correct it for it to be allowed to connect by some networks
Click to expand...
Click to collapse
thanks! great irony, to see an expert pop up right as i comment about being monologing to no one in this thread, hah. i'll read that other thread right after i try my file copy experiment.
i've copied over libril.so and librilswitch.so to the non-working phone's /system/lib directory, but i see that the permissions were altered in the process. i've fixed that (set them to RW- R-- R--) but now i wonder if a chown command is in my future, too.
xsenman said:
read this http://forum.xda-developers.com/showthread.php?t=1857054
Click to expand...
Click to collapse
upon reading that, i started to follow instructions for repairing a lost IMEI.
one of your instructions in this post is to "Download EFS Folders for modification and restoration My Android Collection" however when one visits that link there does not appear to be any entry (even when you expand all the sub-sections) called "EFS Folders" or anything that makes mention of "modification" or "restoration"
help?
Deviant Ollam said:
there does not appear to be any entry (even when you expand all the sub-sections) called "EFS Folders" or anything that makes mention of "modification" or "restoration"help?
Click to expand...
Click to collapse
sorry its in My Android Solutions and mostly for Samsung , none for motorola, you may need to search google . But mostly flashing the initial STOCK firmware the unit came with would correct it
maybe i'm misunderstanding what you mean when you say the "efs folder is found in your root of your Internal Phone memory"... because none of these three phones appear to have any folder called "efs" anywhere i can find it, least of all in the root location (at least when viewed with Root Explorer)
in the root path i see folders like...
acct
cache
config
data
dev
etc
mnt
pds
... and so on and so on, but no efs folder in there. is it a hidden folder? is there a way one must manually turn on the viewing of hidden folders in Root Explorer?
xsenman said:
flashing the initial STOCK firmware the unit came with would correct it
Click to expand...
Click to collapse
heh, that sort of reminds me of using a recovery CD that would ship with PCs back in the day... where does one acquire the stock firmware that comes with a device? is there a hidden recovery partition that does not get disturbed somewhere on the phone?
i tried to choose "stock recovery" instead of "custom recovery" in my bootloader, but that just resulted in the boot error image (similar to this but with a little android figure as opposed to a phone)
EDIT: seems like RSDLite with the stock SBF file might do me right. i have both of those (but i recall RSDLite being an absolute bastard when it comes to ever seeing a phone properly) so i'll try that.
Deviant Ollam said:
... and so on and so on, but no efs folder in there. is it a hidden folder? is there a way one must manually turn on the viewing of hidden folders in Root Explorer?
Click to expand...
Click to collapse
yep, it should be hidden and cannot be edited , and all the information, I am able to provide is based on Samsung, so I am afraid it can be different for your units.
---------- Post added at 11:37 AM ---------- Previous post was at 11:35 AM ----------
Deviant Ollam said:
i have the original backups from my very first Motorola Defy, if that will work. or is there a stock Defy image somewhere kicking around online?
Click to expand...
Click to collapse
try your original backup. that should do it
---------- Post added at 11:44 AM ---------- Previous post was at 11:37 AM ----------
use your WIKI http://forum.xda-developers.com/wiki/Motorola_Defy
xsenman said:
yep, it should be hidden and cannot be edited , and all the information, I am able to provide is based on Samsung, so I am afraid it can be different for your units.
Click to expand...
Click to collapse
any suggestions on where i might look, heh?
xsenman said:
try your original backup. that should do it
Click to expand...
Click to collapse
sadly, i misspoke... don't have the original backup for this device. i have only backups after installing CyanogenMod in various stages
trying now to download the stock rom from the wiki. i cannot say how much of a strong and passionate hatred i have for all these goddamn terrible upload sites. is there a reason that the community can't just settle on ONE that is reliable and useful? the stock Froyo rom for my Defy is linked in a thread with a multiupload link and that forwards to a lnx.lu link which is a steaming pile and doesn't even load in Chrome or Firefox. It loads in IExplore but doesn't download.
is there not just one standard site where people would upload??
got RSDLite to recognize phone
so... for those who later find this thread and keep on reading (i'm continuing to post in the spirit of this) i will report that now RSDLite is updating my phone back to the Froyo 2.2 stock image that i have.
getting RSDLite to see the phone involved getting it into the bootloader (not, as i now realize, the "boot menu")
power on Motorola Defy with VolUp pressed... bootloader (some folk even say that hold VolUp while inserting battery)
power on Motorola Defy with VolDown pressed... boot menu (and then recovery)
... so that was the trick on that one, i do recall knowing that in the past. learning is fun. re-learning is less fun.
wonder of wonders... using RSDLite to push the stock 2.2 rom to the phone worked, and upon boot (wherein the whole MotoBlur nonsense started) i was able to see that the phone thinks it has an IMEI number now! so now i'm going to see about doing a step-by-step upgrade to CM10 and i'll see if the IMEI stays put. =)
Deviant Ollam said:
wonder of wonders... using RSDLite to push the stock 2.2 rom to the phone worked, and upon boot (wherein the whole MotoBlur nonsense started) i was able to see that the phone thinks it has an IMEI number now! so now i'm going to see about doing a step-by-step upgrade to CM10 and i'll see if the IMEI stays put. =)
Click to expand...
Click to collapse
make a nandroid backup using CWM first so that you don't need to do it all over again
xsenman said:
make a nandroid backup using CWM first so that you don't need to do it all over again
Click to expand...
Click to collapse
hah, yeah... that's the first thing i'm doing.
Just a noob sharing some thoughts, hope it can help some other noobs like me.
A no wipe in my book:
Here is how i do a no wipe.
In recovery, mount and storage and choose format system.
Go back and wipe Cache and Dalvik
Install / flash the rom.
A full wipe in my book:
Into recovery, mount and storage and format system, data and cache.
Go back, wipe/ reset data, cache and dalvik.
Install/flash rom
Format of the internal SD:
Here is what i do:
Make a app backup with TB to my external sd
Make a nandroid to my external sd
Make sure i also have a efs backup on my external sd
I only save mods, roms on my internal sd in my download map and this map i move to my external sd.
Then i reboot to recovery.
Mount and storage and format internal sd.
And to be save and have it nice a clean, also format system, data and cache and because i am not only a flashohalic but also a cleanohalic, i then wipe/reset factory reset, cache and dalvik.
Probably a big overkill, but he, done it several times it works for my and it only cause a few seconds.
Then i reboot, skip the setup/registration, move my download map back to my internal sd (don't like flashing from external sd).
Back in cwm, again a full wipe which includes the formats data, system and cache.
Then flash the rom and setting it up.
This way, you have a nice clean fresh S3, but and this is a big BUT.
Backup, backup backup and don't forget a efs backup to your external sd and pc.
Don't think lightly about those backups, when imei is broken and you don't have a backup, your a done, only thing left is a visit to Samsung.
Good luck when you are going for it.
And i know, Aroma installer is also doing some automatic wiping, but i am just a bit old fashion and like to do some stuff manually.
Bootloader.
As you all know, the new bootloader can be a pain in the ass.
But, i am still not sure that Samsung only released the new bootloader just to discourages us to flash custom stuff.
So, if you like flashing stuff and you are on the new bootloader like me, just remember when you entered recovery and you are done flashing stuff, use Triangle Away from Chainfire,
But, for some, like on my wifes phone, the latest version works without problem, but on my S3, i need to use the older version, 2.37, why, don't have a glue.
Not all S3 are the same, although have the same name and using the same chipsets.
But you can also use the old bootloaders, with does, you just have to run Triangle Away just once, when entering recovery, it will not count.
Your own choose.
About Sudden Death.
A lot of threads are open for this.
My 5 cents:
I have the "sudden Death" chips VTU00M chip with 0xf1 on both our phones.
Mine is running since 27 may 2012 without problems, still fast and smooth.
The other is up and running since 31 Augustus 2012 and also still fast and smooth.
Both have been rooted from day one, the only thing i do, is turning the devices off completely for a few minutes 4 to 5 times a week.
Old habit to clear memory, anyway, gives me time to do a good cleaning of my screen.
Here is the code to check your revision and to see from which day you are running your S3 *#12580*369#
Further more, AndreiLux found i string in the ELLA kernels released by Samsung that looks like that it solves the sudden death issue.
So, if indeed if fixes this issue, then off course the latest kernels releases from Sammy has also the fix and not just the custom kernels.
As far as i know, all the custom kernels has the fixes integrated this string by now, but i myself like the stock kernels, Indie puts in the Omega Roms.
Phil3759 has also made a repack of recovery based on CWM touch 6.0.2.7 to get it all safe.
More to come in the future, because i am learning everyday here on XDA and like to share and help others.
Edit, here is quote from AndreiLux about the new bootloader:
http://forum.xda-developers.com/showpost.php?p=37163086&postcount=1298
Do I need any particular Bootloader? No - There is no evidence to suggest this fixes anything
Apparently that's wrong, download mode on the device uses a microkernel from inside the bootloader instead of the full blown Linux kernel. When flashing something via Odin in download mode you'd be using the bootloader's MMC driver and thus be at risk.
All-day users are still safe via recovery and live kernel, but are not advised to flash things in download mode with an older bootloader. This also explains why they updated the bootloader in LLA. The security checks are a mere update to bring it up with what the 9305 and Note 2 users already have in terms of not able to get rid of the exclamation mark.
Personal note:
Maybe i am seeing this wrong, to much thinking in terms of home computers, but here is some thoughts regarding above.
From cold, turned off device,.
Turning the device on, micro kernel inside the bootloader kicks in to send information how to start the device correctly.
If it works this way and you are on the old bootloader, then every time you start the device with the old bootloader, you are at risk?
Some useful links:
My struggle with TA
Omega roms S3
Chris_84 Faq
Triangle Away
http://www.chainfire.eu/articles/118/Triangle_Away_vs_Samsung/
Old bootloader
Philz recovery
https://www.google.nl/search?q=andr...s=org.mozilla:en-US:official&client=firefox-a
https://play.google.com/store/apps/details?id=com.electricsheep.asi&hl=nl
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Here i will post stuff that comes along the road like question about batterystats at recovery.
We used to have a option to wipe the battery stats at recovery, also there are some tools at Play store that claims to give a better battery life by just wiping those stats.
But after reading this excellent article, it comes clear that wiping those stats are bull.
So i am glad that option isn't available anymore and perhaps in time, the questions about those stats will faint away in oblivion
And another one i like to share.
Fast Dormancy.
Here is a great article about it, made by Erica.
For me, my provider is saying it's not supporting FD, but when use the method to check, it is supported.
So i tested it for a few days on and off and found that when it's off, i do get some better battery life, but it's just minor.
Instead of losing 5% battery at 8 hours standby, i lost 6%.
Also, i didn't see any benefits in speeds, so i turn it off every time after a flash of a new rom using gokhanmoral tool.
Another thing i like to add.
Wifi.
I have seen many posts about wifi problems.
Here what always works for me.
Sometimes just a reboot of the router will help.
Also, i find changing from dynamic (default) to static that my connection is faster connecting to my router (always use the never setting at wifi advanced to save battery).
Here is how to do it the easy way.
First set it up using it with the default dynamic settings, this way all will be filled in for you.
To change it to static.
Long press your connection and choose modify network config and check show advanced options.
Scroll down a bit and tap on IP settings and choose Static.
And that is all, now you have changed it to static and there is no more need for ip adress to negotiation any more.
https://www.google.nl/search?q=wifi...s=org.mozilla:en-US:official&client=firefox-a
Also if still having problems, adding some more permissions can solve it.
I use root explorer for this
ETC > Long press wifi folder and choose permissions (remember to change Mount R/W to Mount R/O) and check all nine boxes.
Hit back and go to Data > Misc and again long press wifi folder and again, check all nine boxes.
Space
I know, i am a control freak and i hate it when i see space just vanish.
So did some search and found a thumbnail map with more then 1gb size.
Looked at some submaps and i only saw some old stuff.
So, selected all the submaps and just deleted it without problems and gain more then a gb free space.
Here is where you can find it using root explorer:
storage > sdcard0 > .thumbnails.
Edit:
As bigmo7 pointed out, the thumbnails will be rebuild, but off course not off stuff that isn't present on the S3 anymore.
So, if you are someone that is just making pictures or making / creating movies and never delete then from your S3, there is no point off deleting the thumbnails.
But if you like me, moving, creating copying and deleting this kind off stuff, then you can gain space.
Battery life
Always a hot item.
First all, the S3 is a mini computer and computers need juice, just remember this.
Here are some stuff i always do after flashing a new rom.
If the rom comes with a aroma installer which let you select stuff to install or not install, look careful to the list.
Stuff you don't use, can just eat resources and i myself, just find it a waste.
Next, after flashing and setting up the new rom, you will be presented with the option to use wifi.
I always go to advanced when making a wifi connection to choose Never when phone is in standby.
For me, but this can be different for you, wifi is a bit off a drainer so do some testing, let it run overnight with Always selected and another night with Never and see the difference.
Next you will be present if you want to restore and let google backup your phone.
I always deselect backup my phone, first reason, i am a control freak and i decide when and what i want to backup.
And second it can give you wakelocks and this will cost you battery life.
Next step i do is going into settings and to sounds, i don't like the clicking sounds and i deselect all the system sounds.
Next, location services and deselect GPS and Location and Google search.
I want GPS active only when i need it, some apps like Facebook will activate GPS when running and i don't like this.
And i don't want Google to know where i am all the time.
Some weather apps needs Location and Google search to determine your location, but i use Weather pro and it don't need it.
Next step is going into accounts and look what you have selected for syncing.
I always deselect Google photos, Internet and Picasa web albums.
Stuff i don't need .
Location settings at accounts is also off.
Next step is using the Fast Dormancy toggle to disable Fast Dormancy, although my provider is supporting it, enabled costs me a little more juice. Although it's minor, but a lot off minors things makes it bigger .
Then starting Playstore and at settings, deselect Notifications.
And finally freeze stuff i don't use with Titanium Backup pro.
http://forum.xda-developers.com/showpost.php?p=31576747&postcount=105
All this, is giving me a great battery life, with screen on time between 4 1/2 to 6 1/2 hours, depends what i am doing.
And with the latest JB roms, 1 to 2% battery los in 7 hours standby.
No need for me to toggle Airplane mode, mobiledata or some other powersaving setting or app.
I am also always running the stock insecure kernel that comes with the rom, for me no need for a custom one.
Reserved
KeesStolk said:
I only save mods, roms on my internal sd in my download map and this map i move to my external sd.
Click to expand...
Click to collapse
Hello, when we flash a rom that already has mods ... do you know a way to save them ? (where to find them)
I mean. For example, my rom has a mod (and theme) on the toggles (pandoriam i9305). How can I save that mod ? Do you know a good tutorial to learn (safe) modding ?
thorcyar said:
Hello, when we flash a rom that already has mods ... do you know a way to save them ? (where to find them)
I mean. For example, my rom has a mod (and theme) on the toggles (pandoriam i9305). How can I save that mod ? Do you know a good tutorial to learn (safe) modding ?
Click to expand...
Click to collapse
I never save mods because most of the time when flashing a new rom, it's based on a new build and not every time mods are compatible, just like some themes by the way.
I just safe the mod files and thems, when i am sure they are compatible, i just flash them again.
Indie's Omega roms has already a lot of mods in it by default by the way, but i don't think he was for a 9305.
Good work Kees! Now I'm learning from you.
Chris_84 said:
Good work Kees! Now I'm learning from you.
Click to expand...
Click to collapse
Thank you for your kind words, but it is l who is learning from you every day .
Sent from my GT-I9300 using Tapatalk 2
and why dint i see this , brilliant my friend .... one of the best posts , well explained and really good stuff all at one place
thanks my friend
vegeta1 said:
and why dint i see this , brilliant my friend .... one of the best posts , well explained and really good stuff all at one place
thanks my friend
Click to expand...
Click to collapse
Thank you very much, but from you, Chris, Indie and the rest of the omega team are the ones I learn all this great stuff every day.
Sent from my GT-I9300 using Tapatalk 2
i always feel like a noob when ever i read here
big big thanks my friend for pointing out all this so nicely
Very nice posts KeesStolk. Maybe you should write a manual for us?
I'm about to post this in Q&A (searching for an answer brought me here )
I just (3 days ago) upgraded my Omega ROM to v40. All seemed fine - I did as normal but in v35, my last Omega there wasn't a Full Wipe option. I chose not to wipe and everything went as per usual with Omega. I reinstalled my extras (6 x 5 icons, Loud phone hack, Increasing ring phone, Note2 Keybd) and was back to normal.
Except, now my apps will not update.
I found out the hard way. I had a problem with Play Store - open it and it would flash briefly then close. Tried all I knew of but nothing worked so, logic said, Omega v40 is different enough I need a wipe and that why they put it in there as a choice this time. (I checked the Omega thread and couldn't see anything relevant but I was in the pub at the time and may not have been as thorough as I should have been)
I had a TB backup and Nandroid on my ExtSD from 2 days back and an EFS so I ran the install again and chose Full Wipe - again everything went well... until I tried to download TB so I could restore all my apps and data. Play Store opened and stayed Open (yaaaay!) and TB acts like it is downloading but nothing comes through - it just sits until it times out on an error.
I tried several apps and none would DL but then AuWeather DL'd just fine. I went back to TB - no go.
After much frustration I Restored my Nandroid and got back to where I was (Omega v35) but still I can't DL and update for TB. At least Play Store stays open though. I tried running the v40 update again, installing the Default, just in case, (& I have just finished DL'ing v41) but the DL/Update problem persists.
I'm now on:
AP – I9300XXEMA2
CP – I9300BUELK1
CSC – I9300LBEMA1
RF cal – 2012.6.28
HW Rev – MP 1.100
Any ideas? If I can't DL TB once I have flashed, I can't get my data back so a wipe isn't really an option until I fix the DL issues.
As I said, this will also be in Q&A but you seem to have a good grasp on the basics so I thought maybe...? :fingers-crossed:
So... I tried restoring back to v35 and got the same problem. And yet that version has been running since v35 came out, at least a couple of months. So I did it again but this time used the Android Revolution Wipe zip, then a straight install of v35. I could then load TB from Play Store and restore my apps and data. Phone seems back to normal now although I have lost some logs data from the couple of days between my backup and now - no biggie... I also now can update my apps.
So it seems it is something to do with Omega v40.
I've just DL'd v41 so will give that a try. Any help with what might have gone wrong would be much appreciated.
Thank you for your kind words, just sharing what i know and hoping this info can help others.
And how is it with v41?
Did you tried it with wifi and 3g, any difference?
Also tried removing your google account, reboot and setting it up again?
Hi kees !
Nice idea you've got with this thread but ... I hope it won't turn into another omega q&a thread . I would like to direct people here but it will be quite difficult if they will see Omega issues all over. Please point them out to the correct thread as you already posted the link to it. Just a thought , correct me if I'm wrong
Thanx !
Sent from my GT-I9300 using Tapatalk 2
xanthrax said:
Hi kees !
Nice idea you've got with this thread but ... I hope it won't turn into another omega q&a thread . I would like to direct people here but it will be quite difficult if they will see Omega issues all over. Please point them out to the correct thread as you already posted the link to it. Just a thought , correct me if I'm wrong
Thanx !
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks and you are right, but the main purpose for me, is just help others with the noobish knowledge i have and let people and myself learn and share.
I don't mind which rom people are running, that's everyone his or here's choice and i totally respect that.
I think this thread deserves to be in General, since you're not asking anything. Hit "report" and see what a mod thinks about it
KeesStolk said:
Thanks and you are right, but the main purpose for me, is just help others with the noobish knowledge i have and let people and myself learn and share.
I don't mind which rom people are running, that's everyone his or here's choice and i totally respect that.
Click to expand...
Click to collapse
absolutely !!!
everyone`s choice ! but people must follow proper threads , i`ve got nothing against a certain rom but against disarray when users post or open endless threads about same thing .
some users hates me for this , i know it well , in my thread i always pointed out but somehow is unfair to maintain same topic on more threads .
that`s a bad habit for new users and not only for the rule`s sake but this is the way should be in a human community .
-=-=-
i was thinking as well to open a thread as yours but due to lack of time i didn`t. as soon as i`ll find interesting things i`ll let you know .
i myself am a NOOB !
---------- Post added at 11:28 AM ---------- Previous post was at 11:24 AM ----------
Glebun said:
I think this thread deserves to be in General, since you're not asking anything. Hit "report" and see what a mod thinks about it
Click to expand...
Click to collapse
... and i must agree with you this time ...
Thanks guys.
@xanthrax, i know the feeling, kind off busy family
But i like your comments, just straight forward, the way i like it.
Glebun said:
I think this thread deserves to be in General, since you're not asking anything. Hit "report" and see what a mod thinks about it
Click to expand...
Click to collapse
I think it should stay here as it "Helps" other users. General is more for discussions IMO.
But how about these?
http://forum.xda-developers.com/showthread.php?t=1749214
http://forum.xda-developers.com/showthread.php?t=1827635
http://forum.xda-developers.com/showthread.php?t=1732722
http://forum.xda-developers.com/showthread.php?t=1895737
http://forum.xda-developers.com/showthread.php?t=1946481
http://forum.xda-developers.com/showthread.php?t=2041679
and that's just the first page. all of the above are for "help"