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"
Related
Ok, before you tell me to search, I have. For two days. I have looked at everything from forums to youtube videos on how to root the droid eris. The thing I am trying to do the unrevoked method. The thing I can't get past is in the begining. I go to the hboot screen by pressing volume down and power. I plug in my usb cable and nothing happens. I think I'm supposed to see it say hboot usb plug. It doesn't. I go to devise manager just to check and it doesn't show my phone. So I'm sure you can see my frustration not even being able to get past the first step. Any help would be great.
Thanks,
Matt
Got it fixed using the 1 click root from the market. Then added XTR Sense rom. Works great.
Congrats and welcome to a whole new Eris!
Yes, congratulations, and furthermore, excellent choice of a "replacement" ROM, I just recently went back to xtrSENSE after perhaps four months playing with Froyo.
FYI, I suspect the issue was you might've needed the Windows drivers for the phone loaded before using the unREVOKED method, but it's just a guess.
Install HTCSync (available from HTC's website) for the Droid Eris and that'll install the correct drivers, which will take a moment to load the first time you plug your phone in via USB next time. Also, give it a moment to load those drivers before doing anything like mounting the SD card to the computer via USB.
I just rooted mine back in December and the 1 click was the one that made the most sense for me, i didnt even kno bout the unrevolked til after i was rooted....but im loving the cm7 gingerbread roms, for being such early versions there really stable
Sent from my GSBv1.5-ERIS using XDA App
Pauly2277 said:
I just rooted mine back in December and the 1 click was the one that made the most sense for me, i didnt even kno bout the unrevolked til after i was rooted....but im loving the cm7 gingerbread roms, for being such early versions there really stable
Sent from my GSBv1.5-ERIS using XDA App
Click to expand...
Click to collapse
Belated welcome to rooting, then.
roirraW "edor" ehT said:
Belated welcome to rooting, then.
Click to expand...
Click to collapse
Why thank you sir....i just dont kno why i didnt do it earlier
Sent from my GSBv1.6-ERIS using XDA App
Pauly2277 said:
Why thank you sir....i just dont kno why i didnt do it earlier
Sent from my GSBv1.6-ERIS using XDA App
Click to expand...
Click to collapse
You were probably afraid that you'd let the smoke out.
I'm about to take the plunge myself. I use the Trackmaster app for recording lap times. From my research, Sense does not support the SPP (Serial Port Protocol) bluetooth profile. But, I understand that a non-sense (AOSP) ROM will have the entire bluetooth stack intact.
I've been following the tazz and shed GB threads with much admiration. It's just amazing what some folks will do for coffee money. And guys, I wish you all the best with your personal struggles!
My plan is to root this week. Make sure the phone remains stable. Practice that Up-Volume & Power Button thing a few times to make sure I can follow the flash procedure. Then grab GB next week.
I've read the rooting for dummies thread, and will use the one-click root app from the market. Free one first. Then if all is well I'll download the pay one.
Successful GB load will get a meal, and after I confirm my bluetooth GPS unit works with Trackmaster, coffee money will follow.
As you may be able to tell from the above sentence fragments (or maybe the straight forward I don't give a sh.t if I violate any social protocol plan) I'm a former Engineer (retired), so constructive advice / criticism is greatly appreciated. And I got the time to double-check everything.
Alan Wolfe
Many people with less analytical skills than you have rooted, and it sounds like you've done your homework, so it should be a snap for you. The only thing I will add is to re-emphasize what you proabably have already read - that you should:
- check the file integrity of all file downloads (using MD5 sigs or "jar verify" principles for ROM files, e.g. use 'scary alien's" AFV (Androd File Verifier) free market app)
- charge the phone well before any flashing operations (and don't let it sit in HBOOT or Fastboot modes for extended period of time - it discharges rapidly, even if plugged in)
- make a Nandroid backup of your existing ROM. If things don't work out with the BT issues, you can always go back to where you were, little worse for the wear.
cheers and good luck
Thanks - didn't have the MD5 crypto check in the plan, but it is now.
I just can't believe how good the work being done here is. I used to contract for much poorer work for much more money! This just proves that passion beats bucks every time!
p.s. I pushed that Thanks button for you, but damned if I can tell if it worked
p.p.s Got the Thanks thing - I see it now.
bftb0 said:
Alan Wolfe
Many people with less analytical skills than you have rooted, and it sounds like you've done your homework, so it should be a snap for you. The only thing I will add is to re-emphasize what you proabably have already read - that you should:
- check the file integrity of all file downloads (using MD5 sigs or "jar verify" principles for ROM files, e.g. use 'scary alien's" AFV (Androd File Verifier) free market app)
- charge the phone well before any flashing operations (and don't let it sit in HBOOT or Fastboot modes for extended period of time - it discharges rapidly, even if plugged in)
- make a Nandroid backup of your existing ROM. If things don't work out with the BT issues, you can always go back to where you were, little worse for the wear.
cheers and good luck
Click to expand...
Click to collapse
One thing to add: the Gingerbread ROMs require you to download and flash a google apps .zip file before you restart the phone, unlike many other ROMs that include Google apps as part of the ROM. So, that is one more file that you need to check an MD5 hash, and the procedure will be something like this:
- download and verify the GSB/Tazz and Google apps zip files
- copy them to the root directory of the SD card, and check the MD5s there as well
- root the phone
- restart it to get the root process to install custom recovery
- restart in Recovery
- Nandroid backup what you have
- wipe data/factory reset
- wipe Dalvik cache
- Flash GSB (or Tazz, whichever one you choose)
- Flash Google apps
- restart the phone
doogald said:
One thing to add: the Gingerbread ROMs require you to download and flash a google apps .zip file before you restart the phone, unlike many other ROMs that include Google apps as part of the ROM. So, that is one more file that you need to check an MD5 hash, and the procedure will be something like this:
- download and verify the GSB/Tazz and Google apps zip files
- copy them to the root directory of the SD card, and check the MD5s there as well
- root the phone
- restart it to get the root process to install custom recovery
- restart in Recovery
- Nandroid backup what you have
- wipe data/factory reset
- wipe Dalvik cache
- Flash GSB (or Tazz, whichever one you choose)
- Flash Google apps
- restart the phone
Click to expand...
Click to collapse
Interesting doogald. I understood that root should be done first before any downloading. Thanks for the above instructions! I had things a little out of order. Would you mind clarifying when the SD card format should be done? I was going to:
- root the phone
- format SD
- copy ROM and gapps
- MD5 check
- restart ... and follow your order above.
Alan Wolfe said:
Interesting doogald. I understood that root should be done first before any downloading. Thanks for the above instructions! I had things a little out of order. Would you mind clarifying when the SD card format should be done? I was going to:
- root the phone
- format SD
- copy ROM and gapps
- MD5 check
- restart ... and follow your order above.
Click to expand...
Click to collapse
Honestly, I think that the SD card format is unnecessary. Unless I am mistaken, it was suggested in part to rule out issues people might be having moving from rooted Froyo to Gingerbread, to erase the SD card's /.android_secure hidden folder - where apps that are moved to SD Card in Froyo are stored. That will not be an issue for you if you are stock Eris.
However, it won't hurt to do it, and that would be the step that it should be done.
Thanks again. Its nice to get confirmation.
Ignorant question - The one-click root app says to "reboot" the eris. How do you reboot the eris?
I searched forum - read the whole one-click app thread - googled "reboot eris" and got nothing.
NEVERMIND!!! I turned the phone off, vol - & power, select recovery with vol +, then select reboot.
And I got a Superuser Permission... widget now.
Alan Wolfe said:
I'm about to take the plunge myself. I use the Trackmaster app for recording lap times. From my research, Sense does not support the SPP (Serial Port Protocol) bluetooth profile. But, I understand that a non-sense (AOSP) ROM will have the entire bluetooth stack intact.
I've been following the tazz and shed GB threads with much admiration. It's just amazing what some folks will do for coffee money. And guys, I wish you all the best with your personal struggles!
My plan is to root this week. Make sure the phone remains stable. Practice that Up-Volume & Power Button thing a few times to make sure I can follow the flash procedure. Then grab GB next week.
I've read the rooting for dummies thread, and will use the one-click root app from the market. Free one first. Then if all is well I'll download the pay one.
Successful GB load will get a meal, and after I confirm my bluetooth GPS unit works with Trackmaster, coffee money will follow.
As you may be able to tell from the above sentence fragments (or maybe the straight forward I don't give a sh.t if I violate any social protocol plan) I'm a former Engineer (retired), so constructive advice / criticism is greatly appreciated. And I got the time to double-check everything.
Click to expand...
Click to collapse
I could tell. The way you wrote reminded me of myself, at least from time to time. And probably even more often how I think.
Alan Wolfe said:
Thanks again. Its nice to get confirmation.
Ignorant question - The one-click root app says to "reboot" the eris. How do you reboot the eris?
I searched forum - read the whole one-click app thread - googled "reboot eris" and got nothing.
NEVERMIND!!! I turned the phone off, vol - & power, select recovery with vol +, then select reboot.
And I got a Superuser Permission... widget now.
Click to expand...
Click to collapse
FYI rebooting the phone at it's simplest is just telling the phone to shut down the Android OS and then boot it back up. This doesn't have to involve actually shutting the power off to the phone but it can if you so choose. Also, some ROMs and/or through some apps/widgets, you can explicitly command your phone to "reboot" from within the Android interface. I just didn't want you to think that any time a "reboot" is needed, that you have to boot into recovery and choose the "reboot" option from there.
It's just like a reboot on a computer. Actually powering the computer off isn't really necessary to affect a reboot.
Welcome to root and XDA!
Thanks!
I saw a lot of references to Titanium Backup so I DLed the free version. Its happy now after I enabled USB Debugging and download from Unknown sources. So now that I have double checked I Know I got root now.
Oh, and since I confirmed root I uninstalled the one-click root app and made a donation to the San Antonio Food Bank.
Welcome to the dark side ! At least we have coffee and cookies here !!! LOL
Seriously though, so what ROM did you end up choosing ? Any time someone new to the forums finally roots and flashes a ROM we like to see how things are going and see that your process was successful !
GSB 1.7
Awesome!!!
Now I gotta finish up downloading my apps and getting things set up. This is totally cool.
I did:
- reformat SD
- copy goodies from PC
- wipe data
- wipe dalvik
- flash GSB
- flash gapps
- flash c2c
- reboot
Sooo I am very happy my Ginger Tazz. It is awesome. Now looking into different themes. One concern is skype mobile says it only works on verizon wireless. Im on VW. Why isnt it working?
Thanks
Sent from my Ginger Tazz using XDA App
msturner79 said:
Sooo I am very happy my Ginger Tazz. It is awesome. Now looking into different themes. One concern is skype mobile says it only works on verizon wireless. Im on VW. Why isnt it working?
Click to expand...
Click to collapse
There are two Skype apps for Android: a "special" one for VZW that does not work with WiFi (at least on the Eris it does not), and a real version that does work over WiFi. The VZW version will use Verizon minutes to make calls to phone numbers but 3G for Skype to Skype (and international calls.) I think that the real Skype app uses 3G or WiFi for everything, but 'm not sure.
In the market: https://market.android.com/details?id=com.skype.raider&feature=search_result and https://market.android.com/details?id=com.skype.android.verizon&feature=search_result
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.
I've recently installed AOKP(Jellybean 4.2.2) Task650 (http://forum.xda-developers.com/showthread.php?t=1808015) and the basic install seemed to go very well. I came from stock 4.0.4 (rooted) and for the record I'm using Recovery 6.0.3.0 and I did a full wipe including format system, data, cache, dalvik etc. I installed the new gapps after the ROM, and later restored apps using Titanium.
I have a few issues I can't quite sort out though, and I'm not sure if they are JB, Nova or AOKP related so I thought I'd start a new thread.
1) Lockscreen doesn't appear. At all. When I wake the tablet up, it just comes straight back on to the previously used screen. I've checked all the standard Security settings (unlock mode set to slide or pattern, lock on power button, etc) and also the fancier AOKP ones, but whatever I do the lockscreen just does not appear. I've re-cleared cache and dalvik.
2) Notifications are not showing in the Notifications area. I can see the AOKP 'Toggles' icons/tiles for wi-fi, bluetooth, GPS, etc; the clock; the battery level; the wi-fi SSID, etc - but no general Notifications at all (e.g. list of any updated apps, any download statuses, Poweramp mini controls, new emails/facebook messages, Samba active display, etc).
When these various notification are issued, I do see them appear briefly in the lower-right corner in a grey rectangular box which covers the clock/battery area of the status bar (so the notifications do appear to be triggering) but as soon as that brief message disappears, I can't see any of the notifications within the pop-up notifications area where they should be.
Does anyone familiar with JB, AOKP or this particular ROM have any suggestions, as I'm as a loss at the moment?
Andre
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
andrewilley said:
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
Click to expand...
Click to collapse
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Hope this helps even a little.
kilometers4 said:
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Click to expand...
Click to collapse
Many thanks for the reply. I have searched and asked in the dev's thread, but I get the very clear impression that if it works on his hardware and no one else has the same problem, his opinion is that it's 100% up to me to sort it out - which is entirely his prerogative, of course: his ROM, his thread, his rules.
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
andrewilley said:
...
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
Click to expand...
Click to collapse
Yup that's the one. I'd recommend doing a full wipe on the first install to avoid issues. Let me know if you have any other questions.
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
andrewilley said:
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
Click to expand...
Click to collapse
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
kilometers4 said:
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
Click to expand...
Click to collapse
Yeah, I'm normally the same but I thought I'd be nice and thorough for once and get rid of any remaining legacy ICS stuff which some JB updates shove into hidden folders when you upgrade. In hindsight, I shouldn't have bothered.
Still, at least when I finally did get the system recovered enough to install the new ROM, the free space was amazing!
Andre
I got the same problem...how to solve it bro....
srinuchry said:
I got the same problem...how to solve it bro....
Click to expand...
Click to collapse
I think the problem may have been with something that Titanium Backup restored from my previous setup, but I never found out what. I had to do a factory reset to clear it in the end (although not a full ROM reinstall).
As I'd already gone that far though, rather than risking re-installing apps again I actually chose another ROM anyway - Infamous (see above) - which I'm very happy with, and the devs there seem much happier to talk to you in general. Just my observation anyway, your experiences could well be quite different of course.
Andre
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.
Hello guys..
I am an ATnT Samsung galaxy S2 i777 user. Some may be aware that the logcat files generated by Samsung at times causes issues by exhausting the memory reserved for the apps. My phone was plagued by the issue and i wasnt aware of the exact problem.
As a result, i kept moving apps/data to the external mem card as much as possible to keep the phone cured of the 'device memory low' warning sign. I was away from the scene due to hectic schedule and as there wasnt any big need to install new apps/features either, i wasnt bothered too much.
Finally one day the phone rebooted while i was asleep, and i woke up to find that much of the customization was gone. No Gapps, No Apex launcher, No Amazon app store, many apps (incl Titanium backup) missing.
Forced to google, found out the *#9900# trick and wiped off the excess logcat files. The memory status got straightened out, but the phone wont restore to the earlier state even after reboots.
I was running Shostock ROM, and it was about time i moved to either Kitkat or even Lollipop based ROMS. And this is what i plan to do now that i have the perfect excuse. Before i pulled the trigger, i wanted to clarify some points out so pls do lend me a helping hand here.
Have chosen Carbon ROM as my next. (Geekynimrod and rogsersb11 been superb with the work)
1) I have moved a lot of apps/data to the mem card. Once i have flashed the new ROM, will this data interfere with the new setup?
2) I would ofc need to empty the mem card of the data which i dont require. How to clean up the moved app/data if they are of no use?
spacescreamer said:
Hello guys..
I am an ATnT Samsung galaxy S2 i777 user. Some may be aware that the logcat files generated by Samsung at times causes issues by exhausting the memory reserved for the apps. My phone was plagued by the issue and i wasnt aware of the exact problem.
As a result, i kept moving apps/data to the external mem card as much as possible to keep the phone cured of the 'device memory low' warning sign. I was away from the scene due to hectic schedule and as there wasnt any big need to install new apps/features either, i wasnt bothered too much.
Finally one day the phone rebooted while i was asleep, and i woke up to find that much of the customization was gone. No Gapps, No Apex launcher, No Amazon app store, many apps (incl Titanium backup) missing.
Forced to google, found out the *#9900# trick and wiped off the excess logcat files. The memory status got straightened out, but the phone wont restore to the earlier state even after reboots.
I was running Shostock ROM, and it was about time i moved to either Kitkat or even Lollipop based ROMS. And this is what i plan to do now that i have the perfect excuse. Before i pulled the trigger, i wanted to clarify some points out so pls do lend me a helping hand here.
Have chosen Carbon ROM as my next. (Geekynimrod and rogsersb11 been superb with the work)
1) I have moved a lot of apps/data to the mem card. Once i have flashed the new ROM, will this data interfere with the new setup?
2) I would ofc need to empty the mem card of the data which i dont require. How to clean up the moved app/data if they are of no use?
Click to expand...
Click to collapse
I would recommend checking this thread out:
http://forum.xda-developers.com/gal...de-partition-i777-phone-data-storage-t2839161
This procedure made all the difference for me.
I would also recommend choosing the 4.4.4 OmniRom. Normally I don't favor any Rom over the others in comments out of respect however, OmniRom is still being updated almost daily. It's the only 4.4.4 still in active development. I've tried many of the others and have settled on OmniRom for the past couple of weeks:
http://forum.xda-developers.com/showthread.php?t=2544790
There is a lot of quality work still available here. It's been a lot of fun reading these threads.
Madcat8686 said:
I would recommend checking this thread out:
http://forum.xda-developers.com/gal...de-partition-i777-phone-data-storage-t2839161
OmniRom is still being updated almost daily. It's the only 4.4.4 still in active development.
http://forum.xda-developers.com/showthread.php?t=2544790
Click to expand...
Click to collapse
Thanks a lot for the tip mate. I will def check the thread out.
Carbon ROM has been very impressive, and i wanted to try that out .. hence the inclination. But i guess i can always try both
Once i brush the basics off again, i ll be more comfortable getting the flashing done without too much apprehension. Thanks again. :good: