Related
Hi everyone. I've never been into rooting my technology, so I wait the hard wait for OTA updates.
Well, now that ICS is out for my TF101 I'm extremely happy... My Transformer has gotten me through thick and thin, and it deserves this kind of treatment!
Thing being, I'm not sure how to handle the update. Would things go smoother if I reformatted/factory reset the Transformer before doing the 4.0 update?
Even if I don't, should I maybe back up all my data before moving to ICS?
Lastly, will ICS have all of the Asus-installed apps like that one handwriting-note-taking app they added in an earlier update?
Thank you.
Feoen said:
Hi everyone. I've never been into rooting my technology, so I wait the hard wait for OTA updates.
Well, now that ICS is out for my TF101 I'm extremely happy... My Transformer has gotten me through thick and thin, and it deserves this kind of treatment!
Thing being, I'm not sure how to handle the update. Would things go smoother if I reformatted/factory reset the Transformer before doing the 4.0 update?
Even if I don't, should I maybe back up all my data before moving to ICS?
Lastly, will ICS have all of the Asus-installed apps like that one handwriting-note-taking app they added in an earlier update?
Thank you.
Click to expand...
Click to collapse
Yes.........always best to format.
Yes.....always back up....
Yes.....the apps are there..
Why are you not rooting?...
tweaked said:
Yes.........always best to format.
Yes.....always back up....
Yes.....the apps are there..
Why are you not rooting?...
Click to expand...
Click to collapse
Great, thank you.
I've had no experience rooting. The most I've ever done was put custom firmware on a PSP, and that got to be a headache and a half when the head developer quit development of new firmwares and I couldn't play newer games, etc.
Long story short, while I realize things are far more standardized on technology now, I don't really know what functionality I am going to get out of rooting an Android device. It does what I need without doing that, and tbh I don't really have the time to invest learning about rooting and its advantages, etc.
Lol
Why do people act like rooting is some complicated process that requires a degree in computer science.
Rooting a TF is friggin easy and simple. It takes less than 5 minutes to look up how to do it--you are already on this forum. The actual rooting process takes like a minute.Mod edit
horndroid said:
Lol
Why do people act like rooting is some complicated process that requires a degree in computer science.
Rooting a TF is friggin easy and simple. It takes less than 5 minutes to look up how to do it--you are already on this forum. The actual rooting process takes like a minute. Mod edit
Click to expand...
Click to collapse
I actually have a minor in computer science... lol
It's not that rooting is difficult, but I don't see any advantages to it since flashing custom rome is where things get tricky and I don't have the patience or willingness to learn the process.
I'm doing a factory reset on my TF101 right now. Am I supposed to go into the bios thing and reset those Caches too? Or can I just ignore that?
Edit: That sounded completely uninformed lmao. I mean the Dalvik cache and such in the recovery menu.
Feoen said:
I actually have a minor in computer science... lol
It's not that rooting is difficult, but I don't see any advantages to it since flashing custom rome is where things get tricky and I don't have the patience or willingness to learn the process.
I'm doing a factory reset on my TF101 right now. Am I supposed to go into the bios thing and reset those Caches too? Or can I just ignore that?
Edit: That sounded completely uninformed lmao. I mean the Dalvik cache and such in the recovery menu.
Click to expand...
Click to collapse
Flashing a custom ROM is not tricky.
Yes you should wipe those caches. You won't lose anything.
The vast majority of people who did factory reset before upgrading to ICS aren't having the issues that people are complaining about on this forum.
Hello,
Due to the 10 post threshold I am unable to post in the "Samsung Captivate -
Captivate Android Development
[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]" thread.
I have resolved this issue a couple months back.
So, due to the time that has gone by it is a little difficult to explain what I did.
Last night I reproduced the issue, but after a restore, I'm good as new.
So now I am compelled to post this here. Being a "noob" and like I said not able to completely remember what "exactly" was done to accomplish the fix.
I am willing to share any information you wish.
But in a nutshell, I flashed ( a ROM I can't remember at the moment, but I'm sure I will once I get down to it. at work and pressed for time, "lunch time" ) using Heimdall, then downloaded the rom "Imfinitum-blue-v1.1.0 to my external SD, ( using a 34 Gb SD card, seems that is the only card that I could use. From what I remember anyway. ) Mod version "aokp_galaxysmtd_milestone-4"
The kernel version currently being utilized on this device is "[email protected] #1.
Sorry for being so confusing, and vague, but I really wanted to get something out there. I see they are still working on a fix for this issue, I found this resolve before page 30, it's now at 57, and after recreating the issue and then resolving it after a restore.
So, ask any question you want and I will be happy to help.
Hope this helps.
Take care.
By "fixed" do you mean:
a) You have restored access to your INTERNAL sdcard?
b) You have used the emmc/sdcard swap method to use your external as the internal? (ie. your internal sdcard is still not useable)
It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue.
Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?
Hello,
Because this would save a lot of people's phones including mine, would be great if you post your steps so we can follow.
Take this with a grain of salt guys.
There is very little information in his post, which is his very first post. There is also no information about the process he used. I'm not sure what a 34gb SD card is. I believe the methods he alludes to have been tried by other members with no resolution.
I have a feeling he had a different issue or is just trying to get attention.
For all our sakes I hope I'm just rushing to judgement.
I guess what we want to know is, what have you done?
Say you just got the Enc Unsuccessful screen, turned off the phone and then what?
He's to shy to give anymore details.
Sent from my SGH-I897 using xda premium
yosup said:
By "fixed" do you mean:
a) You have restored access to your INTERNAL sdcard?
b) You have used the emmc/sdcard swap method to use your external as the internal? (ie. your internal sdcard is still not useable)
It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue.
Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?
Click to expand...
Click to collapse
I just duplicated the issue again, "no sdcard found"..etc... then using did a restore ("Semaphore CWM Recovery v5.5.0.4" by the way) restored the Captivate right back. After it boots I get "prepairing sdcard" then everything is back to normal.
Answer to "a." Yes, full access to both External and Internal drives. Also can mount and unmount all /system, /cache, /datadata, /sdcard, /data, /emmc.
Answer to "b." Sorry, can you elaborate on this. I'm just now sure what you mean by "swap"
You said: "It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue."
Now here it's difficult to say, I formatted and haphazardly (sorry, dumb I know!) flashed so many times attempting to get back control of this thing, I don't know. Google will restore my apps like before but I disabled this function. However it will detect application updates same 5 updated every time I restore it.
You said: "Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?"
Damn!, I'm just not sure, I'm really sorry but I wish I would have THOUGHT of posting HERE before YESTERDAY!...
Now is there a log file I can send out? So people can see whats going on inside this thing. Like I said so much time has gone by, and once I was able to get the camera working and transfer apps to the external card, and all that I basically went numb and stopped messing around. And I would like to point out, that
"Encryption Unsuccessful" crap ( and knowing better, I DID press Restart by the way) started just a couple days before this thread started. So just to give you an example as to how long this frustration was. I became obsessed, I worked on this phone for most all my waking hours, and I'm sure some of you have, "dreamed" of possible fixes as well!.
If it wasn't for the 10 post threshold I could have been more help. I read every single post in this thread up to the point where I fixed the problem.
Had it all in my head at the time but when I found I couldn't post with-in the >>Encryption Unsuccessful<< thread?! I wasn't sure why.
I even started a separate identity ( Barney Fyfe ) thinking that would allow me to post something.
And from what I read at the time, I thought, rather understood it to mean that I was locked out by some Admin here... Or ?!
Sorry, really, I did not realize I had to get 10 or more posts >>here<<
You know I'm sure I can get details on pretty much exactly what I did. Right now I'm at work, so I'll need a little more time.
Wdustin1 said:
He's to shy to give anymore details.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
No just very busy. I just posted this yesterday!?
Wadda' ya want from me eh!?..............
swayjd said:
I guess what we want to know is, what have you done?
Say you just got the Enc Unsuccessful screen, turned off the phone and then what?
Click to expand...
Click to collapse
Read my first reply.
I did so much to find a resolve, none of the suggestions I tried in the "Encryption Unsuccessful" thread worked at all by the way. didn't attempt EVERY suggestion, but a lot of them.
I'm going to attempt to get the horrifying memories back!
Oh, now here is an odd change in event, not sure if this is related or not but I just realized last night that the phone won't charge, using three different batteries, all fairly new, nor is it being recognized USB wise.
I have a couple other Captivates I'm now having to use to charge my batteries for this one.
It's like the micro usb is damaged?
I'm usually very careful on how I insert them, 4 different cables too. That all work with the other Captivate. It's bricked but does charge the battery.
It's a GT-19000.
Oh and I almost forgot!!
The Samsung Galaxy S SGH-897/Captivate I'm using is fairly new, the date code is " 1111 "
Red_81 said:
Take this with a grain of salt guys.
There is very little information in his post, which is his very first post. There is also no information about the process he used. I'm not sure what a 34gb SD card is. I believe the methods he alludes to have been tried by other members with no resolution.
I have a feeling he had a different issue or is just trying to get attention.
For all our sakes I hope I'm just rushing to judgement.
Click to expand...
Click to collapse
RELAX! I'm not playing around.
It's comments like this that kept me from being more proactive in posting in the first place!
Good lord!!
See, now you could have waited at least another day before this flaming!
Losing interest in this now. I was trying to help.
- - - - - - - - -
Hey people, my name is Pat Doherty.
Because of this dork I'm about done. I Do not NEED this kind of thing. I got my own stresses to deal with these days. And don't need some immature nerd slamming my attempt at helping out here.
I can be reached if you put anything you want in front of patdoherty dot net.
my site patdoherty dot net.
c'ya!
P.S.
You said:
"I'm not sure what a 34gb SD card is."
Really now!?
Are you serious!?
A SanDisk 32GB micro SD chip, "32gb" ( screen printed right on the chip ) = 32 gigabytes
Barney Fyfe said:
RELAX! I'm not playing around.
It's comments like this that kept me from being more proactive in posting in the first place!
Good lord!!
See, now you could have waited at least another day before this flaming!
Losing interest in this now. I was trying to help.
Click to expand...
Click to collapse
but dude, you gave us nothing.
please as another noob could you post exact details of your discovery? like what you did to get the inscription unsuccesful to come up repeatably,and what did you do get your phone to access the internal memory? an what exactly did you flash to get it all to work
You brought up a fix to an issue that is getting very high attention right now. You were not able to tell people how to recreate the fix. People are looking for a scientific method (think repeatable steps) to fix this issue that is affecting quite a few people.
I'm sorry if I hurt your feelings. I've been watching the Encryption Unsuccessful thread for a very long time. I was stating only what I observed. There have been others who had suggested a similar fix, but it has not been repeatable.
You are a talented artist and obviously have alot going on. I hope for others' sake you can give them some steps to follow. If so, you may just be the "chosen one"
Barney Fyfe said:
It's comments like this that kept me from being more proactive in posting in the first place!
Losing interest in this now. I was trying to help.
Click to expand...
Click to collapse
First of all, I'll commend you for sharing a positive outcome despite experiencing this dreaded issue. However, this is something being dicussed at the DEV thread level, which assumes a deeper level of detail than the average General or Q&A topic.
Serious people are giving serious consideration to the matter. Example, Woodrube is a well respected Vibrant / Transformer / Nook user, and he's invested a lot of time collaborating with Captivate users to pool our resources and build our knowledgebase here.
Whether you continue your participation is up to you. Hopefully your method will be a viable part of the discussion.
Barney Fyfe said:
I did so much to find a resolve, none of the suggestions I tried in the "Encryption Unsuccessful" thread worked at all by the way. didn't attempt EVERY suggestion, but a lot of them. I'm going to attempt to get the horrifying memories back!
Click to expand...
Click to collapse
Barney Fyfe said:
You know I'm sure I can get details on pretty much exactly what I did. Right now I'm at work, so I'll need a little more time.
Click to expand...
Click to collapse
Regardless how anxious we get, life always comes first. Take care of business. Just keep in mind that a lot of XDA veterans are putting their minds to this issue, and more details will help isolate the cause & effect. In general, details on your ROM, kernel, and any specifics would be helpful.
Barney Fyfe said:
I just duplicated the issue again, "no sdcard found"..etc
Click to expand...
Click to collapse
By saying "duplicated the issue", we're all going to assume you encountered the "Encryption Unsuccessful" screen again. Do you recall any specific steps you took to "duplicate" this issue? Since you were able to duplicate it several times, people troubleshooting the issue will benefit to know how you induced the matter. The goal is to discover what actually triggers this. Then, we'll get closer to finding a resolution.
Were you using the phone at the time - ie. the EU randomly appeared? Did it just reboot on its own and result in a dimmed boot animation screen? After you hit "reset," did you simply go into recovery and perform a NANDROID restore? Was there anything specific you did after getting the EU screen? Battery pull, reboot into recovery, flash other roms or kernels, etc? Did you previously connect it to your PC using MTP?
Barney Fyfe said:
... then using did a restore ("Semaphore CWM Recovery v5.5.0.4" by the way) restored the Captivate right back. After it boots I get "prepairing sdcard" then everything is back to normal.
Yes, full access to both External and Internal drives. Also can mount and unmount all /system, /cache, /datadata, /sdcard, /data, /emmc.
Click to expand...
Click to collapse
It seems you "resolved" your issue by simply doing a NANDROID restore via recovery. Was it really that simple? Or was there anything else (other roms or kernels flashed) prior to doing the restore.
If this is the case, then your experience starkly contrasts what most others have experienced - ie. no longer having access to the internal sdcard even in recovery (so a saved NANDROID backup wouldn't be accessible, etc).
Barney Fyfe said:
Answer to "b." Sorry, can you elaborate on this. I'm just now sure what you mean by "swap"
Click to expand...
Click to collapse
The "swap" is the work around being used to swap emmc & sdcard in vold.fstab - ie. to then have the phone recognize the external sdcard as the internal (since the internal sdcard is no longer accessible for 99.9% of the others with this issue).
Barney Fyfe said:
Now here it's difficult to say, I formatted and haphazardly (sorry, dumb I know!) flashed so many times attempting to get back control of this thing, I don't know.
And I would like to point out, that "Encryption Unsuccessful" crap ( and knowing better, I DID press Restart by the way) started just a couple days before this thread started. So just to give you an example as to how long this frustration was. I became obsessed, I worked on this phone for most all my waking hours, and I'm sure some of you have, "dreamed" of possible fixes as well!.
Click to expand...
Click to collapse
Everyone who's gone through this has experienced that same level of dread and anxiety. We can all relate.
Thanks for the nod my friend and I am still on the case but as you say life comes first.
There have been some developments in the SGSII threads that I'll post in the Dev thread.
Barney Fyfe said:
Hello,
Due to the 10 post threshold I am unable to post in the "Samsung Captivate -
Captivate Android Development
[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]" thread.
I have resolved this issue a couple months back.
So, due to the time that has gone by it is a little difficult to explain what I did.
Last night I reproduced the issue, but after a restore, I'm good as new.
So now I am compelled to post this here. Being a "noob" and like I said not able to completely remember what "exactly" was done to accomplish the fix.
I am willing to share any information you wish.
But in a nutshell, I flashed ( a ROM I can't remember at the moment, but I'm sure I will once I get down to it. at work and pressed for time, "lunch time" ) using Heimdall, then downloaded the rom "Imfinitum-blue-v1.1.0 to my external SD, ( using a 34 Gb SD card, seems that is the only card that I could use. From what I remember anyway. ) Mod version "aokp_galaxysmtd_milestone-4"
The kernel version currently being utilized on this device is "[email protected] #1.
Sorry for being so confusing, and vague, but I really wanted to get something out there. I see they are still working on a fix for this issue, I found this resolve before page 30, it's now at 57, and after recreating the issue and then resolving it after a restore.
So, ask any question you want and I will be happy to help.
Hope this helps.
Take care.
Click to expand...
Click to collapse
thinks, I wanna try it on t959 with the EU bug.
USB problem
Hello, the same happens to me an hour ago. No charging no connection to computer but if the phone is powered off as soon as I connect the charger the phone boots up but no charge.
Captivate with CM9.
Barney Fyfe said:
Oh, now here is an odd change in event, not sure if this is related or not but I just realized last night that the phone won't charge, using three different batteries, all fairly new, nor is it being recognized USB wise.
I have a couple other Captivates I'm now having to use to charge my batteries for this one.
It's like the micro usb is damaged?
I'm usually very careful on how I insert them, 4 different cables too. That all work with the other Captivate. It's bricked but does charge the battery.
It's a GT-19000.
Oh and I almost forgot!!
The Samsung Galaxy S SGH-897/Captivate I'm using is fairly new, the date code is " 1111 "
Click to expand...
Click to collapse
What the OP said seems more of luck.
B.S. ALERT!!!!
I cant believe i actually came back to this thread to waste my time again!!, reading a thread that is supposed to help fix a problem i am afflicted with, but is instead filled with A BUNCH OF [email protected]$%@# [email protected]#@#$T!!!!!
Dude, if want to help people you must understand that in order to do this you need to explain "exactly" what it is you are talking about. No one can trust your information based on your "belief" in it. Software is a very techinical thing, which means to explain it you need to speak in technical terms. If you cant do that, do some more reading. Otherwise you arent helping anyone but yourself....Thanks, but NoThanks.
Looking through the forums can be a little scary...mostly because of all the "phone stuck" and "PLEASE HELP" threads. My old phone was pretty much hard to brick, if something went wrong... just flashed back to stock (using ODIN). But the risk seems greater with the Hox. I can understand why people root and flash, obviously. But theres always that little voice saying, "If you f**k up, then you dont have a phone". How did you convince yourselves to take the risk?
roguly said:
Looking through the forums can be a little scary...mostly because of all the "phone stuck" and "PLEASE HELP" threads. My old phone was pretty much hard to brick, if something went wrong... just flashed back to stock (using ODIN). But the risk seems greater with the Hox. I can understand why people root and flash, obviously. But theres always that little voice saying, "If you f**k up, then you dont have a phone". How did you convince yourselves to take the risk?
Click to expand...
Click to collapse
right now, there honestly is really little chance for you to f**k up the hox unless you do something really stupid like flash an international hox rom or... idk what. stick to the tried and true methods: use twrp, wipe before flashing, and stick to att hox roms. Worst case scenario, if you get into a situation where you cannot boot and recovery says sd card not mounted (like I did a few weeks ago), easy peasy. Boot into bootloader and fastboot, then oem fastboot relock and flash ruu. RUU right now is almost like a get-out-of-jail card for any soft brick you might have (unless you hard brick it or mess with hboot). tbh, I know that I bought this phone to be able to flash roms and mod. If I am scared of that little risk, then I should go back to my iPhone LOL
roguly said:
Looking through the forums can be a little scary...mostly because of all the "phone stuck" and "PLEASE HELP" threads. My old phone was pretty much hard to brick, if something went wrong... just flashed back to stock (using ODIN). But the risk seems greater with the Hox. I can understand why people root and flash, obviously. But theres always that little voice saying, "If you f**k up, then you dont have a phone". How did you convince yourselves to take the risk?
Click to expand...
Click to collapse
Read and reread if you don't know what your doing. It's pretty hard to brick this phone. Just read the install instructions. The benefits out way the risks.
Sent from my HTC One X using xda premium
When I joined I never flashed a rom before let alone root and unlock and soff.
I found this forum and read the helpful guides, read them again asked my questions before I proceeded and have never had a problem.
You'll find 99% of the time when someone posts a problem its because they didn't follow instructions.
roguly said:
Looking through the forums can be a little scary...mostly because of all the "phone stuck" and "PLEASE HELP" threads. My old phone was pretty much hard to brick, if something went wrong... just flashed back to stock (using ODIN). But the risk seems greater with the Hox. I can understand why people root and flash, obviously. But theres always that little voice saying, "If you f**k up, then you dont have a phone". How did you convince yourselves to take the risk?
Click to expand...
Click to collapse
Ya know, this forum is a funny place. For each one of those help threads you see there is someone trying to intentionally brick their phone so they can send it back for replacement.
Personally I think they're scumbags for doing so and should have to live without a phone, but there's nothing you can really do about that.
I guess I convinced myself to start flashing stuff on my brand new $600 gadget because I had something else in line if something went wrong. I had my eye on this super neat Sony Experia Active phone, which is only $250 new (its waterproof and scratch proof. You should check it out!). If something goes wrong I can always get that. My financial situation this summer is pretty good (for once) so I can afford the risk.
Sent from my HTC One X using xda premium
Flashing something on the HOX is safe compared to the thought of randomly losing your imei like on the sgs3. Just stay with stuff you find in these forums.
The steps seem complicated but the guides are pretty much step by step, you just have to be patient. There was a couple times where I thought my phone wasn't going to boot back up because it was taking too long, but I just gave it time. Flashing new ROMs every couple days is a habit for me, so there's no way I could own an Android device and not root. Right now the benefits may not be good enough for you to flash because we still lack source code, but to me the ROMs we have now are 100000000x better than the stock ROM. Yeah stock is fast, but these are much faster and have tweaks that really make the phone "you" and not something you can just pick up off the shelf.
roguly said:
Looking through the forums can be a little scary...mostly because of all the "phone stuck" and "PLEASE HELP" threads. My old phone was pretty much hard to brick, if something went wrong... just flashed back to stock (using ODIN). But the risk seems greater with the Hox. I can understand why people root and flash, obviously. But theres always that little voice saying, "If you f**k up, then you dont have a phone". How did you convince yourselves to take the risk?
Click to expand...
Click to collapse
All those "phone stuck" and "PLEASE HELP" threads are posted by n00bs who jump in the deep end without learning to swim. Or even READ about swimming. If you follow the instructions for whatever you are trying to do to your HOX, be it root, unlock, flash a ROM, etc., there is very little risk of turning your phone into a paperweight. Even if something goes wrong, a RUU will fix your problem 99 times out of 100. There is always a risk, but the very minimal risk is well worth the boundless gains. You think the HOX is a bad ass device stock? It's 1000 times better rooted and ROM'd.
_MetalHead_ said:
All those "phone stuck" and "PLEASE HELP" threads are posted by n00bs who jump in the deep end without learning to swim. Or even READ about swimming. If you follow the instructions for whatever you are trying to do to your HOX, be it root, unlock, flash a ROM, etc., there is very little risk of turning your phone into a paperweight. Even if something goes wrong, a RUU will fix your problem 99 times out of 100. There is always a risk, but the very minimal risk is well worth the boundless gains. You think the HOX is a bad ass device stock? It's 1000 times better rooted and ROM'd.
Click to expand...
Click to collapse
I agree, it gets much better with a rom and radio installed. Also the main bricks out there arent from everyday rom flashing. They are from s-off attempt testing and yes from not following instructions. Be careful with apps from playstore that install a recovery. Best to do that manually.
roguly said:
Looking through the forums can be a little scary...mostly because of all the "phone stuck" and "PLEASE HELP" threads. My old phone was pretty much hard to brick, if something went wrong... just flashed back to stock (using ODIN). But the risk seems greater with the Hox. I can understand why people root and flash, obviously. But theres always that little voice saying, "If you f**k up, then you dont have a phone". How did you convince yourselves to take the risk?
Click to expand...
Click to collapse
Read before you flash and you'll be okay.
Sent from my HTC One X using xda app-developers app
Root & Rom is synonymous with Android. I can't imagine owning an android device and not rooting it. I normally give every device the prerequisite 2 weeks stock before I root. The hox I gave a month because I was loving it so much.
Eventually though I always root. Been doing since the days of the G1 when htc actually came pre installed with aosp lol.
Sent from my HTC One X using xda app-developers app
Everything has a risk to it. Change a light bulb in a lamp, and you run the risk of knocking the lamp over and breaking it. But nobody in their right mind is going to replace the whole lamp whenever it needs a new bulb, just because they are afraid of breaking it. Overly simplistic comparison, for sure. But you see what I'm getting at.
Follow instructions, read the warnings, and read up as much as you can on each step along the way, and you will most likely be fine. If things go wrong, flashing the RUU will fix a soft brick 99% of the tiime.
Read and read more. Watch a you tube tutorial maybe. I did both for days and got my hox, then I read more on here for 3 days before starting. Went slow, took me 2 hours to root, unlock bl, install recovery and finally a rom I liked and still liked.
Print out the directions if you have to. I had my iPad out open to the problems others had lol.
Is really not all that hard overall
Sent from my HTC One X
OK, with all my messaging and calendar issues, I decided to re-flash the stock tar (as I had used the old method of rooting). I set the phone up again, and now I am still stuck at the start up screen with the rings. It will not go any further. It works fine as long as I do not shut the phone down. From what I can tell, in order to fix it, I need to factory reset, which I am hoping to not do this time again (for the third time in a day). Where should or can I go from here?
redownload the tar file again, check the md5 sum to make sure its good.
Also make sure the tar file is for your carrier, ie; verizon. that may be your problem.
Ended up they are sending me a new device. Could be the device? Could be an app or setting I am restoring with TB though. Not sure. It is getting kind of frustraing since I am not hacking this as I have other phones in the past and am having more trouble with this than any other phone.
LTLFTCer said:
Ended up they are sending me a new device.
Click to expand...
Click to collapse
This is why we can't have nice things. If people didn't waste so much of Verizon's time and money with their hacking maybe Verizon wouldn't feel the need to fight so hard to keep us from being able to hack our phones.
Did you flash stock with recovery or did you Odin back? Cuz if you odin'ed back, you may have missed the step to uncheck auto reboot, then load stock recovery mode and wipe phone. If you Odin to stock and don't after that, but before booting, you will most likely boot loop or freeze.
For future reference....
jimmiem said:
This is why we can't have nice things. If people didn't waste so much of Verizon's time and money with their hacking maybe Verizon wouldn't feel the need to fight so hard to keep us from being able to hack our phones.
Click to expand...
Click to collapse
Andthis is why XDA sucks sometimes. Guys like you who troll and decide to post in a thread in a negative way instead of helping out earlier. And in all actuality, what is happening to my phone I do not think has anything to do with rooting. I had rooted on 7/9 for the sole purpose of wifi tether, nothing else had been done to the phone. It worked flawlessly until this week when the borwser, calendar and facebook decided to start force closing for no apparent reason. I figured a reboot would help and that started these issues. Sooo..therefore I decided to revert back from scratch and the problem is still there. I think we all would know that Verizon care wouldn't be able to hel outside exchanging the phone.
TechSavvy2 said:
Did you flash stock with recovery or did you Odin back? Cuz if you odin'ed back, you may have missed the step to uncheck auto reboot, then load stock recovery mode and wipe phone. If you Odin to stock and don't after that, but before booting, you will most likely boot loop or freeze.
For future reference....
Click to expand...
Click to collapse
Thanks, I did uncheck autoreboot. And was able to enter stock recovery. I actually factory reset again and other than the calendar issues, seems to be working fine so far.
LTLFTCer said:
Andthis is why XDA sucks sometimes. Guys like you who troll and decide to post in a thread in a negative way instead of helping out earlier.
Click to expand...
Click to collapse
You haven't even waited a day after posting for help before calling Verizon.. Too many people on these forums feel like Verizon is obligated to correct their problems even though they went against their Terms of Service..
Sent from my Commodore 64..
READY.
load"*",8,1
Hypnosis4U2NV said:
You haven't even waited a day after posting for help before calling Verizon.. Too many people on these forums feel like Verizon is obligated to correct their problems even though they went against their Terms of Service..
Sent from my Commodore 64..
READY.
load"*",8,1
Click to expand...
Click to collapse
Maybe so, but this didn't appear to be a root issue. Since this phone is so locked down I hadn't messed with anything and was getting multiple random force closes and then got stuck at the boot screen. No biggie, think I got it sorted out, went throgh and manually reset all settings and apps. Seems to have worked.
I'm glad you fixed the issue yourself..
Sent from my Commodore 64..
READY.
load"*",8,1
My G2X has CM7 #225 nightly. Google Apps are already installed.
ROM Manager is finally working (WooHoo!) and I'm thinking I should install the latest.CM7. When I select to download CyanogenMod 7 20121125 Nightly Build 13550 it asks if I also want to include Google Apps (2.3).
Can anyone please tell me if I need to install Google Apps again?
Thanks!
EDIT: Updated without the Google Apps, now at boot all I see is the smilyface LG at boot (10-sec off, 6-sec on). HELP!
Do you have playstore working right now? If it is, Gapps is already installed. If its not, then you need to install it.
There is no harm in downloading gapps again.
OK, downloaded without Google Apps, flashed thru ROM Manager, the box for clear Davlik cache was checked.
For the past five minutes I on the screen all I see is the flashing LG - it's the blue LG boot screen.
HELP!
EEngineer said:
OK, downloaded without Google Apps, flashed thru ROM Manager, the box for clear Davlik cache was checked.
For the past five minutes I on the screen all I see is the flashing LG - it's the blue LG boot screen.
HELP!
Click to expand...
Click to collapse
Go in CWM and reflash your nightly with Gapps. ROM Manager always screws with this phone. I thought you knew.
cricketAC said:
Go in CWM and reflash your nightly with Gapps. ROM Manager always screws with this phone. I thought you knew.
Click to expand...
Click to collapse
:good: was just going to say, try flashing via cwm.
Harmony Restored
Ah, I forgot and in CWM selected install from ZIP. Of course got a message that the directory was empty. Awk! I'm visiting my brother here in Long Island (helping him clean up from Sandy) and forgot to pack a microSD-to-USB adapter. Ran out to Radio Shack and overpaid for the adapter, Backed up my microSD card to my laptop (because it's the smart paranoid thing to do).
Then I selected Backup and Restore, restored my backup from earlier today - I'M BACK! Good thing I started from 100% battery because I had 53% battery left.
Thanks and thanks given for AndroidKills and cricketAC.
Didn't know that ROM Manager is a no-go for this phone. So, the smart thing to do is:
1) Download the CM7 update as a ZIP to my laptop (NOT using ROM Manager) and transfer to my G2X
2) Boot into CWM, clear Davlik and cache
3) From inside CWM, select Install from ZIP
Is this right?
Yea you always want to flash roms on the g2x with cwm. And do the usual wipe data, wipe cache partition, wipe dalvic cache. Then flash the ROM followed by the appropriate gapps
Sent from my LG-P999 using xda app-developers app
Barracuda1101 said:
Yea you always want to flash roms on the g2x with cwm. And do the usual wipe data, wipe cache partition, wipe dalvic cache. Then flash the ROM followed by the appropriate gapps
Click to expand...
Click to collapse
I wipe Dalvik cache, and the cache partition. But wiping data deletes all my contacts and settings and others say isn't necessary.
EEngineer said:
I wipe Dalvik cache, and the cache partition. But wiping data deletes all my contacts and settings and others say isn't necessary.
Click to expand...
Click to collapse
If you are going from one android version to another (2.* to 4.* or vice versa). It is. Otherwise, you can just wipe cache/dalvik.
cricketAC said:
If you are going from one android version to another (2.* to 4.* or vice versa). It is. Otherwise, you can just wipe cache/dalvik.
Click to expand...
Click to collapse
Why didn't you point that out? I'm wondering why you didn't mention to back up all data.
I've seen jerks on this group recommend to newbies to clear "cache/data", and when the newbie cries he lost everything the jerk gives a big "lol". I'm not saying that's you. But telling people to clear cache/data is clearly dangerous.
EEngineer said:
Why didn't you point that out? I'm wondering why you didn't mention to back up all data.
I've seen jerks on this group recommend to newbies to clear "cache/data", and when the newbie cries he lost everything the jerk gives a big "lol". I'm not saying that's you. But telling people to clear cache/data is clearly dangerous.
Click to expand...
Click to collapse
If newbies read as they are supppsed to, 99% of dev threads say "to make a nandroid/backup your data before you flash this..."
anytime i flash a thing i run TiBkup, nandroid, than wipe cache, dalvik, data, and sysyem.
sometimes internal sd as well.
fresh clean so no data left ober gunking up new setup.
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
justjackyl said:
If newbies read as they are supppsed to, 99% of dev threads say "to make a nandroid/backup your data before you flash this..."
Click to expand...
Click to collapse
Wrong.
Always assume a newbie knows nothing.
EEngineer said:
Wrong.
Always assume a newbie knows nothing.
Click to expand...
Click to collapse
Wrong.
I assume that newbies watched the how not to be a noob video which tells you to search and read.
We are not here to hold people's hands.
No one held my hand, I followed the rules, found the guide.for modding the g2x and...omg...i READ it. That guide alone warns to make a backup.
Its not my, nor any other XDA members responsibility to walk anyone through step by step , we assume you did as you were instructed, and studied. If you jump right in without studying, than thats your/their fault.
Sorry you feel that way, but thats how it is.
Ultimately, in the end, no one is responsible for any action a person takes, and any damages those actions may cause, other that persone themselves. Whether here, or in life.
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
justjackyl said:
Wrong.
I assume that newbies watched the how not to be a noob video which tells you to search and read.
We are not here to hold people's hands.
Click to expand...
Click to collapse
Assume a noob knows nothing. Assume there are visitors that haven't joined, but just found this page by a search engine.
it's not about holding people's hands. It's about helping. That includes not deliberately leaving out vital information that can have devastating consequences to someone's phone. Already had that happen to me, a jerk gave me bad advice that, had I followed it, would have bricked my phone. You remind me of him.
Honestly, you haven't convinced me that you're one of those people that likes giving bad advice.
Look, I've done tech support for over 15 years, both in person and on the phone. This is how it is. Why do you defend giving deliberately dangerous advice?
EEngineer said:
Assume a noob knows nothing. Assume there are visitors that haven't joined, but just found this page by a search engine.
it's not about holding people's hands. It's about helping. That includes not deliberately leaving out vital information that can have devastating consequences to someone's phone. Already had that happen to me, a jerk gave me bad advice that, had I followed it, would have bricked my phone. You remind me of him.
Honestly, you haven't convinced me that you're one of those people that likes giving bad advice.
Look, I've done tech support for over 15 years, both in person and on the phone. This is how it is. Why do you defend giving deliberately dangerous advice?
Click to expand...
Click to collapse
I defend taking responsibility for your own actions.
Ive done, and still do IT tech support. I understand what your saying.
that said, we are just supposed to ignore all the guides for newbies that the xda userbase has created for them and everytime repeat over and over whats stated all over?
*sighs* this is the point where we agree to disagree. You obviously enjoy repeating information easily obtained by searching and reading as rules state.
I on the other hand do not.
And offering support here is nothing like a paid tech support job at all.
And "visitors " can't post, so thats kind of negated.
Lets just choose to stop this here.
it comes down to difference of opinion.
You think everyone should just be handed information that they did not take the time to research themselves, on a silver platter.
I on the other hand, believe everyone has to work for what they want/earn rather than get a free handout.
Your like obama with public healthcare, I'm like Romney, you get what you put in. lol
Just an example, a bad one yes, and not taking a political stance.
We just have varying opinions on the matter is all....
cheers mate!
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel
Please don't compare me to Obama or I will throw up.
And pretty much everything you wrote is a horrible,insulting generalization - and wrong.
Look, I'm updating from CM7 to CM7. Didn't I I make that clear from the beginning? Deleting data is not needed or necessary - you even admitted that yourself, right? And yet you still insist that there was nothing wrong with advising to delete data.
Hey, I can understand your point of view because you have been here for so very long you have a mindset of "everyone should think like I do". You've made it abundantly clear that anyone that isn't constantly on this board deserves what they get, right?
But most people aren't on this board constantly, and only come here occasionally. And those are also the people that need the most help.
Let's be clear - I don't know you. And there are people out there that enjoy giving bad advice and bricking people's phones. How do you differentiate yourself from those people? You haven't convinced me that you aren't one of those people. Your position is that if you give someone bad advice, it's their faulty for taking it. That's the position of someone who likes giving bad advice.
The summary of what you attempting to tell me is that it is O.K. for you to give bad advice as long as your INTENTIONS are good. THAT is the classic liberal Obama position ("so what the economy is screwed, hey, I tried!"). The classic liberal position is avoiding responsibility. You are a classic liberal, bearing the the motto "It's Not My Fault"
I never offered you any advice.
I always advise people to do full wipes, including data, so no junk is left behind.
You must have confused me with someone else.
Anyways, agree to disagree.
Have fun.
G2x-CM7 Nightly 11/18/12 Build, Trinity ELP Kernel